Signal Faces

Signal Faces

Privacy policy

What the app and our service keep about you, why, where it lives, and how to have it deleted. Written to be read, not skimmed past.

Updated20 Nov 2026

01Who we are

Signal Faces (the “app”) and the service behind it are run by Big Signal Systems Pty Ltd, an Australian company based in Western Australia. In this policy “we” and “us” mean that company.

Company
BIG SIGNAL SYSTEMS PTY LTD
ACN
703 678 424
ABN
To be added

02The short version

  • You sign in with your Google account, so your faces and purchases follow you to a new phone. From Google we keep only your Google account’s ID, its email address and your name, and they’re deleted with your account. We don’t ask for a phone number or a password.
  • We keep what the app needs to work: your account code, your watch’s model and screen, the faces you install, and anything you choose to send us, such as a review.
  • When the app crashes, it sends us a crash report. You can turn that off in You→Settings.
  • We never see your card details. Google Play handles payments.
  • You can watch ads to unlock faces. They come from Google AdMob, which collects some information about your device. Premium has no ads.
  • We don’t sell your data, and we don’t use it to build an advertising profile.
  • You can delete your account in the app at any time, or ask us here on the web.

03What we collect

The information we keep, and why
WhatWhy
Your Google sign-inWhen you sign in with Google, Google gives the app a signed note saying who you are, and our server checks it with Google. From it we keep your Google account’s ID (a number Google uses for you), its email address, whether Google has verified that address, and your name. We use them to find your account again on a new phone or after reinstalling the app, and to show you which Google account you’re signed in with (You→Account). We don’t use your email address to contact you or for marketing, we don’t show your name or address to anyone else (reviews still say “Signal Faces user”), and we don’t get your Google password or access to anything else in your Google account. Accounts made before sign-in existed are linked to Google the first time you sign in.
Account code and sessionAn account code such as SF-7K2M-Q9XP, made when you first open the app, and a random sign-in token. We keep only a scrambled form (a hash) of the token, never the token itself. The code lets you and us find your account for support or deletion.
Your phoneA label for your phone: its make and model, such as “Samsung SM-S928B”. It tells your devices apart in support. The app also tells us its own version and your phone’s Android version, so we know which versions are still in use and don’t break them with a change.
Your countryThe country the app connects from, as Cloudflare (our network provider) tells us. Only the country, never your address, city or internet address. We use it to see where the app is used, and to plan prices and languages.
Your watchIts model, Wear OS version, screen size and shape, and what it can do. We use these to offer only faces that will work on it.
App IDsThe phone app and the watch app each make a random ID when they’re installed. The watch app’s ID tells your watches apart and makes sure each watch gets one weekly box. The phone app’s ID is noted when it makes your account, to stop abuse. Neither is a hardware ID: the app doesn’t read your phone’s or watch’s IMEI, serial number or Android ID.
Faces you installWhich faces you install and remove, when, and whether the install worked. This remembers what you have, and tells us when a face fails on a type of watch. The app also updates the faces you’ve installed by itself (on unless you turn off You→Settings→Updates→Update faces automatically), and these updates are recorded like installs.
Faces you saveFaces you save with ♡, and when, so they’re in the Your faces tab. Your faces also lists the faces you’ve installed before, from the install records above. Saved faces are deleted with your account. We also count how many people saved each face, without names, to see which faces people like.
SearchesThe words you type in the search box are sent to our service to find matching faces. We use them only to answer that search. We don’t store or log them.
What you send usReviews and ratings, feedback, suggestions for new faces, and your answers to our messages. Feedback also carries your watch’s model, Wear OS version, the watch app’s version and the face it’s wearing, so we can find the problem; the app shows this before you send. Reviews and ratings are shown to other people in the app under the name “Signal Faces user”, never anything that identifies you. We can hide reviews that break our rules.
NotificationsWhen your phone lets the app show notifications (on Android 13 and later, Android asks you first), the app gets a notification token for your phone from Google’s Firebase Cloud Messaging and sends it to us, so we can tell you when we reply to something you sent, such as a fix for a face you reported. Notifications about replies are on unless you turn them off in You→Settings. Offer notifications are off unless you turn them on: if you choose Turn on when the app asks about notifications, or turn on You→Settings→Offers: free faces, we keep that choice with your account and may tell you, at most about once a week, when a face or a group of faces is free for a while. Turn it off there at any time. We keep the token with your signed-in session, and delete it when you turn off both kinds of notification in You→Settings, sign out, or delete your account. A notification carries the reply’s or the offer’s heading and the start of its text (an offer may also show the face’s picture), and passes through Google to reach your phone.
Reports of reviewsIf you report a review, we keep the reason you chose, any note you add, and which account reported it, so we can look into it. We keep a report until we’ve dealt with it, or until the account that made it is deleted.
PurchasesFrom Google Play: what you bought and whether a subscription is active, so Premium works. The app sends us Google Play’s purchase token so our server can check the purchase with Google. We keep only a scrambled form (a hash) of the token. For a purchase, we also keep the price and currency you were shown, the country Google Play records for it and Google’s order number, to understand sales and match them with Google’s reports. Never your card or bank details.
Premium codesIf you enter a code under You→Have a code?, we keep which code your account redeemed, so Premium stays on for your account.
Weekly boxWhich box your watch opened each week and what was in it, so each watch gets one a week. If you delete your account, the current week’s entry keeps only your watch app’s install ID until that week ends, so the same watch doesn’t get a second box; then it’s deleted.
Ad unlocksWhich faces you unlocked by watching ads, and the ads you watched today, for the daily limit and how many ads the next face takes. Google can confirm to our server that you watched an ad to the end, so an unlock can’t be faked.
Crash reportsWhen the phone app or the watch app crashes, the phone app sends us a report the next time it opens. It holds the error and where in the app it happened, the app and its version, the Android or Wear OS version, the phone’s or watch’s model, and a random ID for the app’s install, which we keep only in scrambled form (a hash). Sign-in tokens and the details in web addresses are taken out before it’s sent. Each report is linked to your account, so we can limit how many one account sends and delete them with it. Reports are on unless you turn off You→Settings→Diagnostics→Send crash reports; then crashes stay on your phone.
Server logsCloudflare and our website’s web server record requests: the internet (IP) address, the time, and what was asked for. Our service uses IP addresses only briefly, in memory, to limit abuse such as mass account creation. It stores one only when a sign-in or pairing attempt fails, to spot attacks.

