Privacy Policy

UpRoar is an alarm clock that makes you prove you're awake. To do that it needs to know when you were supposed to get up and whether you did. This page says exactly what that means in terms of your data — what we hold, what never leaves your phone, and who else can see any of it.

Optional local alarm diagnostics. In Settings you can enable a local support log with up to 100 recent events from the last 7 days. Reports include phone model, app version, permission readiness, alarm IDs and event times, but no account credentials, alarm labels or task answers. Nothing is uploaded automatically. Review before exporting, since times may reveal your routine. Turning logging off or clearing the log deletes recorded events on this phone; saved exports remain wherever you saved them.

Who we are

UpRoar (the Android app com.uproar.app, on Google Play and at uproarme.com) is made and operated by Karmanye Tech LLP, India, listed on Google Play as “Karmanye Tech”. Karmanye Tech LLP is responsible for the data described here. For anything in this policy, including a deletion request, write to support@uproarme.com.

What we store on our server

The following data is stored on our servers. We do not sell this data. Service-provider and optional squad sharing are described below.

• Your account. Your name, your email address, and your password — the password is stored as a salted verification hash, not plaintext. We store a hash and expiry for each sign-in session.
• Profile preferences. Earlier clients may have saved your reason to rise and difficulty on the server. The current Android app keeps edits to these preferences on your phone.
• Alarm configuration. Current Android alarm schedules, labels, tasks and habits are device-local and are not a cloud backup. Server records from earlier clients may still contain alarm configuration.
• Your mornings. When an alarm was due, whether you cleared the chain, how long it took, which tasks you completed, how many times you snoozed, and whether you passed the follow-up wake-up check. When synced, this record supports account progress and optional squad features. Local alarm settings can also stay on your phone.
• Demo credits. Optional credit adjustments and their activity ledger. These are not payment or donation records.
• Beta requests and feedback. We store the name, email, testing phone, Android version, country/region and note you choose to submit. We review requests before sending a private APK link and activation code. We use your email for request review, beta participation and feedback follow-up, not marketing. Submitted email alone is not verified identity; beta activation requires the private code and matching account email. Forms also send IP address, browser user agent, inferred device type/browser/operating system, browser language and time zone for manual review, troubleshooting and abuse prevention. These signals can be inaccurate or shared; we do not make automatic identity decisions from them. Technical context and rate-limit hashes are removed from these records after 30 days. We do not collect precise location or create a hidden device fingerprint.
• Feedback attachments. Reports may include text, email, phone/app version and screenshots or recordings you choose to upload. Recordings may include audio; we never capture your screen automatically. Reviewers can access these privately. Please remove personal information before submitting; files may retain embedded metadata. Images are limited to 10 MB, videos to 25 MB, with 3 files and 30 MB total per report. Attachments are deleted from active storage after 90 days and feedback reports after 180 days. Beta request/contact records are kept while your participation and support needs remain active; contact us to request deletion. Backup copies follow our backup rotation and may persist longer before expiry. Request deletion at support@uproarme.com.
• Your plan. When your free trial started and ends, whether you subscribe and until when, and a fingerprint of each phone that uses your plan (a one-way hash of a random id the app makes, not a hardware identifier). We use it to give each account and phone one trial and to limit how many phones share a plan. If you pay, the payment provider gives us your subscription status and its own customer and subscription references; we never receive or store your card details.
• Squad. Which squad you're in, and the posts, nudges and reactions in that squad's feed.
• Streaks and referrals. Your current and best streak, shields, and your own referral code. If you redeem someone else's code we record that the two accounts are linked, against your own email address. We never ask you for anyone else's email address, and there is no invite-by-email in the app — invites are a link or a code you pass on yourself.

What never leaves your phone

Three of the wake tasks use hardware that people are rightly careful about. None of them send anything to us.

