DuoRise Privacy Policy

Last updated: 7 October 2026

DuoRise helps people set local alarms and, when both people explicitly agree, exchange a prepared voice message or use live push-to-talk at a scheduled wake-up. This policy explains what the service collects and why.

Information we use

• Account information: an anonymous account or an account identifier supplied by Google, Apple, or email/password sign-in. We use it to keep your account and relationships. When you use Sign in with Apple, a refresh token is kept server-side only to revoke the Apple authorization when you delete your DuoRise account, then removed with the account.
• Profile and routine information: display name, optional profile photo, locale, time zone, alarm and routine settings.
• Trusted relationships: invitation state, mutual wake permissions, pause/revoke/block choices, and device capability metadata.
• Shared mood and ritual entries: when you explicitly tap Share my mood, DuoRise stores the mood you choose and daily mood counts in the shared Duo. Other entries you choose to share include breakfast or gym flags and heart totals. Your partner can read these records while your Duo is active or paused. Revoking or blocking the relationship ends access to shared history through the service. This does not erase copies either person has already saved.
• Usage measurement: when enabled, DuoRise keeps a limited buffer of selected product events on this device. If you are signed in, eligible events may be sent to DuoRise with the event name, day, app version, operating system, a random event identifier, and a pseudonymous account identifier. Some pair events also include a pseudonymous Duo identifier. These events do not contain voice audio or message text. Turning off usage measurement clears the local buffer and stops queued and future uploads; an upload already in progress may finish. This does not delete events already stored on our servers.
• Voice messages: only after you choose to record, review, and confirm sending one. DuoRise verifies the relationship, recipient permission, file type, size, and integrity before making the note available. DuoRise does not transcribe recordings, run automated semantic screening, or send voice audio to an AI provider. A recipient report quarantines the selected recording from fresh partner access and restricts new publication or assignment of the same verified audio bytes from that sender within the pair for up to 30 days after the report. This does not classify every new recording or erase copies already saved on a device. Notes are stored in Firebase Storage with relationship access controls and expire within 30 days. DuoRise does not use voice recordings for advertising or model training.
• Live voice: when you use push-to-talk during a mutually authorized wake-up, audio is streamed through the DuoRise relay hosted on Google Cloud Run and forwarded to your paired partner for that session. The relay does not save the stream as a recording.
• Technical information: device token, limited diagnostic/crash information, and support messages you choose to submit. We do not use raw audio or transcripts for analytics.

How we use it

We use this information to authenticate you, deliver notifications, enforce mutual consent, schedule local alarms, play an authorized prepared message, support live wake-up voice, prevent abuse, troubleshoot failures, and honor deletion or revocation requests. We do not use voice recordings for advertising. Advertising data use and available choices are described below.

Sharing and service providers

Firebase Authentication, Firestore, Cloud Functions, Cloud Storage, Cloud Messaging, and Cloud Run are Google Cloud services used to provide and secure DuoRise. They process data under Google's applicable Cloud service and data-processing terms. Cloud Run hosts the live voice relay, which forwards authorized audio between paired devices during a session and does not save the stream as a recording. Google Cloud may process connection and operational log data. A notification contains only the minimum action data needed to open the app. A prepared message is made available to the paired partner selected in the app. Authorized safety operators may inspect a reported recording while it remains available, solely to review the report and protect users. Reports and recordings are not emailed to operators or sent to a new scanning provider. Disclosure may also occur where required by law.

Retention and deletion

Prepared voice files and their metadata expire within 30 days and are deleted sooner when you delete a message, revoke or block a relationship, or delete your account. Account deletion removes account-owned metadata and media before the authentication record is deleted. You can revoke a relationship or remove a message from inside the app. After account deletion begins, a server-controlled security marker blocks direct client access while delayed cleanup is retried. A final cleanup sweep runs after a 24-hour safety window to catch delayed operations; outages or incomplete cleanup can extend retention. The security marker is removed only after cleanup succeeds.

Reports and safety controls

A report stores the reporting account, the relationship and relevant participant or content references, your explanation, a response deadline, and any moderator decision. Only authorized operators can read these records. Reporting a prepared recording quarantines it from fresh partner access; an exact-byte restriction prevents new publication or assignment of the same verified bytes from that sender within the pair. Blocking ends the relationship’s access and starts the same live-session, relay-ticket and prepared-media cleanup used by normal in-app blocking. Downloaded or buffered copies may persist until the device observes the change.

Reports and their moderation decisions expire 30 days after the report was created, whether open or resolved. Related exact-byte restrictions expire after the same 30-day window. Deleting an involved account removes associated reports and restrictions, including complaint text. Scheduled cleanup deletes expired records and retries incomplete cleanup; outages or a backlog can delay final erasure. A reported recording remains subject to its original voice-file expiry and may no longer be available when an operator reviews the report. Live streams are not recorded as report evidence.

Advertising and privacy choices

DuoRise uses Google Mobile Ads and Google's User Messaging Platform. When ads are enabled, a labelled banner may appear above the main navigation, and a medium rectangle may appear after wake-up completion. You do not have to watch or interact with an ad to use local alarms or finish a mission. DuoRise requests non-personalized ads with Google’s Restricted Data Processing signal and disables publisher first-party ID. Non-personalized ads can still involve data processing for ad delivery, fraud prevention, frequency capping and reporting. On iOS, DuoRise also requires authorization through Apple’s tracking permission before initializing or requesting ads. Declining this permission keeps ads off without restricting alarm or partner features. You can change this permission in iOS Settings; the app rechecks it before requesting new ads.

Google describes possible SDK collection including network addresses, approximate location inferred from them, device identifiers, ad interactions, diagnostics and performance information. See Google's SDK disclosure and Google's privacy policy. DuoRise does not supply voice recordings, journal text or partner messages to advertising requests.

Open the app's Privacy explanation and choose Advertising privacy choices to review the available consent form. Choices depend on the service and region; if the form is unavailable, the app offers a retry. Usage-measurement preferences are separate. Contact us below if you cannot access your privacy choices.

An optional, one-time Remove Ads purchase is processed by Apple. StoreKit checks Apple-verified ownership on your device; DuoRise does not receive payment-card details or send this purchase to Firebase. Restore it with the same Apple Account. The purchase removes advertising and does not restrict alarm or partner features.

Children

DuoRise is not directed to children under 13 (or the minimum age where you live). Do not create an account if you are below that age.

Security and limits

We use Firebase access controls, short-lived authorization, and least-privilege relationship rules. No online service can guarantee absolute security. Live wake-time voice exists only as an explicitly permitted, mutually consented push-to-talk session: there is no auto-answer, and the app never turns on a device microphone without its owner's explicit action (the sleeper microphone never starts on an incoming request).

Your choices and contact

You may access, correct, export, or delete your data from the app. For privacy questions or a deletion request, email new.houchti@gmail.com. We may ask for enough information to verify the request without asking for your password.

Support · Terms of use · Delete your account

This policy is a product disclosure, not legal advice. We will update it when the product, providers, or applicable requirements change.