ohhey Privacy Policy

Effective date: November 5, 2026

Last updated: November 5, 2026

Document version: 1.0.0

1. Who we are and what this policy covers

Can't Get Back Time LLC, an Illinois limited liability company, operates ohhey. This policy describes how we collect, use, disclose and handle information in our mobile applications and public invitation pages. It also explains choices and how to contact us about privacy. It covers account holders, people who view public invitations without an account, and people whose information we receive through Contacts matching, invitations, reports or correspondence. We are responsible for deciding how ohhey uses the information under our control. This policy is a notice of our practices, not a request for blanket consent to every type of processing. Accepting the Terms or viewing a public page does not replace a separate permission or consent required by law.

For privacy questions or requests, contact support@ohhey.app. For safety or moderation concerns, contact report@ohhey.app.

2. Information we collect and its sources

Account information includes a username, given name, optional last name, full birthday, phone number and verification/account identifiers. A profile photo is optional. Account and verification information is needed to create and maintain an account; you may view an available public invitation without creating one. We use your birthday privately for age eligibility; we do not publish it in profiles, invitations, discovery results or push notifications.

Invitation and relationship information includes invitation text, privacy choices, selected direct recipients, responses, follow relationships and requests, blocks, and related timestamps. We also maintain invitation history, activity and notification settings, including per-invitation mute choices.

When you contact support or moderation or submit an in-app report, we receive the information you provide, along with account, target and operational information needed to handle the request. Avoid including verification codes or unrelated sensitive information in reports or emails. Legal complaints and privacy requests may also include contact details, a signature, authority to act for someone else and limited verification information where needed for the request.

Information comes from you, your device and interactions with the Service, the providers described below, and other people using ohhey. Other people may supply information about you through invitations, responses, follow relationships, reports or correspondence. Contact-book numbers may concern people who do not have an ohhey account and are handled transiently as described in section 3.

Invitation text, photos and correspondence can contain personal or sensitive information that you choose to include. The audience and purpose of the feature determine how we handle it; including sensitive details does not authorize unrelated uses. Avoid sharing unnecessary sensitive information about yourself or anyone else.

3. Optional Contacts discovery

Contacts discovery requires an explicit action and the access you grant through your device. Where supported, you can permit selected contacts instead of your full address book. We read only permitted phone numbers for matching. We do not send your contact-book names, email addresses, photos, mailing addresses or notes to our matching service.

Permitted phone numbers are normalized and sent over encrypted transport for an explicit match request. Uploaded address-book numbers are used transiently for matching and are not saved as an address book, permanent unmatched list or request-body log. The service uses a secret-keyed matching index for registered accounts; it does not publish a directory of phone numbers.

A person who already has your registered phone number may find your permitted basic profile through Contacts discovery, subject to account and block rules. We do not reveal your phone number to them. A match does not create a follow, send an invitation, add someone to your recipients or bypass invitation access rules. We do not scan Contacts in the background.

Turning off your own Contacts permission stops future device access for this feature; it does not stop someone else who already has your registered number from finding your permitted basic profile through their own authorized match request. A private account is not an opt-out from phone-number matching.

You can decline Contacts access and use username/given-name search. You can change available access in device settings. If parental or device-management restrictions apply, your device may not offer a permission switch.

4. Photos

Profile photos are processed into a resized, sanitized image for display. The upload pipeline removes original image metadata and does not publish the unprocessed original. We do not use profile photos to perform facial recognition or create biometric identification templates.

A profile photo is part of the permitted basic profile shell. Access remains subject to current account, photo-reference and block checks. Removing or replacing a photo stops ordinary access to the old reference, while physical cleanup of the retired object follows the applicable deletion schedule.

5. Device, security and operational information

To operate and protect the Service, we and our infrastructure providers process information such as account and installation identifiers, push-notification tokens, permission/preferences, IP addresses, user-agent information, request timestamps, limited error/operation information and app/device attestation signals.

These records support authentication, access controls, abuse prevention, rate limits, reliable delivery, troubleshooting and safe retries. We avoid placing birthdays, contact books, verification codes, private invitation content or tokens in application logs or notification wording.

A visit to a public invitation page can generate hosting, network and security records, including an IP address and request information, even if you do not sign in or respond. These records do not by themselves identify a visitor as a particular ohhey account.

