Ember
PrivacyTerms

Privacy Policy

Plain words about what Ember keeps, why, and how you stay in control.

Effective 2 November 2026

  1. 01Who runs Ember
  2. 02What Ember collects
  3. 03Cookies
  4. 04Why, and on what legal basis
  5. 05Who can see your data
  6. 06Services that handle data for Ember
  7. 07Google user data
  8. 08How long data is kept
  9. 09Export, deletion and your rights
  10. 10Children
  11. 11Security
  12. 12Changes to this policy
  13. 13Contact

Who runs Ember

Ember is run by Hamza, an individual. I decide what personal data Ember collects and why, which makes me the controller of that data. Contact: support@itshamza.me.

Ember runs on a server I operate. There are no ads, I do not sell your data, and the app has no third-party analytics or tracking scripts.

What Ember collects

  • Account: your name, email address, optional username and avatar, and a hashed password if you use one. A passkey stores a public key, never your biometrics.
  • Google profile, if you use Google sign-in: your name, email address and profile picture, plus the tokens Google issues to Ember for that sign-in.
  • Habits and activity: habits, categories, schedules, check-ins, notes, timer sessions, quit-habit relapses, streak freezes, XP, levels and achievements.
  • Journal and mood: journal entries, tags and a 1 to 5 mood score. This can reveal sensitive things about your mental health or personal life. It is stored with the rest of your account data and is never shown to other users.
  • Time settings: your timezone and the hour your day starts, so check-ins and reminders land on the right day.
  • Push notifications, if you turn them on: the push endpoint and keys your browser gives Ember, your browser's user-agent text, and your notification preferences.
  • Social: friend requests, blocks, reactions, nudges, and the profile and activity information you choose to share (see section 5).
  • Sessions and security: a session cookie keeps you signed in. The server stores each session with your IP address and browser user-agent. Short-lived rate-limit counters, keyed by IP address or account, help block abuse. They are cleaned up about a day after use.
  • Offline copy on your device: the app can keep your data and queued check-ins in your browser so it works offline. Signing out clears it.

Ember does not ask for your date of birth, location or contacts.

Cookies

Ember sets a session cookie to keep you signed in. The app needs it to work. Ember sets no advertising or analytics cookies. Your browser may also store the offline copy described above.

Why, and on what legal basis

  • Run the service you asked for (contract): your account, habits, check-ins, streaks, analytics, reminders, friends and exports.
  • Keep it secure and working (legitimate interests): sessions, rate limits, abuse prevention and backups.
  • Email you about your account (contract): verification, password reset, sign-in links and account-deletion confirmation. These are not marketing.
  • Push reminders (consent): sent only after you allow notifications in your browser. Turn them off in Settings or your browser at any time.
  • Journal and mood (consent, given when you choose to write them): you can delete any entry, or your whole account, whenever you like.

I do not use your data for advertising or to train AI models.

Who can see your data

Everything is private by default. Your profile is not public until you switch it on, and each habit is “Only me” until you set it to Friends or Public.

  • Other users see only what the controls allow: your username, level, and the profile sections and habits you chose to share. They never see your email, timezone, XP total, habit notes, check-in details, journal or mood.
  • Friends can see feed events you made shareable (such as a level-up or a streak milestone on a shared habit), react to them, and send you one nudge a day. You can mute nudges and block anyone.
  • A public profile can be opened by anyone with the link, including search engines.

Services that handle data for Ember

  • Self-hosted server and database. Ember and its database run on a server I operate. There is no separate hosting platform or managed database.
  • Resend (email). Verification, reset, sign-in and deletion emails are sent through an SMTP email service, Resend. It receives your email address and the content of those emails.
  • Google (sign-in). Only if you choose “Continue with Google”. Google tells Ember who you are. Google's own privacy policy covers what Google does.
  • Browser push services. If you enable push, reminders go through the push service run by your browser maker (for example Google, Mozilla or Apple). It sees the notification text so it can deliver it.

There are no advertising networks, analytics providers or data brokers. I do not sell or rent personal data. I may disclose data if the law requires it.

Google user data

If you sign in with Google, Ember asks for your basic profile only: your name, email address and profile picture. It uses them to create and sign you into your Ember account and to show your name and avatar. It does not read your Gmail, Drive, Calendar or contacts.

Ember's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the features you see in Ember. It is not transferred to others except as needed to run the service or as the law requires, it is not used for advertising, and people do not read it except for security, legal compliance, or with your consent.

You can remove it by deleting your account (section 8). You can also remove Ember from your Google Account's third-party access page.

How long data is kept

  • Your data stays until you delete it or delete your account.
  • Deleting your account removes your profile, habits, logs, journal, mood, friends, push subscriptions, sessions and sign-in records from the live database.
  • Sessions expire on their own after a set period.
  • Backups: the database is backed up nightly and each backup is kept for 14 days. Deleted data can remain in those backups until they expire, then it is gone.
  • Rate-limit counters are removed about a day after use.

Export, deletion and your rights

Export: in Settings you can download all your data as JSON, and your check-ins or journal as CSV. You can import an export back in.

Delete: in Settings, “Delete account” erases your account and its data after you confirm with your password, an emailed link or a passkey. It cannot be undone.

If you are in the EEA, the UK or a similar region, you have the right to access, correct, delete, restrict or object to the processing of your data, to data portability, and to withdraw consent at any time. You can do most of this in the app. For anything else, email support@itshamza.me. You may also complain to your local data protection authority.

Children

Ember is not for anyone under 16. Do not create an account if you are under 16. If I learn that an account belongs to a child under 16, I will delete it. If you think that has happened, email support@itshamza.me.

Security

Passwords are hashed. The site sends strict security headers, sign-in and other sensitive endpoints are rate limited, and every request for your data is checked against your account. You can sign in with a passkey. No system is perfectly secure, and I cannot promise otherwise.

Changes to this policy

I may update this policy. The effective date at the top shows the latest version. For a material change I will give notice in the app or by email.

Contact

Questions or requests: support@itshamza.me. See also the Terms of Service.