Who to contact
This policy covers the Layers app and website. Layers is founder-operated. The privacy contact is founder@layersdating.com.
Information used to provide Layers
We handle your verified contact address, sign-in provider details, account/session records, age declaration, profile answers, selected photos, privacy choices, search preferences and confirmed location. Optional profile answers may reveal sensitive personal information; choose what you share and review the public profile presentation before publishing.
We also process reactions, viewed-profile versions, mutual interest, conversations, notification and alert choices (including any email address you give for discovery alerts or a city waitlist), reports, reconsideration requests and limited operational records. These support discovery, recommendations, messaging, safety, account recovery and deletion. We do not collect face-verification or biometric evidence for the initial release.
Signing in and notifications
You can create or sign in to a Layers account using Apple, Google, or an email address and password. When you use Apple or Google, we receive the provider’s account identifier and the email address it shares with us. Apple may share a private relay address if you choose Hide My Email. We use these details to create and protect your account. We do not receive your Apple or Google password.
Supabase processes email/password authentication for Layers. We send an email code to confirm a new email signup and when you request a password reset. Ordinary email/password sign-ins do not send a code. Do not send your password or email codes to support.
For Sign in with Apple, we keep an encrypted provider token so we can revoke Layers’ Apple authorization when you delete your account. Deleting your Layers account removes access immediately. If Apple is temporarily unavailable, we retain only the encrypted token and the information needed to retry revocation, then remove the token once Apple confirms revocation. A provider outage does not restore your account or delay its other deletion work.
If you turn on push notifications for your phone, Layers uses Firebase Cloud Messaging (Google) and, on iPhone, Apple Push Notification service to deliver message, mutual-connection, new-people and city-opening alerts. We associate a device delivery token and an installation identifier with your signed-in account so alerts reach the right phone. The delivery providers receive the device routing information, generic alert text such as “New message on Layers”, and an opaque notification identifier. We do not include message contents, names, profile answers, photos or location in these push payloads. We do not enable Google Analytics for this delivery setup.
When you have seen everyone who currently matches your preferences, Layers records that you are waiting for new people. Once a day we check whether at least five people now match your preferences and you match theirs. If so, we send one alert, then stop until you run out again. The alert comes as a push notification unless you turn that off, and by email only if you turn email on and give an address. Alerts never name or show another member. You can change these choices from Discover at any time; turning email off removes the address straight away.
You can choose a city where Layers is not open yet. You can still create and publish a profile, but nobody sees it and you see nobody until we open there. You can join that city’s waitlist to hear once when we open: by push notification, by email to an address you give, or both. The alert never names or shows another member or your location. We also count, by city, how many people are waiting and how far they got with their profiles, to decide where to open next; these counts do not identify anyone. You can change or leave the waitlist from Home at any time.
You can turn push off in Settings → Push notifications or in your phone’s settings. Signing out or deleting your account removes its device registration. Alerts already accepted for delivery may still appear; opening an alert checks that you still have access to the conversation.
What other people can see
The app shows profile content according to its layer, photo and relationship-access rules. Your contact address, full birth date, precise confirmed location, private answers and unilateral interest are not public profile fields. Personal details you voluntarily put into visible text can identify you; anonymous layers cannot undo that disclosure.
When you and another person are both in Resonance, each of you can see the total points you have given the other and the total they have given you so far. These totals come from your reactions to each other’s layers and can change as more layers are explored. We do not show the other person your reaction to an individual layer, but a change in a total can hint at a recent reaction.
Conversations are available to their authorized participants. Blocking, unmatching, restrictions and deletion change access. We retain reported snapshots privately for safety review rather than exposing unrelated conversations to staff.
Recommendations and safety review
Layers uses your interactions and eligibility settings to suggest people independently for each profile layer. Private recommendation diagnostics are retained for 30 days and removed on account deletion. We do not promise that a recommendation predicts attraction or guarantees a connection.
Projected public profile text and processed photos are checked through OpenAI for content moderation. Private answers, raw location/birth-date fields and unreported private messages are not sent for that check. Flagged submissions stay unpublished for founder review; a provider flag does not automatically ban an account. You may ask for reconsideration of a decision.
Website sign-ups
If you join the waitlist or apply to the beta on layersdating.com, we collect your email address, city and age. If you apply to the beta, we also collect your phone platform, the Google account email you use on Google Play (Android only), your gender, the genders and ages you’re interested in, how far you’d look for a match, and your answers to the application questions. We use these to decide where to open next, to invite a beta group whose members are likely to match each other, and to email you about the beta and launch.
Your gender and the genders you’re interested in can reveal your sexual orientation. Only the founder sees them, and only to form the beta group. We review a sign-up only after you confirm your email address. To stop automated abuse, we keep a one-way coded form of the IP address a sign-up comes from, which cannot be turned back into the address, for up to two days.
Supabase stores sign-ups and Resend sends our emails. Every email we send tells you how to unsubscribe. We delete a sign-up when you unsubscribe, when you ask us to, if you don’t confirm your email within 30 days, or 12 months after you sign up, whichever comes first. Joining the waitlist does not create a Layers account; if you later use the app, the rest of this policy applies.
Service providers and access
Supabase provides account authentication, database and private media services; Apple and Google provide optional sign-in; Firebase Cloud Messaging (Google) and Apple Push Notification service deliver push alerts; Cloudflare hosts the website and forwards the founder contact address; Resend delivers authentication email, any discovery-alert or city-waitlist email you ask for, and website sign-up email; OpenAI provides the public-content moderation check. The founder’s monitored mail inbox receives support requests.
Sentry helps us diagnose crashes using technical details such as the error type, code location, app version, device model and operating-system version. Sentry processes these reports in the United States. We disable screenshots, session recordings and interaction breadcrumbs, and configure app and server-side scrubbing so names, contact details, messages, photos, IP addresses, location and account/device identifiers are not retained in crash events.
Geoapify provides the map images shown when you choose a location. Your device requests tiles for the area visible on the map, so Geoapify and its delivery providers receive that map area, your IP address and technical request details. These requests do not include your Layers account identifier, profile answers, messages or photos. Geoapify hosts its API services in the European Union and uses a globally distributed delivery network.
GitHub Actions runs private photo-backup jobs. During a job, a GitHub-hosted runner temporarily processes private photos and an inventory of the backed-up files, then encrypts the archive before it is stored as a private GitHub artifact. The decryption key is kept separately from GitHub.
Provider processing may occur outside Canada, including in the United States and the European Union.
We limit staff access by current authentication, explicit permissions and purpose. Sensitive reads/actions are audited. Credentials are not published in the app, and private evidence is not stored for offline use in the admin browser. No system can guarantee absolute security; contact us about suspected misuse.
Retention and deletion
Account/profile data and explicit reactions are kept while needed to provide the account, then removed through deletion. Unretained removed media is scheduled for purge within 24 hours; previously issued media access expires within the bounded access window. Reported evidence is retained for 90 days. Closed support content is deleted after 90 days, minimal staff audit after one year, and minimal deletion follow-up/contact records after 90 days from completion if retained.
Inactive push device registrations expire after 90 days. Push delivery jobs expire after one day and are removed after seven days. A discovery-alert email address is kept only while email alerts are on; each alert email job is removed within seven days, and its address is cleared once the email is accepted for delivery. A city-waitlist entry, and any email address in it, is removed once its opening alert is sent, as soon as you choose a city that is open, when you leave the waitlist, or when you delete your account.
Verification codes expire after 10 minutes; any separate verification-attempt details are deleted after seven days.
Sentry crash events are retained for up to 90 days under our current plan. Issue-level error counts may remain after the underlying events expire. Geoapify retains technical request records for access control, usage counting, troubleshooting and performance; its privacy policy says successful-request data is generally kept for no longer than 24 hours, with retention limited to what is needed for aggregated usage statistics.
Encrypted photo-backup archives are retained in GitHub for seven days. A deleted photo may remain in an existing encrypted archive until it expires. Temporary unencrypted working copies are removed when the backup job finishes. Before restored data is made accessible, we reconcile account deletions, removed photos and access restrictions. Other backup copies are not presented as instantly erased. Any legally required preservation must have a documented basis and limited access.
Your choices and requests
You can edit permitted profile information, control visibility, turn push, discovery alerts and city-waitlist alerts on or off, block/report, end connections and delete your account. Withdrawal of information necessary to provide the service may require hiding or deleting the profile. Contact the privacy address to request access/correction, ask about consent or challenge our handling of your information. We verify identity and protect other people’s information before responding.
The service is for adults aged 18 or older. Report suspected underage use through the app or child-safety contact. Material policy changes must be explained before new processing or consent is introduced.