Skip to content
DOS.
Discover
Discover
How DOS works→People nearby→Profiles and social links→Visibility choices→DOS in Iași→About DOS→
Community
Community
For students→Student guide→Business pilot→Community guidelines→
Guides
Guides
All guides→Social discovery→Meet people in Iași→Location privacy→Student connections→
Safety
Safety
Safety center→Privacy→Data requests→Report a concern→Delete account→
Help
Help
Help center→FAQ→Contact→Accessibility→Terms and cookies→
Join early access
ROJoin early access
Home/Safety and help
DOS · Legal

Privacy policy

Understand how DOS handles your information, how location sharing works and the choices available to you.

Last updated 10 October 2026
On this page
Location sharing by app version1. What we collect2. How we use data3. Lawful bases4. Sharing with third parties5. Retention periods6. Your rights7. Cookies8. Security9. Children10. International transfers11. Changes12. Contact13. Optional public web card
Privacy policyTerms of serviceCookie policyData requestsContact DOS

Location sharing by app version

DOS 1.0.6 beta is a test version. If you have this version installed, you choose when to start each new Nearby sharing session. Before sharing, DOS explains who can see your profile and approximate distance and gives you a choice to continue or stay hidden. Device permission, signing in or opening DOS alone does not start a new sharing session. Sharing while using DOS ends when the app goes to the background; there is no 15-minute timer in this version.

Background discovery is a separate, optional choice. After you accept its explanation and grant Always (or All the time) and Precise Location permission, DOS can use location while the screen is locked or you use another app. This sharing session continues until you stop it or sign out. Reopening DOS may continue the same previously authorized session for the same account; it does not create a new check-in. Phone restrictions, lost connectivity or force-closing DOS can delay or stop updates.

DOS compares fresh location samples on its server. Nearby people can see your public profile and approximate distance, not exact coordinates or a map pin. Recent encounters can remain in signed-in Alerts for up to 3 hours; this is separate from whether you are currently visible and from saved favorites. Nearby push previews are generic.

To end the sharing session, turn off Nearby visibility, Background discovery or Location in DOS Settings, or sign out. Revoking location permission in the phone settings pauses updates; restoring the required permissions may continue a previously authorized background session unless you also stopped it in DOS. Using the DOS stop controls clears the session and disables local updates. If a stop request cannot reach the server, the last accepted sample stops qualifying for discovery once it is more than three minutes old.

To block someone, open their profile, open the three-dot menu and choose Block. Manage blocks in Settings → Blocked users. Blocking prevents discovery between both accounts. DOS is for adults aged 18 or older.

iOS 1.0.5 builds 56–58

On iOS 1.0.5 builds 56–58, Nearby uses a manual check-in of at most 15 minutes while DOS is open. Leaving the app ends that session; returning, restarting or signing in does not start another. Background discovery is unavailable in those iOS builds. Older Android releases may have different controls. Check your installed app version and the explanation shown before sharing.

1. What we collect

  • Account information — your name, account email, account identifier and sign-in provider information; date of birth, age and gender used for an adult profile. A waitlist email is separate and optional.
  • Profile and page content — profile photos; optional biography, interests, education, social handles and links; content you add to your public web card, including photos, media links and product information.
  • Business details — public contact phone, address, opening hours, links and descriptions if you add a business or contact option.
  • Location — approximate or precise location with your device permission for nearby discovery. In DOS 1.0.6 beta on iOS and Android, Background discovery requires a separate opt-in and the required device permissions. It is optional and off until you enable it. See the version-specific sharing rules above.
  • Support and safety content — questions or messages you send to support, reports, appeals and privacy requests.
  • Usage and device information — account and installation identifiers, notification tokens, app versions, relevant technical logs, and interactions such as profile actions, favorites and business engagement.

2. How we use data

  • Provide app features (Nearby, notifications, profile).
  • Compare fresh location samples on our server to detect nearby encounters between visible, participating adults. Exact coordinates are not published on public profiles or included in encounter notifications.
  • Support and replies to requests.
  • Abuse prevention and security.
  • Basic analytics for stability and quality.

3. Lawful bases

  • Consent — for location and optional communications.
  • Contract — to provide the requested service.
  • Legitimate interests — safety, fraud prevention, improvements.
  • Legal obligations — when applicable.

4. Sharing with third parties

We do not sell personal data. Google Firebase provides account authentication, database and photo storage, cloud functions and notification delivery. OpenAI processes submitted photos for safety moderation and relevant text when you use optional AI biography or support features. These services process the data needed to perform those functions.

