Cookie notice
Which cookies and browser storage the DataAttendant website and application use, what each is for, how long it lasts, and why none needs your consent.
1. The short version
- The website sets no cookie and stores nothing in your browser. It has no analytics and no advertising.
- The application sets no cookie. It keeps your work and your settings in your browser's own storage, because that is where the Service runs.
- Nothing here needs your consent, because each item is needed for the Service you asked for. So there is no cookie banner.
- Two providers may set their own cookies. Stripe may, on its payment pages. Cloudflare may, on the Account page when its security check is on (section 4).
2. Words used in this notice
- A cookie is a small file a website asks your browser to keep and send back with each request.
- Browser storage is space in your browser where a page keeps data without sending it anywhere. There are three kinds here: local storage, session storage, and IndexedDB, a database inside the browser.
The law treats both the same way. An item may be kept without consent only if it is strictly needed for a service that you asked for.
3. What the application keeps in your browser
None of these items is ever sent to us. They stay in the browser where you use DataAttendant.
| Item | Kind | What it is for | How long | Needed? |
|---|---|---|---|---|
dataattendant-local-store |
IndexedDB | Your saved data: your types, rule sets, plans, lists, the history of your exports, and your Protection keys, which are encrypted with your passphrase | Until you delete it on the Saved data page, or clear your browser's data | Yes: it is the Service itself |
dataattendant.auth |
Local storage | Your sign-in session, so that you stay signed in. It holds the codes that prove you are signed in, never your password | Until you sign out, or the session ends | Yes, once you sign in |
dataattendant.presentation |
Local storage | Your display choices: the density, the content width, the panels' sizes, the column widths, the tips you closed, and when your saved data locks by itself | Until you clear your browser's data | Yes: these are choices you made in the application, and keeping them is how the application shows what you asked for |
dataattendant.checkout-from |
Session storage | Where your account stood when you left for Stripe's payment page, so that the Account page can tell you when the payment has arrived | Until you close the tab | Yes, when you pay |
The application also uses the browser's channel between its own tabs, so that one open tab learns of a change made in another. It stores nothing.
4. Cookies of other providers
4.1 Stripe, when you pay
When you buy credits or change your level, the application takes you to Stripe's own pages, at checkout.stripe.com and billing.stripe.com. Stripe sets its own cookies and browser storage there, to take the payment and to prevent fraud. Stripe's cookie settings page lists, among others, __stripe_mid (one year) and __stripe_sid (30 minutes) for fraud prevention. It also lists eid (two months), for testing versions of its pages.
These are Stripe's, under Stripe's own policy: see Stripe's cookie policy. We do not receive them.
4.2 Cloudflare, on the Account page
When the security check is on, the Account page loads Cloudflare Turnstile before you sign up or sign in (see our privacy notice). Cloudflare states that Turnstile returns a single-use pass and sets the cookie cf_clearance only when a setting called pre-clearance is on. That setting is off for DataAttendant, so Cloudflare's check on the Account page does not set the pre-clearance cookie.
See Cloudflare's cookie policy.
5. How to remove them
You can delete everything the application keeps in your browser:
- your saved data, on the application's Saved data page;
- everything, in your browser's settings, under the site data of app.dataattendant.com.
Deleting the saved data also deletes your Protection keys. Without a backup, the values of your protected copies can then no longer be restored. Make a backup first, on the Saved data page.
6. What would change this
We would ask for your consent first, and add a choice that is as easy to refuse as to accept, if we ever wanted to:
- measure visits with a cookie or a script;
- show or measure advertising;
- keep anything in your browser that the Service you asked for does not need.
We have no plan to do any of these. We would update this notice first.