How we use cookies
TryCode uses essential cookies to keep access to your posts, support GitHub sign-in, and open password-protected documents. They are necessary for the features you request. The app currently uses no advertising or analytics cookies.
Cookies we set
| Cookie | Purpose | Lifetime |
|---|---|---|
tc_guest | Links guest posts and API keys to your browser. | Up to 1 year |
tc_session | Maintains GitHub sign-in. | Up to 30 days |
tc_oauth_state | Protects the GitHub sign-in process. | Up to 10 minutes or until sign-in ends |
tc_access_* | Confirms password entry for a specific post. | Up to 24 hours |
tc_view_* | Tracks views of a post with a view limit. | Up to 1 minute |
The asterisk in a name stands for a specific post ID. These cookies use HttpOnly and SameSite=Lax; in production they are sent only over HTTPS.
Data in your browser
Besides cookies, your browser may store your collaborative editing name and appearance in sessionStorage, and the settings panel state and cookie notice dismissal in localStorage. This data stays on your device and is not used for advertising.
Managing cookies
You can remove cookies and site data in your browser settings. Removing the guest cookie may make guest posts and API keys inaccessible from this browser. Removing the session cookie signs you out; removing an access cookie requires you to enter the password again.
Changes
If optional cookies are added, we will update this page and provide a separate choice before using them.