FrecklesOpen Freckles

Privacy policy

Last updated 31 October 2026 · version v2

This says what Freckles stores about you, why, for how long, who helps us run it, and how you can get it back or have it deleted. We keep what we need and no more. We don’t sell your information, and there is no advertising or tracking in Freckles.

Who is responsible

Freckles. Until a contact address is published here, use the feedback button inside Freckles.

We are the “controller” of the information below for running Freckles. For what the visitors and users of your app put into it, you are the controller and we are your processor: we only store and show it for you.

What we store, and why

WhatWhyHow long
Your sign-in email, your name (the one you give us after signing up, and the one Google or Microsoft gives), and how you sign in (Google, Microsoft, GitHub or an email link)To know who you are, and to let you in again.While your account exists.
Your apps, their versions and pictures of them, the notes you save with each versionTo do what you came for: keep every step, and go back to any of them.While your account exists, or until you delete the app.
Who you shared an app with (their email addresses and what they may do), your team’s membersTo decide who may open an app, and to show it in their “Shared with me”.Until you remove them or delete the app or account.
Notes and comments on apps (who wrote them, when, what they pointed at)So the people on an app can talk about it.Until the note, the app or the account is deleted. If the writer deletes their account, their words stay and show “Deleted account”.
How many signed-in people viewed an app, and how much of the built-in data store it usedTo show you who uses it, and to apply plan limits.While the app exists.
Plan and billing records: your Stripe customer number, your plan and its changes, the terms you accepted and the limit you chose, what your apps cost each day, every charge and bill, the notices we sent you, failed payments and disputes. Card details never reach us: they are entered on Stripe’s own pagesTo give you your plan, charge what you owe and tell you first, answer a dispute, and keep the invoices the law requires.While your account exists. After deletion, only Stripe’s customer number is kept, so invoices can be found for the accounts.
If your app sells things through Freckles’ payment button: what it sells (names and prices you set) and each payment that completes on it (the item, how many, the amount, the date, and the email address the customer gave to Stripe). The customer’s card details never reach us; the money goes to your own Stripe accountTo show you what was paid, and to help you with refunds and questions. Customers’ addresses are shown only to you and your agent.While the app exists. If you delete your account, they are deleted with it; you can export them first.
For a domain you buy: your name, postal address, phone and email as the registry requires, the domain, and when it endsTo register the domain in your name and remind you before it ends.The contact details are deleted 30 days after the domain was registered and handed to you; the domain and its end date stay while your account does.
The computers your agent is connected on (their names, system and last use), and which plugin version they runSo you can see and disconnect them, and tell you when one is out of date.Until you disconnect it or delete your account.
What you send us in feedback, with the page and a picture if you add oneTo fix and improve things.Until you delete your account (or until we have dealt with it, if sooner).
Reports of abuse sent by anyone: the address reported, what was said, and the reporter’s email if they gave oneTo look into the report and answer it.While we need them to deal with the report and any appeal.
A small record of when you accepted the terms, and an audit record when an account is suspended or deletedTo show that rules were agreed to and applied.Terms: while your account exists. Deletion record: a hashed number and a date, with nothing that names you.
If a phone check applies to your account: the last two digits of your mobile number, when it was checked, and a one-way scrambled version of the number (a keyed hash, which can’t be turned back into the number). We never store the number itselfTo stop one person making many accounts: the scrambled version lets us see that a phone is already used by another account.While your account exists. When you delete your account, the scrambled version is deleted too, so the number can be used again.
Counters kept to limit abuse: how many sign-in emails, accounts or codes were asked for from one connection or address in a day or an hour. Each is kept under a scrambled version of the address or connection, never the address itselfTo stop floods of sign-ups and emails sent in our name.A few hours to a day, then they are removed.
Technical logs of requests (address of the visitor, time, page, errors)To keep the service running, find faults and stop attacks.A short time, then they are removed.
Aggregate counts: sign-ups, page views of our own pages and which website they came from, and how many accounts reached each step per day. On your account, the dates you first connected a computer, saved a version, published and shared, and when you were last active; and what your apps cost this monthTo see whether it works for people and what it costs to run. Counts carry no names, addresses or browser details, nothing is sent to a third party and no cookie is used for them.The daily counts are kept. The dates and the cost go when your account is deleted.
Which features you asked about: when you press “Tell me more” on something that is coming shortly, we note that your account asked, how many times, and when. It is kept under a one-way scrambled version of your account, never your name or address, and only added up into counts for the person who runs FrecklesTo see which features people want before we build them.The daily counts are kept. The note about your account goes when you delete your account.