Version 1 does not use advertising trackers or precise device-location collection. Firebase Analytics, Crashlytics and Performance Monitoring collection are disabled in the current app configuration. This does not mean that essential authentication, hosting, delivery or security infrastructure processes no technical data. Any materially different collection or advertising feature would require a policy update and any consent required by law.

The current public invitation page does not set application cookies or use browser local storage to retain invitation content. It temporarily holds authorized content and photos in memory for display; that is separate from provider request logs. Authentication, app integrity and device notifications use technical identifiers and local state needed for those functions. Google's phone-verification flow may include an external reCAPTCHA security check when required, whose processing is governed by Google's applicable terms and privacy notice.

Our current public invitation page does not change its behavior in response to a browser's Do Not Track signal. We do not use that page to track visitors across other companies' websites for advertising. Do Not Track is distinct from legally recognized opt-out preference signals, such as Global Privacy Control. Because version 1 does not sell personal information or share it for cross-context behavioral advertising, there is no such activity for a signal to opt you out of. We will honor applicable legally required opt-outs if our practices change.

6. How we use information

We use information to:

• Create, verify and maintain accounts and enforce age eligibility.
• Display authorized profiles and provide search and explicitly requested Contacts matching.
• Create and deliver invitations, enforce audiences, record responses and maintain history and totals.
• Handle follows, requests, blocks, reports and safety restrictions.
• Deliver permitted notifications and route authorized links.
• Respond to support, privacy and deletion requests.
• Protect the Service, investigate misuse, resolve errors and comply with specific legal obligations.

We do not use your private birthday or uploaded contact-book numbers to send marketing messages. We do not sell personal information or share it for cross-context behavioral advertising in version 1, including personal information of users under 16.

We use automated rules for age eligibility, invitation permissions, matching, security and abuse limits. We do not use version 1 to make automated profiling decisions about eligibility for employment, housing, credit, insurance or similarly significant opportunities. If you believe an account or privacy restriction is mistaken, you can contact support@ohhey.app for review.

7. What other people can see

Your basic profile can include your given name, username, current photo, account privacy and aggregate follow counts. A private account does not make this basic identity entirely invisible. Access to additional profile details depends on the applicable profile/account rules. Your phone number and birthday are not public profile fields.

Invitation privacy is separate from account privacy. A public invitation can be viewed by anyone with its valid link. The anonymous page shows invitation text, a limited creator shell, sent time and aggregate response totals, without the complete guest list or individual guest responses. Signing into the app is required to respond. A private-account owner can still create a public invitation.

Follower-only and super-private invitation content is not shown through the public web page. App access depends on current authorization. A directly selected recipient and a valid responding guest may retain access after unfollowing, subject to account and block rules. People who are merely able to view a broader invitation do not automatically receive an inbox entry or push notification.

Authorized signed-in viewers can see the permitted roster and responses. On a third person's invitation, a guest who created a block can still see the blocked guest's limited name/username and response for attendance safety, without restored photo/profile access. The reverse-only view is anonymous and does not reveal the blocker's individual response. A block between the creator and viewer denies access to the invitation. An anonymous public visitor cannot be identified as a person who previously blocked or was blocked by someone.

A public invitation is not confidential merely because its link is difficult to guess. People can forward the link, and we cannot guarantee that public information will never be indexed, copied or republished outside ohhey.

Recipients can copy information or take screenshots outside the Service. Choose your audience and invitation wording accordingly.

8. Service providers and other disclosures

We use Google Firebase/Google Cloud for services including authentication, data and photo storage, trusted processing, hosting, app integrity and notification delivery. Apple and Google also operate device/app services used for attestation and notification delivery. These providers receive the categories needed for their functions: account and phone-verification information for authentication; profiles, invitation content, relationships and photos for authorized storage and delivery; and device identifiers, attestation signals, network information and notification payloads for security and messaging. Not every provider receives every category. Provider agreements and applicable policies govern their processing; some processing, including the Google phone-number use described below, serves provider security purposes as well as ohhey's operation. We remain responsible for our own obligations when selecting and using providers.

Phone numbers used for Firebase Authentication are sent to and stored by Google to improve spam and abuse prevention across Google services, including Firebase. That processing is disclosed before verification texts are requested. Google describes relevant processing and retention here:

