1. Who is responsible
This policy describes the Streakly app and its connected services. The person or organization operating your deployment is responsible for its handling of personal data. Streakly is currently pre-launch and no public operator identity or dedicated privacy address is published in this app. Contact the deployment owner through the channel that provided your access. An identified operator and working privacy-request contact are launch requirements, not something this policy substitutes for.
2. Information you provide and information generated
- Account: email address, authenticated user identifier, username, account creation date and onboarding status. Email magic-link sign-in and optional Google sign-in are handled by Supabase. If you choose Google, the provider may supply your name and avatar; the app only uses an optional avatar URL in your profile.
- Habits: habit names, emoji, daily virtual-point stakes, active or archived status, creation dates, check-in dates and timestamps, and freezes.
- Accountability: friend requests and connections, challenge invitations, selected habits, challenge dates, completion scores, results and virtual stakes.
- Points: available balance and an immutable ledger of starting points, missed-habit deductions, friend payouts, challenge reserves and settlements.
- Billing: Stripe customer and subscription identifiers, verified subscription status and access end date. The app requests invoice summaries and links from Stripe. Card details are entered on Stripe-hosted pages, not stored in Streakly’s habit database.
- Notifications: if you opt in, your browser’s push endpoint and encryption keys. These identify a browser subscription, not a phone number.
- Technical data: authentication/session information and security or operational logs processed by Supabase, Stripe and the hosting provider. Provider logs may include IP addresses, request times and device/browser information.
Do not enter health records, financial credentials, confidential workplace information or other sensitive personal data into habit titles, usernames or avatar URLs. Habit tracking is not a medical service.
3. How information is used
We use this information to authenticate you, save and display your actual habits, prevent duplicate check-ins, calculate streaks and daily stakes, connect friends, settle challenges, maintain a transparent points ledger, provide paid subscription features, send opted-in reminders and secure the service. Daily processing runs even when you are not signed in. We do not currently include advertising trackers or sell account information. The deployment operator is responsible for identifying the lawful bases required in its jurisdiction; an app setting is not a substitute for those obligations.
4. What other people can see
Signed-in users can search usernames and see public profile information: username, optional avatar and virtual Streak Points balance. Your sign-in email is not part of that public profile. Friendship participants can see the connection and request status. Challenge participants can see the associated habit names, dates, equal stakes, completion totals and settlement result needed for the shared challenge. Your personal habit list, check-ins, freezes and points ledger are otherwise restricted to your authenticated account by database access policies. Do not assume that information intentionally shared with a friend can be made unseen later.
5. Service providers and transfers
Streakly uses Supabase for authentication, database storage and realtime updates; Stripe for Checkout, subscriptions and the billing portal; the configured hosting provider for serving the app and scheduled processing; and browser/operating-system push services for notification delivery. If Google sign-in is enabled, Google handles the authentication step you choose. These providers process data under their own terms and privacy policies as well as their arrangements with the deployment operator. Avatar images load from the HTTPS host you provide, which can receive a request and your IP address. Data locations and international-transfer arrangements depend on the actual deployment and must be disclosed by its operator before public launch.
6. Cookies, local assets and offline behavior
Supabase uses session cookies to keep you authenticated. These are necessary for sign-in and access-controlled API requests; there is no account bypass based on a browser flag. The service worker may cache public app/offline assets so an offline screen can load. Streakly does not intentionally cache private API responses for offline use or queue check-ins locally. A habit action requires a successful server request. We do not use local browser habit or social data as a substitute for the database. Your browser may remember notification permissions and home-screen installation independently.
7. Your controls
You can edit your username and optional avatar in Settings, remove your avatar URL, archive habits, decline or cancel friend requests, remove friends, manage your subscription through Stripe and sign out. Notification permission is optional. Use Settings to remove the saved subscription for this browser; you can also block permission in browser settings. Disabling a permission in one browser does not disable a different device. Archiving a habit stops future daily stakes but does not erase history or reverse an already processed deduction. Removing a friend does not cancel settlement rules for an existing active challenge.
8. Retention and deletion requests
Account, habit and accountability records are kept while the service provides your account. Archived habits and immutable points history remain part of that account; this app does not offer self-service account deletion or data export at present. Ask the deployment operator through the channel that supplied your access for access, correction, export or deletion assistance. The operator must verify your identity and explain what can be deleted, what must be retained for legitimate security, billing or legal reasons, and the applicable retention periods. Stripe may retain billing records under its own obligations. Do not assume a sign-out or cancellation erases data.
9. Security and availability
The app uses authenticated requests, database row-level access policies and HTTPS in deployed environments. Realtime updates are subject to the same database permissions. Payment access is determined by verified server-side subscription records, not URL flags. No system can guarantee perfect security or uninterrupted access. Protect your email account, avoid sharing sign-in links, and notify the operator promptly if you suspect unauthorized access.
10. Children and eligibility
Streakly is not intended for children. You must be at least 18, and satisfy any higher minimum age or other restrictions in your jurisdiction, to create an account or subscribe. The service does not knowingly seek children’s personal information. If you believe a child’s data has been submitted, contact the deployment operator for review and removal.
11. Your rights and complaints
Depending on where you live, you may have rights to access, correct, delete or obtain a copy of personal data, restrict or object to processing, withdraw applicable consent, or complain to your local data-protection authority. Contact the deployment operator to exercise a right; it must explain verification, time frames and any lawful exceptions. This policy does not claim global compliance or limit rights provided by law.
12. Changes and contact
Material changes should be communicated in the app, and this page’s updated date will change. Review it before submitting additional information. For privacy, security or account-data requests, use the verified channel through which the deployment operator provided your access. Do not send passwords, payment card numbers or private sign-in links. A public support/privacy contact must be provided before the service opens to the public.