Privacy policy

Glimby is run by Issmail Basel Mokhibi, Private Entrepreneur (Armenia). We decide how your personal data is used, which makes us the “controller” under data protection law. In this policy, “we” and “us” means Issmail Basel Mokhibi, Private Entrepreneur. Our registered business details are available on request.

For anything about your data, write to hello@glimby.app, or send a privacy request from Settings → Feedback inside the app. We don’t have a data protection officer; we’re small enough that the person who reads your message is the person who can act on it.

The legal reasons come from the GDPR (articles 6 and 9). “Contract” means we need it to give you the app you asked for.

• Your account: email, display name and password (only as a secure hash). If you sign in with Google: your account ID there, the link to your profile picture, and the sign-in tokens they issue

  Why

  To sign you in and keep your things yours. Contract.

  Kept

  Until you delete your account.

• Passkeys: a public key for each device you add one on. Your fingerprint or face never leaves your device

  Why

  So you can sign in without a password. Contract.

  Kept

  Until you remove the passkey in Settings or delete your account.

• Guest accounts: a random ID in a cookie, no email

  Why

  So you can try Glimby without signing up. Contract.

  Kept

  Until you delete it or move it into a full account. If you don’t visit for 30 days it can’t be reached any more, so we delete it.

• What you write and do: tasks, steps, projects, notes, directions, rewards, focus sessions, reflections, weekly letters, progress, days you take off, your companion’s look, wanders and finds, and whether you have Glimby Plus (including the preview). What you tell your companion you’ll do in a focus session stays on your device

  Why

  This is the app. Contract.

  Kept

  Until you delete it or your account.

• If you use Plan with Glimby (Glimby Plus): the tasks you pick (their titles and estimates, any time or part of the day you gave them, and whether they’re due soon or marked as dreaded) and how much you can take on today go to the AI provider to suggest an order, times and first steps. Nothing from your calendar is ever sent; Glimby fits the plan around it itself

  Why

  To make the plan you asked for. Contract. With AI off, Glimby makes the plan on its own and nothing is sent.

  Kept

  The AI provider doesn’t keep it for training. What you apply becomes ordinary tasks and steps; a note of the first day you used it is kept so Glimby asks about it once, after two weeks.

• If you turn on backup reminders (Glimby Plus): we email the address on your account when a “don’t let me forget” item’s nudges get no answer. The email says when; it names the task only if you choose that

  Why

  So a reminder you asked for still reaches you. Contract. Sent through our email provider (see “Who helps us run Glimby”).

  Kept

  We keep only that a backup was sent, and when, with your nudge history. Turn backups off in Settings or with the link in any of the emails.

• If you connect a calendar (Glimby Plus): its secret link, stored encrypted and never shown again, and the next two weeks of busy times from it. Event names only if you turn them on

  Why

  To show your real day on Today and say when it’s time to get ready. Contract. Glimby only reads the calendar, at most hourly, and never sends anything from it to an AI provider.

  Kept

  Until you remove the calendar (Settings → Glimby Plus), which deletes the link and every busy time at once, or your account. Busy times are replaced on every read and cleared when Plus ends; the link waits, in case you come back, until you remove it.

• Daily check-ins: how much you can take on each day (light, normal or full)

  Why

  To suggest tasks that fit your day. Contract. Turn the question off in Settings any time.

  Kept

  Until you delete them (Settings → Your data) or your account.

• Sign-in sessions: a cookie, plus the IP address and browser type of each

  Why

  To keep you signed in and spot sign-ins that aren’t you. Legitimate interest in security.

  Kept

  30 days after your last visit, or until you sign out.

• Abuse protection: IP addresses

  Why

  To slow down automated sign-in attempts. Legitimate interest in security.

  Kept

  One hour after the last attempt.

• Usage stats: which days you opened Glimby, a few milestones (finishing setup, saving a guest account, installing the app, turning nudges on, reaching the daily AI limit, telling your companion a plan before focusing and how it went, taking a day off, opening a feature that isn’t built yet, choosing your companion’s look, sending it on a wander and opening what it found, joining or leaving the Plus preview, connecting or removing a calendar, starting a routine from a template, asking for or applying a day plan, your one-tap answer to the week-two check-in, and your answer if you choose to say how you’d feel without Glimby or a Plus feature), and where your first visit came from (a link’s campaign tag, or the name of the site that linked here, never the full address). Never what you wrote, never your IP. Also how fast Glimby responds on your device (timings only, with the kind of page and of device, linked to no one)

  Why

  To learn whether Glimby actually helps people come back, and which ways of finding it bring people who stay. Legitimate interest. Turn it off under Settings → Your data and what we have is erased.

  Kept

  Until you turn it off or delete your account.

