1. Introduction and scope
This Privacy Policy describes how the operator of Same Wavelengths handles information when you use the Same Wavelengths iOS app and when you visit this website. Same Wavelengths is a two-player question game for couples and friends. You answer the same questions, see where you match, and can talk over a live video connection while you play.
The app is guest-first. You can create a profile with a display name and play without an account. Sign in with Apple is optional and is the only account provider. There is no email-and-password sign-in.
This website is a public information site. It does not offer accounts, gameplay, video calls, or a contact form. It does not run advertising or a third-party analytics script.
The description below is based on the iOS app and API reviewed on November 18, 2026. It is a draft for the operator and for legal counsel. It is not legal advice.
2. Information we collect
Some information is provided by you. Some is created so the app can run a game, keep a profile on your iPhone, and understand whether the product is working.
You provide a display name, an optional avatar from a fixed set, and an optional profile photo. If you use Sign in with Apple, Apple can provide a user identifier and, when you allow it, an email address, including a Hide My Email address. You also provide your answers by selecting an option the app offers. You choose whether to allow notifications, and you can change statistics privacy settings.
The app and API create a player id, a device secret, session tokens, game and room records, product-activity events, and, if you allow notifications, a push token. The sections below say what each of those is for.
3. Account and profile information
A guest profile stores a display name of up to 20 characters, an optional avatar (wave, sun, moon, star, bolt, leaf, flame, or spark), sound and haptics preferences, and a player id created on the device. The device secret and tokens are kept in the iOS Keychain. The server stores a hash of the device secret, not the secret itself. Refresh tokens are stored only as a SHA-256 hash.
Sign in with Apple is optional. The server checks Apple’s identity token. The Apple subject is the account key. An email address Apple provides is stored on that sign-in record. It is not used to find or merge accounts. The app does not ask you to create a password, and it does not offer Google, Facebook, or email sign-in.
If you choose a profile photo, the app uploads a JPEG to the API. The file is stored on the server for that player and can be removed from Profile or when the account is deleted.
An unclaimed guest profile cannot be restored if the app is deleted or the Keychain is lost. The app says so in Settings. Signing in with Apple is what keeps the profile attached to your Apple ID.
4. Information you provide when playing
A game is a private room for two people. The host gets a 4-character room code and can share that code or an invite link that opens the app. The other person enters the code on their own iPhone. A third person cannot join that room. Rooms expire after two hours.
Questions come from the app’s catalog. You answer by choosing one of the options. The API stores the option id, your player id, and the time you submitted it. It does not store a free-text answer. The person you are playing with sees the round result with you, including when you match.
You choose a category or collection, a mode, the number of rounds, and the timer when you create a game. Those choices are part of the session.
5. Game activity and statistics
The server calculates statistics from completed sessions. The app does not let you type in a score. Counts include games played, rounds, matches, streaks, play time, and a match percentage. Recent completed games can appear on an Apple account’s profile.
Compatibility, discoveries, and achievements are calculated from those sessions. “Friends” in the statistics screens means people you have played with. The app does not read your contacts and does not have a friend-request directory.
Settings includes Wavelength privacy controls: whether your matches are visible to people you have played with, whether you appear on friend leaderboards, whether achievement sharing is allowed, and whether statistics sharing is allowed. Those controls do not hide the live round result from the person in the current game. The in-app text says your answers stay private either way, meaning they are not posted as a public feed.
Guest statistics shown as “On this iPhone” stay on the device. An Apple account’s home stats are labeled as synced with the account and come from the server.
6. Camera and microphone permissions
Same Wavelengths asks for the camera so you and the other player can see each other, and for the microphone so you can hear each other, during the live conversation in a game.
The permission text also says that, if you both agree, the host phone can save a private recording of the camera and microphone. That recording option is currently turned off in the app, and the lobby does not ask for recording consent. See the next section.
The app asks for photo library access so you can choose a profile picture. It asks for permission to add to your photo library only when you choose to save a clip or recap. A local-network permission exists only in Debug builds used with a development server. Release builds do not include it.
You can refuse the camera or microphone. A normal game is built around the live conversation, so refusing those permissions means the two phones cannot show and hear each other. You can change the permissions later in iOS Settings.
7. Video and audio communication
Live video and audio use WebRTC directly between the two iPhones. The API introduces the phones: it passes connection messages such as offers, answers, and network candidates, and it does not store those messages. The API does not store the live call.
By default the app uses Google’s public STUN server (stun.l.google.com) to help the phones find a path to each other. A TURN relay is used only if the operator configures one on the API. No TURN provider is named in the app. If a relay is turned on later, that provider carries the encrypted media packets between the phones and can see connection metadata such as IP addresses. This policy does not claim that a relay provider is unable to see that metadata.
WebRTC encrypts the media connection between the two phones. This policy does not claim a separate end-to-end encryption review or certification.
Optional session recording is implemented in the codebase and is switched off (recordingEnabled is false). The designed behavior, when it is turned on, is that nothing is recorded unless both players accept, the host phone records the game screen locally, and the clip stays on that phone. The current app tells the host that nothing was uploaded. The API still contains older upload and private-storage code, with a default retention of 168 hours, for a recording file. The current iOS game path does not upload the session clip. Do not read this policy as saying that recordings are being made today.
8. Device information and app diagnostics
Product events can include the platform (iOS), app version, build number, OS version, device model, screen name, an install id, and a session id. The install id is not the same thing as your player id.
Diagnostics on the phone use Apple’s OSLog. The free-text detail of an application error stays on the device. The event sent to the API keeps a short safe property, such as a result or a reason code, and drops answer text, option ids, names, room codes, tokens, and URLs.
The API is served over HTTPS, and the live socket uses a secure WebSocket, except when a developer points a Debug build at a local server. The app does not ask for your location, contacts, or advertising identifier. The privacy manifest declares no tracking.
9. Push notification tokens and preferences
If you allow notifications, the app obtains a Firebase Cloud Messaging registration token and sends it to the API with an installation id, the platform, the app version, and the environment (development, staging, or production). One player can have more than one device.
The API uses that token to send a notification through Firebase Cloud Messaging and Apple Push Notification service. The notification payload carries an action such as opening home, creating a game, or joining a room. It does not contain your answers or a message you wrote.
You can turn notifications off in the app’s Settings, or in iOS Settings for Same Wavelengths. Signing out, switching account, or deleting the account deactivates that device’s token. A token has one active owner.
Notification preference is your choice. The app can invite you to allow notifications; it does not require them to play.
10. Crash reporting
Firebase Crashlytics is not part of the app. There is no Sentry, PostHog, or other third-party crash SDK in the project reviewed on November 18, 2026.
If the app crashes, Apple may offer you the chance to share a crash report with the developer through App Store Connect. That report is handled by Apple under Apple’s own terms. The app also writes local OSLog diagnostics that stay on the device unless you choose to share them.
11. Analytics and usage information
The app records product events so the operator can see whether people get through a game, where sign-in is offered, and when something fails. Events are queued on the phone and sent to the operator’s own API at POST /events/batch. This is not a third-party analytics product, and the app does not load an advertising or tracking SDK.
Events cover app opens and sessions, screens, creating and joining games, answers being submitted (without the answer itself), matches, completed or abandoned games, sign-in with Apple, settings changes, push permission, and errors. Unknown event names are rejected. Events are tied to your player id when you have a session, and stored without an account when you do not.
The in-app Settings screen says that Same Wavelengths records which screens you open, games you play, and errors that occur, and that it does not put passwords, tokens, or answer choices in that activity log.
There is no separate website analytics tool on this site. If one is added later, this policy and any required consent notice have to be updated first.
12. How information is used
Information is used to create your profile, run two-player games, connect the live video conversation, calculate compatibility and achievements, send notifications you have allowed, keep the service reliable, and protect accounts from misuse.
Sign-in information is used to recognize an Apple account and, when you delete it, to revoke the Apple grant if revocation credentials are configured. Profile photos are used to show your picture in the app. Statistics are used to show you your own history and, subject to your privacy settings, to show people you have played with.
Product events are used to understand feature usage and failures. They are not used to sell advertising profiles. The project reviewed here has no in-app purchases and no ad network.
Question text is written for the catalog. An optional AI provider can be configured for operators to draft questions. That tool is not the gameplay path, and player answers are not sent to it.
14. Third-party services and service providers
Apple. Sign in with Apple, the App Store, Apple Push Notification service, and crash reports you choose to share. Apple processes the identity token and, if you share one, the email address Apple provides.
Google Firebase Cloud Messaging. Used to deliver push notifications. The app includes Firebase Messaging for that token. It does not include Firebase Analytics or Crashlytics. Firebase’s handling of the token is covered by Google’s terms.
Google STUN. The default server that helps two phones connect a WebRTC call. It receives network addresses needed to establish the connection. It does not receive your answers.
TURN relay, only if configured. Not set in the reviewed project. The provider would be named here once one is chosen.
The operator’s API and database. The API is a NestJS service. Player, game, answer, statistics, event, and notification records are stored in MongoDB. Profile photos are files on the API server. The hosting company and the country where those servers sit are not named in this draft.
Optional AI question drafting. Operators can connect an OpenAI-compatible API to draft catalog questions. It is optional, it is not used to score your game, and player answers are not part of that request.
This website’s host. Whoever serves these pages may keep ordinary connection logs, such as IP address, date, and browser type. No host is named until the site is deployed.
15. Data storage and security
The hosted API uses HTTPS. Tokens on the phone live in the Keychain. The device secret and refresh tokens are stored as hashes on the server. Access tokens are JWTs that expire according to the server configuration. Signaling messages are limited in size and rate and are not stored.
Profile photos are stored as JPEG files addressed by the player id. Game answers are option ids tied to a round.
This policy does not claim that the database is encrypted at rest, and it does not claim a security certification. No penetration-test report is attached to this draft.
16. Data retention
Product events are deleted automatically 400 days after they are received. The in-app Settings text describes that period as about 13 months.
A guest profile remains until you delete it, you delete the app, or the Keychain entry is lost. An Apple-linked profile remains until you delete the account. Signing out of Apple on the phone does not delete the server profile.
Room records are for a live game and expire on the room’s two-hour lifetime when they are not used. Completed game sessions, rounds, and answer records are kept so the other player’s result and the statistics engine still make sense. Account deletion does not currently erase those session and answer rows. See the next section.
Local recording leftovers, if recording is enabled, are removed from the host phone after about 24 hours when the host does not delete them sooner. The unused server recording directory has a default retention of 168 hours.
Ordinary hosting and security logs do not have a retention period set in the product code reviewed here.
17. Account deletion and data deletion requests
You can delete a profile from the app. Open the Profile tab, tap the settings gear, then choose Delete account if you are signed in with Apple, or Delete guest profile if you are not. Confirm the prompt. There is no separate website form that deletes an account. The steps and the limits are explained on the Account deletion page.
When the server deletion succeeds, it removes the player profile, the profile photo, the Apple sign-in record, refresh tokens, product events stored for that player id, statistics, connection rows, discoveries, achievements, and push-token registrations. If Apple revocation credentials are configured, the server also asks Apple to revoke the stored grant. The account is still deleted locally if Apple cannot be reached.
Saved game sessions are not deleted. Your display name on those sessions is changed to “Deleted player.” Answer rows, which store the selected option id and player id, are not deleted by the current erasure flow. The other player’s completed game remains. Notification delivery history can remain with the player id removed. Administrative audit logs are not deleted and may still contain a player id.
For an Apple account, if the server deletion fails, the app shows an error and the account stays. For a guest, the iPhone profile is still removed even when the server cannot be reached, so a guest record on the server can remain until a successful request.
A privacy contact email has not been published yet. Add privacyEmail in the site configuration before publication.
18. Your rights and privacy choices
You can change your display name and avatar in Profile, remove your profile photo, turn sound and haptics on or off, and change notification permission. Wavelength privacy toggles control friend-facing statistics, leaderboards, achievement sharing, and statistics sharing.
You can play as a guest, sign in with Apple, sign out, or delete the profile. Signing out leaves the Apple account on the server and keeps the name on the phone as a guest until you sign in again.
Depending on where you live, you may have rights to access, correct, delete, or export personal information, or to object to certain uses. This draft does not list country-by-country rights because the operator’s country and the countries where the app will be offered are not confirmed. Those rights, where they exist, are not waived by this policy.
A privacy contact email has not been published yet. Add privacyEmail in the site configuration before publication.
19. International data transfers
The API, MongoDB database, Firebase Cloud Messaging, Apple, and Google’s STUN service can process information in countries other than yours. The countries used for the operator’s own servers are not recorded in this draft.
No transfer mechanism, such as standard contractual clauses, is named here because the hosting region and the operator’s establishment are not confirmed.
20. Children’s privacy and age restrictions
A minimum age has not been set. The iOS app does not ask for a date of birth and does not block use by age. This policy cannot honestly name an age until you choose one and, if you want it enforced, add that check to the app.
The app is a social game for couples and friends, with a camera and microphone. It is not directed at young children, and the operator does not knowingly want children’s profiles. Because there is no age gate, the operator cannot honestly claim that no one under a given age has used the app.
If you believe a child has a profile and you want it removed, use the contact method in the last section. Include enough detail for the operator to find the player. Do not send a copy of a government ID to the public website; this site has no secure upload.
21. Changes to this policy
The “Last updated” date at the top of this page is November 18, 2026. When the policy changes, the operator will update that date and the page. The app does not currently show an in-app acceptance dialog for privacy-policy changes.
If a change affects recording, analytics, a new sign-in provider, or a new SDK, the policy and Apple’s privacy details need to be updated together.
22. Contact
A privacy contact email has not been published yet. Add privacyEmail in the site configuration before publication.
Support questions go to the address on the Support and Contact pages. If no email is shown, the address has not been published, and this draft is not ready to ship.
Write to the privacy contact for access, correction, or deletion requests when you cannot use Delete account or Delete guest profile in the app. The operator may need your player display name, and whether you used Sign in with Apple, to find the right profile. There is no public player id in the app for you to copy.