This policy lists everything PrysM Tools stores on your device, cookies and browser storage alike, what each entry is for, how long it lasts, and how to refuse the ones that are not strictly necessary.
What this covers
A cookie is a small file a site asks your browser to keep. The same rules apply to anything else written to your device for the same purposes: localStorage, sessionStorage, IndexedDB and similar. We call all of it storage here, and this policy covers all of it.
Under French and EU law, storage that is strictly necessary to deliver a service you asked for may be used without permission. Everything else needs your consent before it is written, and that consent must be as easy to refuse as to give, and as easy to withdraw later.
Strictly necessary | used without consent
| Entry | What it does | Lifetime |
|---|---|---|
sb-*-auth-token | Keeps you signed in and refreshes your session. Set by our authentication provider. Without it you would be signed out on every page. | Session, refreshed while you stay active |
prism.ui-lang | Remembers the interface language you picked, so the site does not reset to English on every visit. | Until you clear it |
prysm.geo-lang | Starts the site in the language of the country you browse from (France: French, Italy: Italian, Spain: Spanish, Germany and Austria: German, anywhere else: English) until you pick one yourself. It holds only that language code: neither your IP address nor your country is kept. | 30 days |
prysm.cloud-upsell.* | Remembers that a storage notice was already shown today, so it does not reappear on every page load. | Written per day; stale entries are inert |
prysm.consent | Remembers your answer to the measurement notice, and nothing else, so you are not asked again on every page. | 13 months if you accept, 6 months if you refuse |
| Editor draft state | Your work in progress, held in your own browser so a refresh does not lose it. It is never transmitted to us unless you export or save to the cloud. | Until you clear it |
__stripe_mid, __stripe_sid | Set by Stripe, our payment processor, only on the pages where you pay, the checkout and the single-document unlock. Used to detect and prevent payment fraud. Stripe.js is never loaded anywhere else on the site. | One year (mid) and 30 minutes (sid) |
These carry no identifier used to follow you across sites. Only the two Stripe entries involve a third party, and only for the payment you are making, see the sub-processor list.
Measurement | only if you agree
We want to know which features are used and where the interface loses people: which templates get opened, where an export is abandoned, which errors people actually hit. That means counting interactions, pages viewed, links and buttons clicked, how far a page is scrolled, which parts of it came into view, and where a visit ended.
What reaches our servers is a count, not a record of who did it: for example, one more view of /docs. No identifier, no IP address and no device details are stored with it, and nothing typed into a form is ever measured. Accounts created are also counted in total by our own database, for everyone, that is a tally of accounts we already hold, not information read from your device.
What we do and do not do with it
We do. Aggregate it to decide what to build and what to fix. Keep it inside our own infrastructure. Give you a real choice before any of it is written.
We do not. Sell it, rent it, or share it with advertisers or data brokers. Use it to build an advertising profile. Combine it with data from other sites. Record the content of your documents: measurement captures that an action happened, never what was in the fields.
| Entry | What it does | Legal basis | Lifetime |
|---|---|---|---|
prysm.m (session storage) | Marks a visit as begun, and which steps it has reached, for example that the pricing was seen, so a visit is counted once rather than once per page. It never leaves your browser. | Your consent, withdrawable at any time | Erased when the tab is closed |
| Aggregate counts on our servers | Audience measurement and feature analytics, as counts per day. Held in our own database, in the European Union. | Your consent, withdrawable at any time | 25 months |
None of this is written before you have agreed to it through our cookie notice, and you can change your answer at any time from the Cookie preferences link at the foot of every page. Refusing is as easy as accepting, both choices are offered on the first screen, nothing is pre-ticked, and you can change your answer at any time afterwards.
What we never use
- No advertising cookies. We run no advertising and host no advertising tags.
- No third-party trackers. No social widgets, no pixels, no tag managers loading other companies’ scripts.
- No cross-site tracking. Nothing we store follows you to another website.
- No fingerprinting. We do not attempt to identify a device by combining its characteristics.
- No selling. Nothing collected here is sold, rented or exchanged. Ever.
Giving, refusing and withdrawing consent
Refusing costs you nothing
The Service works identically whether you accept measurement or not. No feature is withheld, no notice keeps reappearing to wear you down.
Changing your mind
Consent can be withdrawn at any time, and withdrawing is as easy as giving it. Your choice is remembered for a maximum of six months if you refuse, after which you may be asked again, no more often than that.
If you do nothing
Continuing to browse is not consent. Closing the notice without choosing is not consent. Absent a clear positive action, only the strictly necessary entries are written.
Browser-level controls
Independently of our own controls, every major browser lets you view, block and delete storage, per site or globally, under its privacy settings.
Blocking strictly necessary entries will sign you out and may lose unsaved editor work; the Service cannot keep you signed in without them. We also honour the Global Privacy Control signal where your browser sends it, treating it as a refusal of non-essential storage.
Related
How we handle personal data more broadly is in the Privacy Policy; the providers involved are listed under Sub-processors.
Changes to this policy
If we add a category of storage, this page is updated first and, where the new category needs consent, you are asked before anything is written. The date at the top always reflects the current state.
A question about any of this?
Write to legal@prysm.tools and a person will answer.
Published in English. Any translation is provided for convenience only; where they differ, the English text prevails, except where mandatory local consumer law provides otherwise.