• A calendar link, if you make one: a secret link your calendar app uses to fetch the titles and times of your timed plans and deadlines. We keep only a scrambled (hashed) form of it

  Why

  So your calendar can show your plans. Your choice: turn it off in Settings → Nudges and the link stops working.

  Kept

  Until you turn it off, make a new one, or delete your account.

• A display link, if you make one: a secret link that shows today on a screen of your choice, with counts and times only unless you turn titles on. We keep only a scrambled (hashed) form of it

  Why

  So Today can stay in view without opening the app. Your choice: turn it off in Settings → Nudges and the link stops working.

  Kept

  Until you turn it off, make a new one, or delete your account.

• Features you asked to hear about, when you tap “Tell me when it’s ready” on one that isn’t built yet

  Why

  To tell you when it’s ready. Consent: take yourself off the list in the same place.

  Kept

  Until you take yourself off, we’ve told you it’s ready, or we decide not to build it.

• AI usage counts: how many AI helps you used and what they cost

  Why

  To keep a fair daily allowance. Legitimate interest.

  Kept

  Until you delete your account.

• Notifications: an address your browser gives us, which browser it is, and a log of the nudges we sent and whether you opened them

  Why

  To send the reminders you asked for, and ease off when they aren’t helping. Consent.

  Kept

  The address until you turn notifications off; the log until you delete your account.

• Feedback you send, and whether we may reply

  Why

  To fix problems and improve Glimby. Legitimate interest.

  Kept

  Until you delete your account, or ask us to delete it.

• Privacy requests: who asked, what for, when, and what we did

  Why

  To show we answered within the legal time limits. Legal obligation.

  Kept

  Three years after the request is closed, even if you delete your account.

• A log of what the operator did in Glimby’s admin tools, such as looking up an account

  Why

  So access to accounts is accountable. Legitimate interest in security.

  Kept

  Two years.

• Technical logs, such as error messages

  Why

  To keep the service running and fix bugs. Legitimate interest.

  Kept

  Only as long as needed to fix the problem.

Deleting your account removes your data from the live database straight away. We back up the database every night to Cloudflare R2 (Western Europe), and backups are deleted within 30 days, so a deleted account is gone from them by then.

• No advertising, and no third-party analytics, pixels or trackers.
• We don’t sell your data, and we don’t share it for targeted advertising.
• We don’t use your data to train AI models, and our AI providers don’t either.
• No marketing email. Glimby only emails you to confirm the address you sign up with, when you ask for a password reset link, and backup reminders if you turn them on. We reply when you write to us.
• No automated decisions that have legal or similarly significant effects on you.
• We don’t read what you write. To help you or answer a request, the operator can look up facts about an account (like when it started and what you’ve agreed to), but the admin tools never show your tasks, notes, reflections or check-ins, and every lookup is logged.

Some features use an AI model: suggesting a size, energy and traits for new tasks, breaking a task into steps, helping when you’re stuck, and writing your weekly letter. AI is on unless you turn it off, when you set up or any time in Settings. Then Glimby uses its own built-in suggestions and nothing is sent.

While AI is on, we send only what each feature needs:

• When you add tasks: each new task’s title, for the size, energy and trait suggestions.
• For a breakdown: that task’s title and notes.
• When you’re stuck: the step and its task’s title.
• When you ask Glimby to sort your inbox: the titles of the items waiting there (up to 30). Nothing moves until you confirm.
• For a voice note, on a device without built-in dictation (like an iPhone Home Screen app): the recording goes to OpenAI to be turned into text. Glimby never stores the audio; the words come back into your brain dump for you to edit.
• For a weekly letter: the name you gave Glimby, a few simple numbers about your week (like tasks finished, focus minutes and active days), the words you typed into the reflection.

This copy of Glimby uses Anthropic's API, and OpenAI’s for voice notes. Under their API terms, providers don’t train on this data and may keep it for a limited time (typically up to 30 days) to detect abuse. AI-written text is labelled in the app, and it can be wrong: it isn’t advice.