04What we don’t collect

Apart from the name and email address of the Google account you sign in with (see “Your Google sign-in”), we don’t ask for your name, email address or phone number, and we don’t collect your contacts, photos or messages. The app doesn’t read your location from your phone or watch; we keep only the country you connect from (see “Your country”). Google AdMob may work out a rough location from your IP address when it shows an ad (see section 06). Faces show things like steps, heart rate and battery on your watch; that information stays on the watch and isn’t sent to us.

If you email us, we’ll have your email address and what you wrote, and we use it only to reply.

05How we use it

  • To run the app: show you faces that suit your watch, find faces when you search, install them, and remember what you’ve unlocked or bought.
  • To fix problems: find faces that fail on particular watches, fix the crashes in crash reports, and answer your support questions.
  • To improve the collection: which faces are installed, and what people suggest and review.
  • To keep the service safe: stop abuse such as mass account creation or spam reviews, and look into reviews people report.

We use AI tools to help us sort reviews, feedback and suggestions, and to draft replies (see section 08). A person reads every reply before it’s sent, and nothing is decided about you by a machine alone.

We don’t sell your information, rent it, or use it for advertising profiles.

06Ads and purchases

Purchases

Premium and other purchases are made through Google Play, under Google’s terms and privacy policy. Google tells us the status of a purchase; we never receive your card details.

Rewarded ads

Ads only appear when you choose to watch one to unlock a face. They are served by Google AdMob, using Google’s Mobile Ads software in the app. When it runs, Google collects your device’s advertising ID and app set ID, your IP address (which can give a rough location), how you interact with ads, and diagnostic information about the ad software. Google uses this for advertising, analytics and fraud prevention, as described in how Google uses information from apps that use its services.

The app also gives Google your account code with each ad, so Google can confirm to our server that the ad was watched and the unlock is yours.

Where the law requires it, such as in Europe, the UK and some US states, the app asks for your consent with Google’s consent form before showing an ad. You can change your choice at any time in You→Settings→Privacy→Ad privacy choices (shown where the law requires it). You can also reset or delete your advertising ID in your phone’s settings. Premium has no ads.

