Privacy Policy
Dear Orbit is operated by an individual based in Egypt. This policy describes the information handled to run the platform and how to contact us about it.
Information we handle
We handle your account email and authentication information, the messages and names you enter into gifts, photographs and other creation content, draft and publication records, and support messages you choose to send.
Checkout records include billing country, currency, amount, provider references and payment status. Where Paymob checkout is enabled, it may also require the billing name and phone number to process payment. Card details are entered with the approved payment provider, not stored as card numbers by Dear Orbit. Paddle collects payment details through its own checkout for purchases it processes.
How information is used
We use information to create and store your drafts, render and share published experiences, authenticate your account, verify payment and publication access, send account or experience-link emails, respond to support requests, operate the service and address misuse or technical problems.
Our product-event records can include account, journey or creation identifiers, selected occasion, relationship or mood, music choice, country, interaction steps, duration and error information. The product-event schema excludes free-form gift messages, photo URLs and precise geolocation. This does not mean hosting providers never receive network information when serving a request.
Anonymous gift reactions
Recipients may optionally choose one of three predefined reactions to an active published gift. Reactions do not ask for a recipient name, email, free-text comment or media. The creator sees aggregate counts for their own gifts, not recipient identities.
A random browser cookie, unavailable to page scripts, lasts up to 180 days to help prevent repeat reactions. Reaction records store a hash scoped to that gift. Request network information is used transiently for daily rotating, keyed abuse limits; we do not store an IP address or device fingerprint as a reaction identity. Clearing browser storage or using another device can defeat anonymous deduplication.
Product events record reaction and return-gift progression using the existing bounded journey identifiers, without private gift text or photographs. Demos and editing previews do not submit recipient reactions. Unpublishing prevents new reactions and disables the shared experience.
Drafts, photographs and shared links
Draft access is restricted through account authorization. Uploaded photographs are processed into optimized copies with embedded metadata removed and stored in private media storage.
Publishing deliberately makes the experience available to anyone with its unlisted link. The link is not password protected, and recipients can forward it. Recipient pages request that search engines do not index them; this is not a guarantee against discovery or copying. Obtain permission before uploading another person’s content and avoid highly sensitive information.
Service providers and browser storage
The hosted service uses Vercel for website hosting, Supabase for authentication, database and private media storage, and Resend for configured transactional email delivery. These providers process information needed for their functions. They may process information outside Egypt under their own service arrangements.
Paddle handles purchase information as Merchant of Record when its checkout is used. Its own privacy notice applies to that processing. When enabled, Paymob processes Egyptian transactions and the related billing details under its applicable privacy notice. Live Paymob transactions are not enabled until onboarding is complete. We use authentication cookies and browser storage for functions such as sign-in, region selection and experience preferences. Your browser can clear this storage, although that may sign you out or reset preferences.
Deletion, retention and requests
You can unpublish or delete a creation and request account deletion through My Creations. Creation deletion removes the published snapshot and associated stored media and clears the main personal message fields. Copies previously saved by recipients remain outside our control.
Deletion is not a promise of immediate erasure from every operational record, log or provider backup. We do not promise a fixed retention or backup-erasure period. Transaction and service providers may retain records under their applicable requirements. Contact us for information about your data or to request access, correction or deletion; applicable rights depend on your circumstances and local law.