Privacy policy

sumore helps you manage app limits with friends. This policy explains how cowcatbird handles information in sumore and on this support website.

Information we store

• Account: an account identifier, display name, friend code, authentication records, and a protected hash of your private login key. You do not need to provide an email address to create a standard sumore account.
• Circle activity: group membership, time requests and any notes you enter, approvals or denials and their timestamps, daily reward eligibility, shared s’more balance, purchases, and selected character appearance and background.
• Shared limits: your planned daily allocation and any app labels and allowances you voluntarily share. These are not a record of your actual app usage.
• Notifications: a device push token if you enable notifications, used to deliver requests and decisions.
• Support: messages, your sender email address, and attachments you send us. In-app problem reports include app version and platform; you review and send the email using your mail app.
• Service operation: our service providers process technical information such as IP addresses and request or error logs to run and protect the service. Account-access rate limiting also uses account identifiers and a keyed hash of the network address.

Community rules, reports, and review

• Rule acceptance: your account identifier, the version of the community rules you accepted, and the acceptance timestamp.
• Reports: the reporter’s and reported person’s account identifiers, the request identifier when a request is reported, your chosen reason and optional details, report and retry-receipt identifiers, submission timestamps, and review status. Retry records retain the submitted fields so the same report is not counted twice.
• Reported content: a server-captured snapshot of the reported person’s display name and voluntarily shared app labels with their planned minutes. A request report also captures that request’s note and category label. These are fields the reporter can already see, not a record of actual app usage.
• Review records: manual decisions, decision notes and timestamps, report versions, private notices, and any social restriction with its reason, duration, and source report. Where an app moderator reviews a report, the audit records that moderator’s account identifier. For reviews through trusted database administration, it records the database operator’s session role; that role is not a verified personal email identity. We also retain account identifiers for approved app-moderator access.

Community reports do not automatically collect selected-app tokens, device app icons or package lists, detailed usage, push tokens, or login keys. Do not type private information into the report’s free-text details. We use report records to assess concerns, prevent duplicate submissions and misuse, explain decisions, and handle appeals.

Saved reports are available only through approved private operator access, not to circle members or the reported person. The reported person may see a relevant decision notice and restriction reason, not the report or reporter identity. The app’s private review list also omits the reporter’s account identifier. Free-text details can still indirectly identify someone, so keep them limited to what is necessary.

Saving a report is separate from sending email

The app saves the report and its authoritative content snapshot first. It then opens a prefilled draft addressed to our support team: Show email address. You review the draft and tap Send in your own mail app. The draft includes the report reference, reported display name, type of content, chosen reason, and your details. It does not automatically include private account identifiers or login keys.

Cancelling the email does not delete the saved report. It also remains saved if a mail app is unavailable or delivery fails. Opening a draft does not confirm sending or delivery. If you send it, Gmail and your email provider process the message and support can see your sender email address and anything else you include. The reported person is not given your email address by this flow.

The email draft can be edited. It is a notification for a human reviewer, not authoritative evidence or an instruction to take action. An authorized operator checks the saved server record before a manual decision. Report counts do not automatically punish an account. A limited text filter may reject clearly abusive wording before sharing; it is not comprehensive detection. Read the community rules and reporting guide for the available controls and appeal contact.

Screen Time and Android permissions

On iPhone, Apple’s Family Controls, Device Activity, and Managed Settings APIs let you select apps and enforce limits. Apple supplies privacy-preserving selection tokens. Those tokens and local limit state remain on your device, including the app’s shared storage used by its Screen Time extensions. They are not uploaded to our circle database.

On Android, Usage Access measures time in your selected apps. If you enable sumore’s Accessibility service, it detects the foreground app and shows the blocking screen when a limit is reached, including while that app remains open. The service uses app identifiers and app-change events; it does not retrieve screen content or read messages, passwords, or typed text. Selected package identifiers, app icons, and detailed usage are handled on your device, not uploaded to the circle database.