07Where it’s stored

  • Google Cloud, in Sydney. Our server and database run on a server rented from Google Cloud in Sydney, Australia.
  • Cloudflare. Face pictures and face files are stored in Cloudflare R2, and so are nightly backups of our database, which are kept for 30 days. Cloudflare’s network sits in front of our services, so your requests pass through it.
  • Our own server, in Western Australia. A live copy of our database is kept on our own server in Western Australia, where our store admin tools run. A further copy of your reviews, feedback, suggestions and answers to our messages, with the watch details sent with them, and of failed installs and crashes, is kept there too. We use them to run the store, sort what you send and plan fixes and new faces.
  • AI services, in the United States. To sort that copy and draft replies, we send it to Anthropic (Claude), and sometimes to other AI models through OpenRouter (see section 08).

This means your information is held outside Australia as well as in it. We choose providers with strong security, and they handle it only to provide their service to us.

08Who we share it with

Google AdMob. The only company we share information with for its own purposes. When you watch an ad, Google AdMob receives your rough location (from your IP address), how you interact with ads, diagnostic information and device IDs (the advertising ID and app set ID), and uses them for advertising, analytics and fraud prevention. See section 06.

Service providers. These handle information only on our behalf, to provide their service to us:

  • Google Cloud and Cloudflare, for hosting and storage.
  • Google Play, for purchases.
  • Anthropic, which makes the Claude AI models. We send it your reviews, feedback, suggestions, answers to our messages and reports of failed installs, with the watch details sent with them, so Claude can sort them and draft our replies. It doesn’t receive your account code. Anthropic handles this under its commercial terms and privacy policy.
  • OpenRouter, which we sometimes use to send the same work to other AI models when Claude isn’t available.
  • Google, to sign you in. When you sign in, Google knows you signed in to Signal Faces, as with any app you sign in to with Google, under Google’s privacy policy. We don’t send Google anything about you.
  • Google Firebase Cloud Messaging, to deliver our notifications to your phone. It receives your phone’s notification token and the notification’s text.

We may also disclose information if the law requires it. We don’t sell it, and we don’t share it with data brokers.

09How long we keep it

We keep your information while your account exists. When an account is deleted, most of its information is removed from our database straight away (see section 10), and it falls out of our backups within 30 days. There are some exceptions:

  • Crash reports are kept for 90 days, or until the account is deleted if that’s sooner.
  • Install counts. We keep a count of how many times each face has been installed. When an account is deleted, those install records stay, but with nothing left that links them to you.
  • What you sent us, in our feed. Reviews, feedback, suggestions and answers also go into a feed inside our database, which our own server in Western Australia copies. Each entry holds what you wrote, the rating, the watch details sent with it, and a number that stood for your account. Deleting your account doesn’t yet remove these entries, in our database or in the copy, and they have no end date yet. We’re changing that so that deleting an account removes them too.
  • Deletion requests made on the web, with the contact details and note you gave, are kept as a record that we acted on them.

10Deleting your account

In the app, go to You→Account→Delete my account. That deletes your account at once, including your reviews, feedback, suggestions, our messages to you, your notification tokens and choices, crash reports, reports you made of reviews, your watches, any faces you unlocked with ads, any Premium code you redeemed, and your Google sign-in (your Google account’s ID, email address and name). Your Google account itself isn’t affected. The exceptions are in section 09.

After deleting, the app returns to the sign-in screen. Signing in again, even with the same Google account, makes a new, empty account with a new account code. That’s expected: the new account has nothing from the old one.

Signing out (You→Account→Sign out) is different: it only signs this phone out. Your account stays, and signing in with the same Google account brings it back.

No longer have the app? Use the account deletion form or email [email protected]. We act on requests within 7 days.

Deleting your account doesn’t cancel a Google Play subscription. Cancel that in Google Play. Your purchases stay with your Google account.

11Your rights

You can ask us what information we hold about you, ask us to correct it, or ask us to delete it. Email us with your account code (in the app under You→Account) or the email address of the Google account you sign in with, so we can find it. If you’re in the European Union or the United Kingdom you also have rights under the GDPR, such as to object to processing or to take your data elsewhere.

If you’re unhappy with how we’ve handled your information, tell us first and we’ll try to put it right. In Australia you can also complain to the Office of the Australian Information Commissioner.

12Children

The app isn’t directed at children under 13, and we don’t knowingly collect information from them. If you think a child under 13 has used it, email us and we’ll delete the account.

13Security

Everything between the app and our service is encrypted in transit (HTTPS). Sign-in tokens are stored only as hashes, and access to our systems is limited to the people who run them. No system is perfectly secure. If a breach affects you, we’ll tell you as the law requires, in the app or on this site.

14Changes and contact

If we change this policy, we’ll update it here and change the date at the top. If the change is significant, we’ll also say so in the app.

Questions? Email [email protected].