• Microphone. The speak-aloud task is handled by Android's own speech recogniser. We ask it to work offline wherever your device has an offline model, and the app only ever receives back the recognised text so it can check whether you said the line. We never receive or store audio from the wake task. One caveat we would rather state than hide: if your device has no offline model, Android's recogniser may fall back to Google's online service, in which case the audio is handled by Google under their privacy policy, not ours. The task is optional — leave it out of your chain if you would rather it never happen.
• Camera. The scan task decodes your registered code using a barcode model bundled inside the app, running on your device with no network access. The household-object alternative — pointing the camera at a kettle or a tap instead of a printed code — recognises the object with Google's on-device image-labelling model, which is delivered through Google Play Services rather than bundled in the app, so it is downloaded to your phone once and then runs entirely offline like the other. In both cases camera frames are analysed in memory and discarded: no photograph is taken, stored or uploaded, and no image ever reaches us or Google.
• Motion and step count. The walk task reads your phone's own pedometer, and the shake task reads its motion sensor, only while the task is on screen. Only the outcome — that the task was cleared — is ever sent.
• Touch and typing. Sums, memory patterns, taps and typed lines are checked on your phone. What you type or tap is never sent, only that the task was cleared.
• Mood. If you tap how you feel (after waking, on the Mood screen or on the "Today's line" widget), that mood, any words you pick like "stressed" or "calm", and the time are kept only on your phone, to choose a fitting line and draw your mood charts. They are never sent to us, to analytics or to anyone else, and are left out of phone backups. If you allow analytics, we count only that a mood was logged and from where, never which mood. You can delete your mood history in the app at any time. UpRoar is an alarm clock, not a medical or mental-health service.

Voice wake-up messages

You can ask a friend to record a short message that plays as your alarm. You don't need an account for this. The app sends our server the name you choose to show and an optional short note, and gets back a private link (uproarme.com/w/…) to share. Anyone with the link sees that name and note. If you leave “Let them know when I’m up” on, the app also tells our server the time you got up to each message, and the link page shows it to the people who have the link.

If you record a message for a friend, you do it in your browser. We receive the recording (up to 10 seconds), the name you type, and the time you sent it. To limit abuse we also keep a one-way hash of your network address, not the address itself. The recording goes only to the friend who sent you the link, whose phone downloads it to play as their alarm. We don't listen to it, analyse it, or use it for anything else, and it is not shared with analytics. The name you type is shown on that link page to anyone who has the link.

How long it stays. A link takes new messages for 7 days. A recording is deleted from our server 3 days after your friend's phone downloads it, and everything about the link, including names, notes, times and any recording not yet downloaded, is deleted 30 days after the link was made. Your friend can also delete a message in the app at any time, or tap Stop sharing to delete the link page and everything on it straight away. Copies already saved on their phone stay there until they delete them. To have a recording you made deleted sooner, email support@uproarme.com with the link. Voice recordings are not included in our backups.

Who can see your mornings

A squad exists so that other people can see whether you got up; that is the whole mechanism, and you should join one knowing it. Members of your squad can see your display name, whether your alarm is armed, whether you cleared or slept through, and your streak.

They cannot see your email address or your full demo credit ledger. If you enable snooze sharing, posted updates may include demo credit adjustments. Snooze sharing is off for new alarms. If you would rather nobody saw any of it, don't join a squad — every other part of the app works without one.

What we don't do

• We don't sell or rent your data, and we never will.
• We don't run advertising, and there are no ad or attribution SDKs in the app.
• We don't collect your location, contacts, call logs, messages, or the list of other apps you have installed.
• We don't use crash-reporting services or advertising networks, and optional analytics stays off unless you opt in. Account, squad and feedback requests send the information needed for those services.
• We don't email you marketing you didn't ask for.

Analytics

In the app. The app asks once whether you'll share optional usage analytics. Until you say yes, the analytics SDK does not collect usage analytics. Account and service requests still work separately. If you do, Google Analytics for Firebase and Mixpanel (EU project) receive a few events with fixed values: onboarding finished, successful beta activation, an alarm saved (new or edited, how many tasks, which repeat pattern), a delivery test passed or failed, a morning or practice finished (how many tasks), signing up, and seeing the plans screen. It never receives your alarm times or names, what you say or type, scan targets, your email or squad messages. Each analytics provider uses a resettable app-instance identifier and device/app metadata; this is pseudonymous, not a guarantee of anonymity. Advertising ID, ad personalisation and ad storage are off. Turn it off any time in Settings, Help improve UpRoar; turning it off also clears the analytics data held on your phone.

On this website.

Choose “Analytics only” to let Google Analytics measure visits, page views, broad location, device/browser type and accepted beta requests. Mixpanel also receives fixed events for download links, guides opened and accepted requests, using a resettable browser identifier in local storage. On the home page, Microsoft Clarity also measures clicks, scrolling and mouse movement, with typed text masked. Analytics cookies distinguish visits. Choose “Allow analytics + ad measurement” to additionally let Google Ads store click-attribution cookies and receive an event after a beta request is accepted. This links applications to our ads. We do not send names, email addresses, phone details, application text or attachments in these events. Enhanced conversions, ad personalisation and Google signals remain disabled. Nothing loads before your choice; “No thanks” keeps these tools off. Existing analytics consent does not grant ad-measurement consent. Change your choice using “Analytics choices” in the footer. Global Privacy Control overrides consent and keeps tracking off. Google, Mixpanel and Microsoft receive the relevant measurement data when you opt in.

