What this covers.
Cookies and local or session storage keep information in your browser. This page covers storage used by the shapes website and app, optional PostHog browser analytics, and how this differs from published-page statistics and creator-selected third parties. See the Privacy Policy for the information processed and your rights.
Necessary cookies.
We use these cookies for requested account and security functions, not advertising. They are separate from the optional analytics choice:
- tp_auth: keeps you signed in. It is created when you sign in, lasts up to 30 days, and is readable only by our servers.
- _csrf: a server-readable security cookie created when the app requests an anti-forgery token, used to protect account actions from other websites. No persistent expiry is configured for this cookie; browser session-restoration behaviour can affect how long it remains.
- tp_oauth: used only while you sign in with Google, to check that the sign-in came from you. It lasts about 10 minutes.
Functional browser storage.
The following browser storage and preferences support requested features. Local storage normally remains until the app or you remove it; session storage normally lasts for the tab’s session. Browser settings can change this behaviour. We use:
- Local draft backups in the editor to help recover unsaved changes. Backups are updated or removed by editor actions; content you recover can be saved to your account. Clearing browser data removes unsaved backups.
- Local flags remembering dismissed editor hints, until cleared.
- Session storage for a pending billing choice so it can be resumed after sign-in. It is removed when the billing flow consumes it or the browser session ends.
- shapes_cookie_consent: a local-storage preference managed by CookieConsent that remembers your analytics storage choice. Revision 2 expires after 180 days; choices saved under an older revision require a new choice before analytics resumes. You can change or clear this preference sooner. Remembering a rejection is not consent to analytics.
PostHog browser analytics and session replay.
Optional browser analytics and session replay are off unless you accept them. Accept and reject options are available in the consent control, and you can reopen it with Cookie settings. No analytics events are sent while your choice is pending. Rejecting optional cookies turns all of it off, and nothing is sent to PostHog from your browser. Your choice applies to this browser; another browser or clearing browser data may require a new choice. You can keep using shapes if you reject.
If accepted, PostHog uses local storage for browser identifiers to connect selected feature events and sanitised route labels across visits. Signed-in events can be associated with your shapes account identifier. Session replay records what you do on shapes pages and the editor so we can see where people get stuck. Replays hide on-screen text, form entries, images, media and page addresses, and exclude network requests and console logs. We do not enable automatic interaction capture or browser exception capture, or send raw page URLs, referrers, names or emails as analytics properties.
PostHog identifier storage, commonly named with a ph_ prefix, remains until cleared by the app or browser. Withdrawing acceptance removes shapes-managed PostHog identifier storage and stops analytics and session replay; browser settings can also inspect and clear it. This does not delete information already received by PostHog.
Session replay and analytics can still involve personal information, for example what you click and when, and masking cannot guarantee that nothing sensitive is captured, so do not enter secrets on pages you would not want recorded; reject optional cookies if you prefer. Global Privacy Control or Do Not Track signals also keep all shapes browser analytics and session replay off. Contact us if you wish to object to other processing or request deletion.
Visitors to published pages.
Our first-party page statistics use neither analytics cookies nor local storage. They still process request information such as IP addresses and browser details, generate short-lived pseudonymous visitor hashes and store aggregate counts. Cookieless does not necessarily mean anonymous or exempt from legal notice or consent requirements. See the Privacy Policy.
Browser PostHog analytics is not loaded on creator-published pages or custom domains, draft previews, share links or agent routes. Necessary cookies already in a browser may still accompany requests where their scope allows; this is not a promise that no cookie can ever be sent to a published-page address.
Creator-selected embeds, remote resources, payment tools and custom code can contact other providers and may involve their own cookies or data collection. shapes does not automatically block these until consent. Creators must implement any required prior-consent mechanism or omit the integration. Our Cookie settings control does not manage these third parties or replace a creator’s own privacy notice.
What the browser choice does not control.
Rejecting optional browser analytics does not stop necessary authentication, security logs, first-party published-page statistics, Stripe billing, or the AI processing involved in Cove and content moderation. Server-side PostHog operational AI usage metadata is separate from browser analytics and does not use a browser cookie. Its contents and purposes are described in the Privacy Policy.
We do not use shapes analytics for targeted advertising. Creator-selected providers operate under their own policies, and payments or sign-in flows may open another provider’s site with separate cookie controls.
Your choices.
Open Cookie settings in the shapes website or app footer, or the editor’s page menu, to accept or reject optional analytics and session replay, or change an earlier choice. These settings are in the footer or page menu rather than a floating control. Withdrawing consent stops all optional analytics and session replay; GPC or DNT does the same. Your choice does not undo processing already carried out or control creator integrations. No analytics consent is required to sign in or edit.
You can also inspect, block or delete cookies and browser storage in your browser settings. Blocking necessary cookies can prevent sign-in and account actions; deleting local storage can remove unsaved draft backups. Signing out removes the shapes sign-in cookie, not necessarily all other stored information.
Changes.
We update this page when our storage or analytics practices change and request new consent where required. Questions about storage or providers? Email [email protected].