Names, recognition photos and messaging access depend on reciprocal Signals, both Continue decisions, saved reveal timing and continuing account permissions.
Who is responsible
David Stein operates KYSS and is the privacy and safety contact: david@steindavid.com. This policy describes the KYSS beta member app and its account, proximity, messaging, support and subscription services. The version shown above is the version acknowledged during sign-in.
Information you give us and information created by KYSS
Information you give us
We collect your email address for passwordless access and confirmation of sensitive account actions. Setup and profile information includes your display name, birthday, gender, recognition photo, bio and selected connection preferences.
Relationship context and preferences about whom you wish to meet can reveal sensitive information, including sexual orientation or practices. Messages, reports and support requests can also contain sensitive information. Provide only what is needed and do not include another person’s sensitive information without authority.
We use the preferences you choose to assess mutual eligibility for discovery and to show relevant context before a connection proceeds. Your birthday supports the adult declaration; ordinary profile editing does not change the birthday recorded during setup. Contact support if that record is wrong.
Information created when you use KYSS
The service records account and device sessions, temporary nearby identifiers, active Orbit time, Signals, mutual and Continue decisions, saved reveal timing, messages, blocks, reports and requests. It also uses network and security information, such as request IP addresses, timestamps and delivery or error records, to operate and protect the service.
Bluetooth supports nearby discovery. Names, photos and relationship preferences are not broadcast as Bluetooth identifiers. The radar does not use GPS coordinates to place dots. The service uses observed temporary identifiers to check eligible nearby accounts; it is not a history for browsing everyone you passed.
Apple subscription records support purchase verification, expiry, cancellation-related access changes and abuse prevention. KYSS receives transaction identifiers, product and entitlement information; Apple handles the payment method. Push registration and notification records support the alerts you enable.
When you successfully sign in or create an account after ticking the agreement box, KYSS records the Terms and Conditions version, Privacy Policy version and the server time against your account. This records your terms agreement and privacy acknowledgement for that sign-in. It is separate from marketing choices, device permissions, sensitive-information choices and permission to reveal your profile. Account-deletion handling also applies to this record.
What other members can see
People in Orbit see eligible anonymous signals and any clue you deliberately share for that Orbit. A clue is visible before a mutual and can make you recognisable. One-sided interest is not disclosed as an admirer notification.
After reciprocal Signals, the required relationship context is shown before either person independently Continues. Name, recognition image and messaging access depend on both Continue decisions, the saved reveal timing and continuing account permissions. Blocking or a closed connection prevents future authorised access; it cannot retrieve a copy another person already saved.
Photos, automated checks and service providers
Photos and automated safety checks
Your recognition photo is held in private storage, with prepared image versions for the app. A pending replacement is separate from your current image. KYSS sends an image needed for automated safety analysis through its photo-checking service to AWS Rekognition.
The analysis checks content safety and can return image-quality warnings. Ordinary quality warnings let you choose whether to use the photo. This process does not verify identity, liveness or adulthood and is not routine human portrait approval. Specifically authorised handling of a report, appeal or consented safety review can include the relevant image and context.
Text checks on bios, clues and messages help restrict prohibited content; they are not a guarantee that every harmful expression will be detected. The adult-check screen describes a separate age-only service if one is offered. Do not send identity documents to the support email; any separately enabled age service must explain its own collection and purpose first.
Service providers and overseas handling
DigitalOcean provides the configured private photo storage; the supplied beta configuration selects Singapore. Resend delivers account and service emails and states that it stores message and related service data in the United States. AWS Rekognition photo analysis is configured for the Sydney region in the documented photo service. Apple provides iOS notification delivery and App Store purchases.
These providers receive information needed for their roles. For example, email delivery needs the destination and message, photo analysis needs the submitted image, and notifications need the device routing information and permitted notification content. If you enable message previews, private message content can be included in a notification and appear on your lock screen.
Service-provider and support operations can involve overseas processing. The complete hosting, mailbox, backup and provider-location inventory remains under review. This policy does not claim that all information stays in Australia. KYSS’s recorded AWS service-improvement opt-out must remain in place; it is separate from keeping the operational data needed to provide the service.
Operator access and security
Access by the operator and authorised reviewers is limited by purpose and permissions. A report, appeal or request may need review of relevant records; another member is not given staff notes or the reporter’s identity through that process.
We use protected connections, private storage, access controls and encryption for selected stored information. KYSS is not an end-to-end encrypted messaging service. No system can guarantee that information will never be accessed without authority. Keep your device, email and any saved export or receipt secure.
Retention schedule under review
The periods below are proposed operating limits and targets for this beta. They have not become public promises by being included in an installed app. The deletion preview shows the specific policy associated with an accepted request. Records should not be kept longer merely because a maximum period exists.
| Information or stage | Proposed handling |
|---|---|
| Account access after confirmed deletion | Withdraw access and discovery immediately. |
| Eligible profile, preferences and your authored content | Complete ordinary cleanup within 7 days of confirmation. |
| Obsolete or abandoned private photo copies | Remove within 24 hours of becoming eligible, except a specifically justified evidence hold. |
| Account exports | 15 minutes of server access; remove expired or revoked server copies within 24 hours. |
| Expired codes and ended Orbit protocol records | Clean up eligible records within 24 hours after expiry or their remaining live purpose ends. |
| Diagnostic and security logs | Target 30 days from the event. |
| Routine support correspondence | Target 90 days after resolution. |
| Dismissed or no-action safety cases | Only while needed, up to 90 days after case and appeal closure. |
| Serious or substantiated safety cases | Only while needed, up to 12 calendar months after case and appeal closure; final review required. |
| Necessary financial records | Restricted transaction fields for up to 5 calendar years from the reviewed transaction date; final review required. |
| Routine backups | Proposed maximum 30 days from creation; actual inventory must be confirmed. |
| Private deletion progress receipt | 90 days of access. This is not an erasure deadline. |
Exceptions and copies that last longer
A specific safety, financial or legal need can justify keeping a limited record after ordinary cleanup. We must identify the reason, the records needed, who authorised the hold, when it will be reviewed and what ends it. Proposed hold reviews occur at least every 90 days. A general note is not a reason to keep an entire account indefinitely.
A backup taken near the end of a 7-day cleanup period could remain until about day 37 if the proposed 30-day backup limit applies. Separately justified records can last longer. Limited deletion records also prevent a backup restore or later purchase event from recreating a closed account; their need must be reviewed.
Deleting a server copy cannot recall messages or photos someone independently saved, an export you saved, or email in a recipient’s mailbox. Those limits must not be used to claim that incomplete KYSS cleanup is finished.
Access, correction, withdrawal and complaints
Open Account & data controls for available session, export and deletion actions. An export provides your own supported account data and authored content without disclosing other people’s private decisions or authored messages. Photo files are not included in that export. Ask the privacy contact about information not included or a correction you cannot make in the app.
You can remove an optional clue, change supported preferences, pause or end Orbit, disable notification previews, withdraw device permissions and request deletion. A required field or permission may be needed to use its related feature. Withdrawing a choice cannot undo a disclosure that already occurred.
For a privacy complaint, email David Stein with the issue and the outcome you seek. We will assess the concern, seek only information needed to establish ownership or investigate, and respond with the outcome or next step. No fixed response deadline is promised by this beta policy.
Changes to this policy
Material changes require an updated version and appropriate notice or acknowledgement. The sign-in record identifies the version shown for that attempt; it does not backdate agreement for an earlier session. The retention periods explicitly labelled as proposed remain under review and are not activated by the agreement checkbox.
Questions or concerns?
Email David Stein with the issue and the outcome you are seeking.