We use only one cookie: the one that keeps you signed in. It is needed for Freckles to work, so there is no cookie banner. People opening an app that was shared with them get a cookie that remembers who they signed in as, for a day or so.

The legal reasons

  • To give you the service you asked for (a contract): your account, apps, versions, sharing, plan and domain.
  • Our legitimate interest in running a safe service: logs, stopping abuse, looking into reports, keeping the audit record.
  • The law: keeping invoices, and answering the authorities.
  • Your consent, where we ask for it (for instance when you attach a picture to feedback), which you can take back.

Who helps us run it

We use these companies to run Freckles. Each only gets what it needs to do its part, under terms that protect it.

  • Microsoft Azure: where Freckles, your published apps and our records run and are stored, and the email service that sends sign-in links and alerts. This is in the United States: Azure’s East US 2 region (Virginia), with backup copies in its Central US region (Iowa).
  • Stripe: payments for your Freckles plan (it keeps your card and charges it when we ask), and the payments on your apps through your own Stripe account. Stripe is also a controller of what it collects for fraud and law.
  • Porkbun: registers the domains you buy through us, and holds the contact details the registry requires.
  • GitHub: stores the history of the apps we keep for you, in private repositories, and a private copy of a GitHub project of yours only if you connect GitHub and choose Continue in Freckles for it (you pick which projects Freckles may read, and can take that access away on GitHub at any time). Your own project is never written to, except when you ask your assistant to send your work back to it.
  • Twilio: when a phone check applies to you, it sends the code by text or call to the number you enter and tells us whether the code was right (and what kind of line it is). Twilio sees that number to do so; we keep none of it afterwards, only what the table above says.
  • Google, Microsoft and GitHub, as sign-in providers: when you sign in with them, they tell us your name and a verified email address. They are separate controllers of their own accounts.

Freckles itself runs in the United States, so if you are in the European Economic Area, the United Kingdom or Switzerland, what we store about you is transferred there. Some of the other companies above are outside those places too, or may process information there. For each transfer we rely on the safeguards the law allows: the EU–US Data Privacy Framework (and its UK and Swiss extensions) where the company is certified under it, as Microsoft is, and otherwise the European Commission’s standard contractual clauses (with the UK addendum) in that company’s data protection terms. You can ask us for a copy of the safeguards that apply.

Your rights, and how to use them

If you are in the European Union, the United Kingdom, or somewhere with similar law, you have the right to:

  • Get a copy of what we hold (access and portability): Settings → Your data → “Download my data” gives you everything as one JSON file, at once.
  • Have it deleted (erasure): Settings → Your data → “Delete my account” takes your apps offline and deletes your records, pictures, sign-in methods, connected computers and team. What you wrote on other people’s apps stays but shows “Deleted account”. We keep only what the law requires (Stripe’s invoice number) and a record that an account was deleted, with no name in it.
  • Correct it: change your details in Settings, or write to us.
  • Object, or ask us to limit how we use it, and take back consent, by writing to us.
  • Complain to the data protection authority where you live or work. We would like the chance to put it right first.

You can also sign out of every browser at once (Settings → Your data). To use a right in another way, write to the feedback button inside Freckles. We answer within one month. We may ask you to prove who you are first, so that nobody can get someone else’s information.

Keeping it safe

Everything is encrypted on its way to and from you. Records are kept in our storage in Azure, reached with Freckles’ own identity and no stored passwords. Sign-in codes are kept only as hashes. We limit who can reach the records, and we tell you and the authorities if something goes wrong that the law says we must.

Children

Freckles is not for people under 16, and we don’t knowingly keep their information. If you think a child has an account, write to us and we will delete it.

Changes

When this policy changes in a way that matters, we will tell you and put the date at the top of this page.

Contact

Privacy questions and requests: the feedback button inside Freckles.

TermsAcceptable usePrivacy