https://firebase.google.com/docs/auth/ios/phone-auth
https://firebase.google.com/support/privacy
https://policies.google.com/privacy

When you use an external mail application to contact us, your mail provider and our email provider process the message as part of delivery. We do not automatically email every in-app report to a public mailing list. Ordinary in-app safety reports are not disclosed to the reported user through the reporting feature. A separate legal complaint, copyright notice or counter-notice may need to be forwarded to the relevant claimant or affected person, including contact details where the legal process requires them. Our Terms describe the copyright process. We limit disclosure to information appropriate to that process and applicable law; the ordinary report-confidentiality rule is not a promise of anonymity in legal proceedings.

We may disclose information when a valid legal process requires it or when a disclosure is otherwise permitted by applicable law and reasonably necessary to address a serious security or safety issue. We evaluate the request and disclose only information appropriate to the circumstances. We may also need to transfer relevant information as part of a lawful corporate reorganization or business transfer, subject to this policy and applicable notice, consent and privacy obligations. These provisions do not authorize unrelated advertising use.

9. Notifications

When you enable user-visible push notifications, we register a device/installation token and applicable permission/preferences. Notification delivery follows your response, mute and account settings and the applicable cancellation rules. Turning off push does not hide invitations or activity or change invitation access.

Push wording is minimized so it does not disclose private guest lists, block facts, membership or relationship details. Delivery providers still process technical delivery information and the notification payload. Phone-auth verification messages or silent authentication notifications are separate from optional invitation alerts.

You can manage push preferences in the app and alert permission in device settings. Signing out clears local account-sensitive state and initiates device-token unregistration. If the device cannot connect, server-side cleanup cannot be confirmed immediately; the app will not claim otherwise. No token-cleanup process grants ordinary signed-out access to private account content.

10. Account records, retention and deletion

During account use, we retain records needed to provide the Service, including invitation history. Retention depends on the record's purpose, whether it remains needed for an active feature or request, disclosed provider schedules and specific legal obligations. We must not retain information longer than reasonably necessary for its disclosed purpose. The 30-day period below applies after an accepted account-deletion request; it is not a claim that every kind of technical record is ordinarily kept for 30 days. Cancelling an invitation retains its history; cancellation is not account deletion.

You can request account deletion from edit profile in the app. We may verify ownership before accepting it. After acceptance, your account closes, ordinary access and visibility stop, and your account data under our control is retained privately for 30 days. At the end of that period, the records become due for automatic erasure through our daily deletion process. The scheduled date is the retention deadline; it does not mean every deletion operation finishes at that instant. Processing time and retried failures may delay completion, with access remaining closed. We must address failures and complete erasure without undue delay, subject to any earlier deadline required by law. In version 1 the request is final and cannot be cancelled; the retained account cannot be restored. The accepted request and scheduled date are shown in the app. Repeating an uncertain request does not restart the retention period.

Account erasure covers account identity and private profile data, birthday, photos, relationships, account-linked invitation/participation records, discovery indexes, notification registrations/preferences, activity and reports, and related operational records, to the extent they are your personal information under our control. It removes your owned invitations and personal participation records in other people's invitations while preserving their independently supplied content. Shared references must be handled without exposing others' private information. Truly independent copies saved by others outside ohhey are outside our control.

SERVICE-PROVIDER TIMING: The 30-day period above concerns ohhey-controlled account records. Google's published Firebase policy states that certain Authentication data and installation identifiers may take up to 180 days to be removed from live and backup systems after the relevant deletion request/API call. Firebase Hosting also describes IP-log retention lasting a few months. These provider periods begin with the relevant provider deletion request or API call, not necessarily with your in-app request. In the current account-deletion process, Firebase Authentication user deletion is initiated during account erasure after the 30-day hold, so its published period can run for up to 180 additional days after that operation. It is not a promise of complete provider erasure within 180 days of your original account request. Other provider cleanup depends on the relevant service and deletion operation. Profile photos are removed from live storage during account erasure; the current Google Cloud Storage soft-delete policy retains deleted copies for seven additional days, without app access. We must submit relevant provider deletion requests and accurately disclose their timing; we cannot promise physical erasure of all provider-held copies within 30 days using the present services.