Glimby uses a few small cookies, all for signing in: the one that keeps you signed in, a short-lived copy that saves a trip to the database, brief ones while a passkey or Google sign-in completes, and one that remembers how you signed in last time (for example “passkey”) for 30 days, so the sign-in page can point you to it. It also saves a few things in your browser’s storage, like half-typed drafts, display preferences, which tips you’ve dismissed, and (for the current visit only) whether it has already invited you to install Glimby. Anything you capture without a connection waits there too, until it’s saved to your account; then it’s removed, and signing out empties it. A copy of Glimby’s offline page and its app files is kept so Glimby can open without a connection; it holds nothing about you. All of this is needed for the app to work as you’d expect, so there’s no cookie banner. Nothing on your device is read by anyone but Glimby.

A few companies process data for us, under contracts that limit them to doing that job:

• Hosting: DigitalOcean (Frankfurt, Germany). They store everything listed above.
• Delivery and protection: Cloudflare (USA) sits in front of our servers, delivering pages securely and blocking attacks. It sees your IP address and requests on the way through, but doesn’t keep your Glimby data.
• Backups: Cloudflare R2 (Western Europe) keeps our nightly database backups, deleted after 30 days.
• AI: Anthropic, while AI is on, as described above.
• Error reports: when something breaks on our servers, Sentry (EU region) receives the technical details so we can fix it: the error and where in the code it happened, never what you wrote or who you are.
• Notifications: if you turn them on, reminders travel through your browser maker’s push service (for example Apple, Google or Mozilla). Their content is encrypted on the way.
• Sign in with Google: only if you choose it. They share your name, email and a link to your profile picture. Their own privacy policies apply to your account with them, and none of their code loads on Glimby’s pages until you press the button.
• Email: Resend delivers the emails that confirm your address, reset your password, and carry backup reminders if you turn them on. It receives your email address and the message.
• Email you send us: messages to our addresses reach us through Cloudflare Email Routing into our Gmail inbox (Google), where they’re kept until we delete them.
• Leaked-password check: when you choose a password, we check it against Have I Been Pwned’s list of leaked passwords. Only the first five characters of a one-way scrambled (hashed) version leave our server, so neither your password nor your email is ever shared.

When paid plans arrive, a payment company will act as the seller and handle your payment details; we never see your card. We’ll update this policy before that happens.

Some of these companies are in the United States or other countries outside the EU and UK. When your data goes there, it’s protected by an adequacy decision (such as the EU-US Data Privacy Framework, where the company is certified) or by the European Commission’s standard contractual clauses (and the UK addendum). Ask us for a copy of the safeguards.

Wherever you live, you can:

• See and download everything: Settings → Your data → Download my data (a JSON file you can take elsewhere).
• Correct your name and everything you create, right in the app, or ask us to change your email.
• Delete your account and everything in it: Settings → Account → Delete account. It happens immediately.
• Withdraw consent, for example by turning off notifications. That doesn’t affect what happened before.
• Object to usage stats (turn them off in Settings), and ask us to restrict how we use your data.

For anything you can’t do in the app, contact us. We reply within a month, and usually much sooner. We may ask you to confirm the request comes from your account.

Please tell us first and we’ll try to put it right. You can also complain to a data protection authority: in the EU, the one where you live or work; in the UK, the Information Commissioner’s Office; in Armenia, the Personal Data Protection Agency.

Some US states, including California, Connecticut, Colorado, Virginia, Washington and Nevada, give you specific privacy rights. Here is how they apply to Glimby:

• We collect the categories listed above (identifiers, the content you create and usage information), for the purposes listed above.
• We don’t sell personal data, share it for cross-context behavioural advertising, or use it for targeted advertising or profiling.
• We don’t collect sensitive data such as health information. The consumer health data policy explains how we handle anything that could touch on it.
• You can access, correct, delete and get a copy of your data as described above. We won’t treat you differently for using these rights.
• If we turn down a request, you can appeal by replying with “Appeal” in the subject. We’ll answer within 45 days. If you’re still not satisfied, you can contact your state’s attorney general.

Glimby is for adults, 18 and over. We don’t knowingly collect data from anyone younger. If you think a child is using Glimby, tell us and we’ll delete the account.

Connections are encrypted (HTTPS), passwords are hashed, and access to the database is limited to the people who run Glimby. No system is perfect, so if we ever have a breach that puts you at risk, we’ll tell you and the authorities as the law requires. Found a security problem? See reporting a vulnerability.

When we change this policy, the date at the top changes. If a change matters, like a new kind of data or a new company helping us, we’ll tell you in the app before it takes effect, and ask again where consent is needed.