Social account previews may request a public handle from unavatar.io; website icons may request a domain from Google's favicon service. These requests disclose that handle or domain and normal connection information to the provider. They do not disclose your DOS password.

Your public profile information and social links are visible according to your settings. Publishing a web card makes the content you select accessible to anyone with its link. Opening a social link, external shop, WhatsApp link or embedded media connects you to that external service, whose own privacy practices apply. Exact coordinates are not shown on public profiles.

5. Retention periods

  • Waitlist email: until withdrawal or launch + 6 months.
  • FCM tokens: until revoked/replaced.
  • Google Cloud Logging currently retains logs in the default bucket for 30 days and required audit logs for 400 days. Other support, security and provider records can have different retention needs; these Cloud Logging periods are not a single retention period for all DOS data.
  • Profile data: until account deletion or upon your request. Account deletion removes your sign-in account, profile, public web card, active photos, device and location records, notification preferences and other account-owned content. Limited deletion audit records and records needed for security, legal compliance or shared business continuity may remain; they are not kept as an active public profile.
  • Profile photos removed from the app may remain recoverable in restricted cloud storage (soft delete) for up to 7 days after they are deleted from active storage. These recovery copies are unavailable in the app, can be restored only by authorized cloud administrators, and expire at the end of that period. This photo recovery period does not change the retention periods for other account data.
  • Current location samples are assigned an expiration target approximately 10 minutes after an update. Automatic server deletion is configured for expired location samples. Cleanup is asynchronous: the expiration timestamp is not a guarantee of physical deletion at exactly 10 minutes, and expired records can remain stored while cleanup is pending. Matching uses fresh samples, not a public movement trail.
  • Recent nearby encounters appear in the recipient's signed-in notification history for up to 3 hours from detection. They may include the other person's public name, photo, profile link and approximate distance. Expired encounters disappear from the app; server-side cleanup may take longer.

6. Your rights

  • Access, rectification, erasure.
  • Restriction and objection.
  • Data portability.
  • Withdraw consent (e.g., location) anytime.
  • Turn off Background discovery, location or visibility in DOS Settings, or revoke location access in your device settings. Background discovery requires a separate opt-in; accepting these terms does not enable it.
  • Complain to the competent authority.

To exercise your data rights, use the DOS privacy request page or email us at info@dos-web.com. We may ask you to verify account ownership before responding.

7. Cookies

We may use technical cookies for operation (e.g., preferences, abuse protection). No third-party marketing cookies without consent.

8. Security

We use reasonable measures: HTTPS, access rules, logging, anti-abuse. No method is 100% secure; we improve continuously.

9. Children

DOS is intended only for people aged 18 or older. People under 18 must not create or use a DOS account.

10. International transfers

The current Firestore database is located in europe-west1, Belgium. The profile-media bucket configured for DOS is located in us-west1, United States. Provider support and authorized remote administration may involve additional international access. Applicable safeguards must be assessed for each relevant transfer; choosing a European database region alone does not keep every part of the service in the EEA. Contact DOS for information about the safeguards applicable to your data.

11. Changes

We may update this policy. The current version and “Last updated” date are on this page.

12. Contact

Privacy email: info@dos-web.com

We respond as soon as possible.

Background discovery and notifications: The operating system decides when background updates and notifications are delivered. Background discovery is available only in versions that provide the separate opt-in described above. Accuracy, power-saving settings, network conditions and force-closing the app can delay or stop discovery. DOS does not bypass system permission prompts, location indicators or reminders. Nearby push previews are generic; encounter identities are shown in the signed-in app. Your device settings control lock-screen visibility and sound.

13. Optional public web card

Publishing a web card is optional and off until you choose to publish it in DOS. Anyone with the published link can view the public name, biography, approved photos, public details, social links and optional photo, media and product blocks you add. Your account email, age and exact location are not automatically included. Contact information you deliberately add as public content is visible.

Product buttons open your chosen external shop or WhatsApp; DOS does not process checkout on the card. External media loads from its provider when activated. Publishing does not enable nearby discovery. Unpublishing removes live availability but cannot remove copies or screenshots already saved by others. Web cards are marked for search engines not to index, and DOS does not load optional analytics or advertising trackers on the card page.

DOS.

People around you. Connections on your terms.

Iași, Romania

Discover

How DOS worksPeople nearbyProfiles and social linksVisibility choices

Community

For studentsDOS in IașiBusiness pilotCommunity guidelines

Safety

Safety centerPrivacyData requestsReport a concernDelete accountSecurity

Help

Help centerFAQContactAccessibilityTerms
© 2026 DOS
18+Cookies
Your cookie choices

Optional analytics only start with your permission. Details