These permissions are used for the app-limiting features you choose. You can revoke them in your phone’s settings; doing so can stop blocking. Revoke notification permission separately if you no longer want notifications. App blocking requires the installed iPhone or Android app.

How information is used and shared

We use information to operate accounts, synchronize circles, deliver requests and decisions, maintain shared rewards and purchases, apply your chosen limits, respond to support requests, review community concerns and appeals, and prevent misuse of account access and social features.

Members of your circle can see the profile and shared activity described above, including requests and their outcomes. Your total planned daily allowance syncs automatically when you save limits or refresh circle sharing. Only the app labels and individual allowances you type into the sharing form are optional. Keep sensitive information out of display names, request notes, and shared app labels. Your private login key is not displayed to your circle.

If you block someone, we store both account identifiers and when the block was made to keep you out of the same circle and prevent new requests between you. Your blocked list is private to your account, though someone may infer a block. Unblocking or deleting either account removes the block record. Leaving a circle does not delete your account or that circle’s shared wallet and purchases.

We use Supabase for authentication and database services, Expo and Apple/Google services for supported app delivery and push notifications, and Gmail to receive support email. This support website is hosted through Vercel. These providers process information needed to provide their services. Their infrastructure may process data outside your country.

We do not sell personal information or use your app-usage data for advertising. This support website has no custom analytics, advertising scripts, or contact form; hosting providers may still process ordinary network requests and security logs.

Login keys and device storage

Your private login key can recover your account. The server stores a hash, not a readable copy. Native apps save the device copy using protected device storage. A web login key is held in the current tab’s memory; web authentication sessions use browser storage. If you copy a key, it is placed on your device’s clipboard. Keep your own copy somewhere private and never send it to us in email. Your friend code is not a login credential.

Switching to a recovered account does not merge accounts or automatically delete the abandoned account. Replacing a login key prevents that old key from being used for new recovery attempts, but does not automatically sign out every previously signed-in device.

Retention and deletion

Account information remains while the account exists; sumore does not currently delete accounts automatically for inactivity. Uninstalling the app does not delete information from our servers.

Community-report cleanup is manual, not scheduled. Resolved or dismissed reports become eligible for operator cleanup when their last review action is more than 90 days old (or their creation date if no review action exists). Reports supporting a still-active social restriction are excluded. An authorized cleanup run removes up to 1,000 eligible reports and their related receipts, notices, and audit records. There is no automatic 90-day deletion job or guaranteed deletion date. Open reports remain pending manual review unless the reporting or reported account, or an associated request, is deleted.

Use Setup → Account → Delete account to request permanent deletion in the app. This removes your account, profile, login-key records, and associated personal data from the active database. Other members keep their accounts and the circle’s shared wallet and purchases. Shared reward history and certain peer decisions can remain without your deleted account identity so that another member’s progress is not erased.

Deleting either the reporting account or the reported account deletes the associated reports, content snapshots, receipt records, notices, and moderation audit entries from the active database. It also removes any restriction currently linked to a deleted report, including when the reporter deletes their account. A newer restriction linked to a different retained report is not removed. Your own rule-acceptance, moderator-membership, and restriction records are deleted with your account. If only a reviewing moderator’s account is deleted, that moderator’s identifier is removed from retained audit entries rather than deleting other people’s reports.

You can also request account deletion outside the app. We verify ownership before acting. Provider backups, security records, and information needed to meet legal obligations may remain for applicable retention periods and are not promised to disappear instantly. Emails already sent to support are separate from the app database; tell us if you also want those copies deleted, subject to necessary legal or security retention.

Your choices

You can edit your display name and appearance, change or remove voluntarily shared app labels, manage device permissions, and delete your account. For questions about access, correction, or deletion of your information, contact us below. We may need to verify ownership before fulfilling a request.

Children

sumore is not directed to children under 13. If you believe a child under 13 has provided us personal information, please contact us so we can review and address it.

Updates and contact

We may update this policy as sumore changes and will update the date above. For privacy questions, contact cowcatbird: Show email address.