1Cookies and browser storage
Cookies are small pieces of data stored by your browser and sent with requests to a website. Browser session storage keeps data in a browser tab. This notice covers Tinkerly's website and app and supplements our Privacy Policy.
2What we use
Sign-in and security
Supabase authentication cookies keep you signed in and refresh your session. They use names beginning with sb-, sometimes split across several cookies. Their lifetime follows the sign-in session and provider configuration. Signing out clears your session. Google and GitHub also handle cookies on their own sites when you choose those sign-in methods.
Community view counts
When a signed-out visitor opens a community project, we set a first-party cookie named tk_vid containing a random identifier, with a maximum lifetime of one year. It helps count a project view once per visitor per UTC day and attribute sharing events. It is not an advertising identifier. Signed-in views use your account identifier instead.
Work in progress
We use session storage for your draft prompt, Build, Plan and Chat conversations, generation state and attachment references. This lets the same tab recover your work after a reload. Your browser normally clears session storage when the tab closes, although browser session restoration can retain it. Clearing site data removes this browser copy; saved projects remain in your account.
Payments
Stripe's payment components may use cookies and similar technologies for payment processing and fraud prevention. Stripe determines their lifetimes. Read Stripe's Cookie Policy for its current details.
Staff support sessions
Authorized staff support sessions use short-lived cookies to identify and limit an impersonation session and show its visible support banner. These are not advertising cookies.
Analytics and session replay
When analytics is on (see below for when that is), our analytics library keeps random identifiers for your browser and your current visit in browser storage, in entries whose names begin with ph_. A first-party cookie named tk_region records, for one day, whether your region requires us to ask first; it holds only that answer, not your location. If you make a choice, Allow or No thanks, it is kept in a first-party cookie named tk_consent for 12 months.
Where you came from
When analytics is on, a first-party cookie named tk_src remembers, for 90 days, the first and the most recent way you arrived at Tinkerly: campaign tags in the link (such as utm_source or ref), or the name of the site that linked to us. It holds no identifier. If you then create an account, we keep that first and last source with your account. In the EU, EEA, UK and Switzerland it is set only after you choose Allow, and never when your browser sends Global Privacy Control or Do Not Track; choosing No thanks removes it.
We do not use advertising cookies, and no third party receives our analytics or replays.
3Analytics and session replay
In the European Union, the rest of the European Economic Area, the United Kingdom and Switzerland, we ask before collecting anything: nothing loads and nothing is sent until you choose Allow. We work out the region from the country our hosting provider reports for your connection; if it cannot tell, we ask. Everywhere else, analytics is on by default and you can turn it off at any time below.
Wherever you are, if your browser sends a Global Privacy Control or Do Not Track signal, we treat it as No thanks: analytics stays off and we do not ask.
With your permission we record the pages you open, what you click and type into, errors your browser hits, how quickly pages load, and a replay of the visit: what appeared on screen and how the pointer moved. Passwords are always hidden in replays, card fields are never recorded, and sign-in, checkout, billing, API key and staff pages are never recorded at all. Web addresses are stored without their query strings, except campaign tags such as utm_source. We do not store your IP address; we keep only the country it comes from, plus your browser, operating system and device type.
All of it goes to Tinkerly's own collector and is stored in our own database and file storage at Supabase. We use the open-source posthog-js library to collect it, but nothing is sent to PostHog or to any other analytics company. Only a small number of staff can see it.
We also count, for every visit and without any cookie or identifier, how many visits arrived from each campaign tag or referring site per day. Those counts cannot be linked to you.
We keep events, sessions and error reports for 90 days and replays for 30 days, then delete them automatically. Daily visit counts are kept for 24 months. The source attached to an account is kept until the account is deleted.
4Your controls
Your browser settings let you inspect, block or delete cookies and clear site storage. Apply these settings separately to each browser and device. Blocking authentication cookies can prevent sign-in, and clearing session storage can remove unsaved conversations and drafts.
You can read public pages without an account. Signing out ends your account session; clearing all site data also removes the community visitor cookie, your analytics choice, the analytics identifiers and the tk_src source cookie.
You can change your analytics choice at any time:
5Changes and questions
We update this notice when our use of browser storage changes. Contact hello@tinkerly.dev with questions about cookies or your data.