Doomate is for adults aged 18 and over.
We store your adult declaration privately with its version and confirmation time until account deletion. The iOS app also checks Apple’s shared age range when available and requires it where applicable. A legacy default age is not a declaration. These checks are not a guarantee of identity verification.
Word filtering, reports and blocks
Doomate’s server checks shared text against a limited list of disallowed words before publication. This word filter does not analyze photos or voice notes and does not send content to Google. It cannot identify every harmful message or context. Manual reports and blocking remain available. Doomy’s separate AI review still requires every human participant’s consent.
Report opens an email draft that you review and send to contact@doomate.app. It includes the relevant request, message and user identifiers, displayed text and indicators of media; media is not attached automatically. The founder handles this inbox. Email copies are outside app storage and are not automatically erased by deleting your account or the app.
Blocks are stored privately. Blocking removes the person from your circles, leaves other circles you share, and expires affected pending requests. Finalized access grants remain valid. Unblocking does not restore relationships. Block records are removed with account deletion. People removed from a request lose access to its conversation history.
Accounts, requests and conversations
Firebase stores your account identity, email, profile, support relationships, limits, requests, votes and conversation text, photos and voice notes to run the service. Request participants can see the request and its conversation. Scheduled cleanup removes requests and their conversations after 14 days from creation; retries or a backlog may delay removal. Copies already cached on a device and backups are outside this cleanup.
Service providers and infrastructure
Google Firebase and Google Cloud operate our authentication, database, backend and API services. They process the account and service data described here, plus technical request, IP address, installation, device and security information needed to operate and protect the service. This essential processing is separate from optional analytics and diagnostics.
Sign in with Apple or Google involves the chosen provider and Firebase Authentication. They process sign-in credentials, provider identifiers, and the name and email supplied by that provider. Email/password sign-in also uses Firebase Authentication. Doomate does not receive your Apple or Google password.
When you enable notifications, Google Firebase Cloud Messaging and Apple Push Notification service process installation identifiers, push tokens and notification content. Content can include sender or requester names, group names and short conversation previews. Photos and voice files are not attached to push notifications.
Firebase App Check uses Apple App Attest to verify requests from the iOS app. Apple, Google and our backend exchange app/device attestation information and verification tokens for abuse prevention. Website verification uses Google reCAPTCHA Enterprise as described below. These security checks do not depend on optional analytics consent.
Vercel hosts our public website and processes IP addresses, browser/device information, request details and technical logs to deliver and secure it. Website Google Analytics operates only with the separate analytics choice described here.
Cloudflare Email Routing forwards messages sent to contact@doomate.app to Apple iCloud Mail, where we receive and store them. Both providers process email addresses, headers, message contents and any attachments you send. These support and report emails are outside app storage; account deletion does not automatically erase them. Contact us to request their removal.
For invited testers, Google Firebase App Distribution processes tester names and email addresses, iOS device identifiers, installation/testing activity and any tester feedback you submit to deliver test builds. Apple also processes device and signing information for Ad Hoc installation. This testing processing is separate from optional in-app analytics.
See the privacy information for Google/Firebase, Apple, Vercel and Cloudflare for their processing and retention practices.
Doomy AI and Google
Only after every human request participant separately consents, Google Vertex AI may receive bounded context for Doomy: the owner’s name, age, goals, language, limits, up to seven usage days, recent requests, twelve conversation messages, the request photo and the latest conversation photo and voice note. Selected Apple activity tokens are excluded. Google processes this data to generate Doomy’s review and may retain flagged prompts for up to 90 days for abuse monitoring, including authorized human review. The global endpoint does not guarantee regional processing. See Google’s abuse-monitoring documentation.
Doomy data-sharing consent is versioned and stored privately until account deletion, separately from analytics and ads. Owners cannot consent for other participants. Consent is checked before inference and before publishing its result; revocation pauses Doomy while human chat and votes remain available. Later solo requests can start Doomy automatically only with valid consent. Replies are visible to request participants. An AI approval can grant access immediately; a denial is one vote. Remove Doomy from your circle to stop using him for future requests.
Account deletion and contact
Use Profile → Delete account and confirm your identity to request deletion. You are signed out while the server removes your account, profile, owned groups and requests, and your messages and identity from other requests. Other people’s content remains. A temporary deletion record prevents access while cleanup completes. Deleting Doomate does not cancel an Apple subscription; manage it in Apple subscription settings. For privacy questions, contact contact@doomate.app.
Account setup answers
After you create an account, we save your age, goals, chosen companion, referral source, accountability choice, and any screen-time estimate you enter with your private account profile in Google Firebase Firestore. We use these answers to restore your preferences on another installation and calculate the time projections you request. These answers are not included in other people’s public profile views. Detailed Screen Time activity is rendered on your device and is excluded from these setup answers.
Older accounts without these answers use display defaults: age 18, friends as the companion, and other as the referral source. A default age is distinguished from an age you supplied; it is not a confirmed answer or an age-verification result. Account deletion removes your saved account profile and its setup answers.
Optional analytics and diagnostics
New app versions ask separately for usage analytics and crash/performance diagnostics. Both are off by default and can be changed in Profile → Legal. Usage analytics uses Google Analytics for Firebase, installation-only identifiers and two-month event-data retention. Events describe app flows, plan choices and operation outcomes, without an account identifier.
If enabled, Firebase Crashlytics receives crash stacks and sanitized error codes, and Firebase Performance Monitoring receives named timing traces. Reports include app and device details. We exclude names, emails, selected apps or categories, limits, Screen Time usage, chats, media, authentication tokens and signed purchase proofs. Session replay, advertising personalization and paid analytics exports are disabled. Advertising consent is separate.
The two-month setting applies to Analytics event and user-level data; aggregate reports may remain. Firebase retains Crashlytics data for 90 days and Performance data for 30 or 60 days, depending on the data type.
Website analytics uses separate opt-in consent and a browser-specific identifier. Page addresses exclude query strings and fragments, and referrers are not sent. Change this through Privacy settings.
Onboarding metrics in older app versions
Older app versions use the following collection. Before signup, we measure which setup steps people view and complete and their structured choices. This includes referral source, companion, goals, broad age group, accountability choice, self-reported hours, chosen limit, counts of selected activities, and permission choices. We group ages rather than sending an exact age to these metrics. Names, usernames, email addresses, photos, messages, invite codes, selected app or website tokens, and detailed device activity are excluded.
Events use random onboarding-session identifiers, not account, device, advertising, or installation identifiers. We record account completion after the profile is saved, without adding the account identity to the metrics. Session events expire after 30 days and aggregate counters after 90 days; expired records are removed by a scheduled cleanup. The app keeps only a bounded queue of unsent, unlinked events for up to 30 days. No advertising analytics SDK is enabled for this collection.
Firebase App Check protects this endpoint against automated abuse. Account-completion events also require authentication, but the account identifier and authentication tokens are not stored in the metrics.
Optional profile photos
You can choose a photo or take one for your profile. Adding a photo is optional. The system photo picker shares only the image you select; we do not request access to your whole photo library. Camera access is requested only when you choose to take a photo.
We resize the selected image and remove its original metadata, including location information, before uploading a thumbnail during account setup. We store the thumbnail with your profile in Google Firebase Firestore. It appears with your name in Doomate, including your profile, supporter relationships, requests, chats, and account search results. You can replace or remove it in profile settings.
Optional in-app feedback
Sending feedback in the app is optional. If you send it, we save your message, selected language, and app version and build privately in Google Firebase Firestore, linked to your account. We use this information to review issues and improve Doomate. Feedback is not shared publicly and is deleted when you delete your account. This feedback feature does not accept attachments or automatically collect detailed Screen Time activity or diagnostic data.
Points and home-screen widgets
Your points total is visible to people who can view your profile. Your earning history and completed-day monitoring records are private and linked to your account in Google Firebase Firestore. We award points for eligible support votes and completed days with confirmed active limits, no time requests and no emergency access. Completed-day records describe monitoring and enforcement continuity; they are app-reported evidence, not independently verified Apple usage totals. Later evidence can correct an award. Account deletion removes these records.
Widgets read a local, shared snapshot of your limit and confirmed monitoring checkpoints. Checkpoints are lower bounds, so missing measurements stay unknown and displayed progress includes its confirmation time. Widgets do not receive detailed activity from Apple’s private Screen Time report extension. Local widget data is cleared when you sign out or change accounts.
Waitlist emails
If you join the Doomate launch waitlist, we collect the email address you submit and store it in Google Firebase Firestore in the Doomate app’s Firebase project. We use it to send launch updates. The waitlist is not publicly readable. To ask us to remove your address or stop receiving launch updates, contact contact@doomate.app.
We use Firebase App Check with Google reCAPTCHA Enterprise to protect waitlist submissions from automated abuse. Google processes browser and device signals for this verification under its Privacy Policy and Terms of Service.
Subscriptions and paid points
We link your verified App Store subscription, product, transaction identifiers, trial status and expiry to your account in Firebase to enforce your plan, restore purchases and prevent duplicate monthly points. Apple processes payment details; Doomate does not receive your card number. Paid Plus periods grant 100 points monthly and paid Pro periods 200; trials grant no subscription bonus. Annual subscribers receive the same monthly awards.
Subscription emails and push reminders
When subscription reminders are enabled, Resend sends trial and renewal emails, which may include product guidance. Resend receives your verified email address, reminder content such as plan, price, currency, billing period and trial/renewal dates, and delivery and unsubscribe identifiers. We do not include private conversations or user-uploaded media. Subscription reminders may also be delivered through Google Firebase Cloud Messaging and Apple Push Notification service.
Resend stores email content and delivery logs in the United States. Selecting an EU sending region does not keep that stored data in the EEA. Its Data Processing Addendum explains the safeguards for international transfers.
We store reminder schedules, delivery status, bounce/complaint information and reminder preferences in Firebase. Reminder records are scheduled for deletion 30 days after the related subscription period ends; cleanup can be delayed. Account deletion removes our account-linked reminder records. Resend's own processing and retention are described in its Privacy Policy.
Use a reminder email's unsubscribe link to stop reminder emails, and your device's notification settings to control push notifications. These choices are separate from optional analytics and do not cancel your Apple subscription. Apple processes payments and subscription changes; Resend does not receive your payment-card details from Doomate.
We use delivery, delay, bounce, complaint and failure events to operate reminders. We do not use email-open or click tracking for these messages.
Advertising on Free
Free uses Google AdMob interstitial ads before requests, saved limit or target changes, and support votes. The Google Mobile Ads SDK may process IP addresses (including approximate location), device identifiers, crash and performance diagnostics, ads viewed and ad interactions for advertising, measurement and fraud prevention. IDFA is available only with Apple tracking permission. We never provide private chats or Screen Time app and website tokens for ad targeting. Paid plans do not initialize the advertising SDK.
Google’s consent flow asks for consent where required, and ad privacy choices can be reopened in the app. Users under 16 are marked under the age of consent; users under 18 receive non-personalized ads. Adults may separately choose Apple tracking permission; refusal does not prevent using Free. Non-personalized ads may still process technical data. See Google’s Privacy Policy.