Mixpanel event ingestion uses our EU project. Automatic interaction capture, Mixpanel session replay, user profiles, account linking and IP-based location enrichment are disabled. Network providers still process connection information to deliver requests. We do not send personal wake-up reasons, alarm labels or times, invitation/download codes, form contents or attachments to Mixpanel. Previous analytics approvals require a fresh choice for this update; previous refusals stay off.

Turning analytics off prevents new events and clears the local Mixpanel identifier and queued events. It does not automatically erase events already received by analytics providers. For a deletion request, contact support@uproarme.com; because we do not link Mixpanel identifiers to your account or email, we may need your device's analytics identifier to locate those records. Provider-side retention is separate from local storage and follows the project's configured retention settings.

Who else touches your data

As few parties as we can manage. Our server runs on rented infrastructure in Germany, and traffic passes through Cloudflare, who terminate TLS and filter abuse. If you allow analytics, Google, Mixpanel (and on the home page, Microsoft) receive the data described above. Android's speech recogniser is Google's, in the narrow case described above.

Premium purchases. In the Google Play version, Google Play takes the payment and handles your payment details; we never see them. The app tells our server about a purchase only if you are signed in, so your plan follows your account: we receive the product, its status and dates, and a purchase token we check with Google. The website version uses our payment provider's checkout in the same way.

Buddy (optional AI, Premium). Buddy is off until you turn it on in Settings and agree to what it sends. When it is on, the app sends our server your streak, best streak, next alarm time and the reason to get up you wrote (up to 120 characters). Our server removes any emails, phone numbers and links, and asks Anthropic, PBC (United States), the maker of the Claude AI models, to write a few short lines. Anthropic processes this on our behalf and does not use it to train its models. Your mood, name, email, alarms and location are never sent. We keep Buddy's lines for up to 2 days, keep a count of requests to limit use, and keep lines you report for up to 90 days so we can review them. AI can get things wrong: every Buddy line is labelled, can be reported in the app, and is not medical advice. Turning Buddy off removes its lines from your phone; deleting your account removes everything Buddy-related from our server.

The Premium offer screen. In the Google Play version, the screen that shows Premium's plans may be provided by Superwall, Inc. (United States), so we can improve its design and compare versions without an app update. It is used only once we offer Premium, and only when that screen opens. Superwall receives device and app details (such as phone model, Android version, language, store country and app version), a random identifier it creates, which offer screen you saw, what you tapped on it and whether a purchase started or finished. It never receives your email, account, alarms, wake reasons or anything you type in the app. If you haven't allowed analytics, the app tells Superwall to collect only what it needs to show the screen. Superwall processes this on our behalf, in the United States.

Keeping it safe

Traffic between the app and our server is encrypted in transit. Passwords are stored as salted, versioned PBKDF2 hashes; older hashes are upgraded after a successful sign-in. Session tokens are stored as hashes and expire after 30 days. In app version 1.4-beta and later, signing out also attempts to revoke the server session. Offline sign-out clears this phone, but server revocation cannot be confirmed until a request reaches the server. Older app versions only clear the local sign-in. No system is perfect, and we would rather say so than claim otherwise.

How long we keep it

Account details and your wake history are kept while your account exists, because streaks and settlement depend on the history. Delete your account and we remove your account record, alarms, wake history, streaks and squad posts. The current demo credit ledger is also deleted; it is not a financial transaction record. Your plan and phone records are deleted too, except one thing: the one-way fingerprint of any phone that used a free trial is retained without its account link to prevent repeated trials. Reviewed invitation records also retain a consumed marker so an old invitation cannot be reused after account deletion. These anti-abuse records are not a claim of anonymous data.

Your rights

Wherever you are, you can ask us for a copy of your data, ask us to correct it, or ask us to delete it. If you're in the UK or EU, that's your right under the UK GDPR and GDPR respectively, along with the right to object to processing and to complain to your data protection authority. Email support@uproarme.com and we'll action it within the applicable legal deadline. The same requests apply under other privacy laws, including those of US states such as California, Canada, Brazil, Australia and India. We don't sell your personal information or share it for cross-context behavioural advertising. We may ask for proportionate information to verify ownership before disclosing or deleting data; we will explain any lawful retention or extension.

Children

UpRoar isn't intended for children under 13, or under the minimum age for consenting to online services where you live (up to 16 in parts of the EU). The current app has no real-money stakes. If you believe a child has given us personal data, write to us and we'll delete it.

Changes

If this policy changes in a way that affects what we collect or who sees it, we'll change the date at the top and say so in the app rather than quietly editing this page.