A specific applicable legal obligation or valid preservation requirement may require some records to be handled differently. Any such preservation must be limited to the records, access and duration actually required; this is not an indefinite general exception for ordinary account data. Where law requires earlier removal, that requirement takes priority. We remain responsible for handling requests for information we control and for our obligations when using service providers.

Account-related support and legal correspondence in email systems must also be addressed when handling deletion and privacy requests; the database-erasure worker does not automatically erase those mailboxes. We remain responsible for information under our control in those systems.

Backup, security-log, correspondence and report retention remain limited by the purposes, schedules and specific legal obligations described in this policy. These provisions do not authorize indefinite retention.

11. Your choices and privacy requests

You can edit supported profile fields, choose account and invitation privacy, manage follows and blocks, control optional Contacts and notification access, and request deletion. Turning off a permission does not itself delete your account or reverse processing already completed. If a feature relies on consent, you may withdraw that consent through the relevant control or by contacting us; this does not affect the lawfulness of processing before withdrawal. Essential processing needed to provide an account, protect the Service or meet a specific legal obligation is separate from optional device permissions. You may contact support about information concerning you even if you have no account or cannot sign in.

Depending on where you live and which laws apply, you may have rights to learn whether we process your information; access it or obtain a portable copy; correct inaccuracies; request deletion; restrict or object to particular processing; opt out of sale, targeted advertising or qualifying profiling; limit certain uses of sensitive information; appeal a request decision; or contact a regulator. Not every right applies in every jurisdiction, and version 1 does not perform the advertising or significant-opportunity profiling described above. Contact support@ohhey.app to make a request. We may request proportionate ownership verification; do not send a verification code or unnecessary identity document by email. Please describe the request and provide enough information to locate the relevant account or records. We use verification information only as needed to verify and handle the request, protect against fraud and meet legal requirements. We will handle applicable requests within the period required by law, notify you of a lawful extension and explain any legally permitted refusal or limitation. A privacy request does not require deletion of your whole account unless that is needed for the action you request.

To appeal a privacy-request decision where an appeal right applies, email support@ohhey.app with the subject "privacy appeal" and identify the request and reason for appeal. We will review it, respond within the applicable legal period, and provide any required information about further complaint or regulator options. This does not require you to appeal before exercising another right the law provides.

We will not require you to waive privacy rights to receive support or retaliate for exercising rights protected by applicable law. An authorized representative may contact us where applicable law permits; we may verify the representative's authority.

12. Children and age eligibility

ohhey accounts are for people 13 or older. We collect a private birthday to check age eligibility; a statement of age does not excuse us from obligations that apply if we learn that a person is under 13. If you believe a child under 13 has provided personal information, contact support@ohhey.app. We will investigate and take the action required by applicable children's privacy law, including removing information where required. We do not claim that a blanket 30-day retention period overrides a requirement to act sooner. A parent or guardian may contact us about a child's information, subject to appropriate verification and applicable rights. For teenagers, any required consent, parental rights and privacy protections depend on applicable law. A person's status as a parent or guardian does not automatically grant access to another account's private invitations or other users' information.

13. Security

We use measures intended to protect information, including encrypted transport, trusted server authorization, device/app integrity checks, access-restricted storage and minimized public/notification responses. No system or transmission is guaranteed to be completely secure. Protect your device and verification codes and contact support about suspected unauthorized access. If a security incident requires notice to affected people or authorities, we will provide that notice as required by applicable law.

14. Where processing occurs

Can't Get Back Time LLC is based in Illinois. Our current backend data region is in the United States, but infrastructure, support, authentication, messaging and security providers may process information in the United States and other locations described in their service arrangements. Choosing a database region does not mean that every provider operation or backup is restricted to that region. We remain subject to applicable obligations concerning these arrangements.

15. Changes to this policy

We will update this policy when practices change and identify when revisions take effect. We will provide appropriate notice of material changes and obtain consent where required. We will not treat a policy update as permission to make an undisclosed new use of information already collected without satisfying applicable requirements.

16. Contact

Can't Get Back Time LLC
Illinois, United States

Privacy, support and account-deletion questions: support@ohhey.app
Safety and moderation: report@ohhey.app