Privacy, in plain language.
How the PostRoom beta handles workspace and reviewer information. Operated by Kartheek Akella in India. Updated 17 October 2026.
Information used to run your workspace
Clerk handles account sign-in and the identity information you provide during registration. PostRoom associates your Clerk account ID with rooms, client names, draft titles and text, chosen channels, planning dates, review feedback, activity records and API key labels. API key secrets and review-link tokens are stored as hashes rather than readable secrets.
What a reviewer shares
A reviewer can provide a name, an approval or request for changes, and feedback. These are stored with the draft’s workflow history and shown to the workspace owner. Reviewer names are self-reported. Reviewing does not require a PostRoom account.
Who can see submitted content
The owner can view workspace content. Anyone with an active room review link can see submitted drafts, including content already approved or sent back for changes. Private drafts are excluded from that review view. A link lasts seven days unless revoked or replaced sooner. People may retain copies of content they have already viewed; revoking a link does not recall those copies.
Service providers
PostRoom uses Clerk for authentication, and Cloudflare Workers hosting and D1 storage to operate the application. These providers may process account information, request metadata and service data needed to deliver their services. Read Clerk’s privacy policy and Cloudflare’s privacy policy for their practices.
PostRoom uses Creem for new Pro checkout and subscription billing when available. Earlier purchases may be handled by Dodo Payments or Razorpay. The applicable provider receives your verified account email, name and a random checkout reference to process and manage the purchase; PostRoom stores provider customer, subscription and transaction references and billing status to control paid access. Card details are entered on the payment provider’s checkout, not stored in PostRoom. See Creem’s privacy policy. Do not send card or bank details through drafts or feedback.
Cookies, storage and AI
Sign-in relies on Clerk’s session technology, including authentication cookies or browser storage. PostRoom uses server-side request counters to limit abuse. The current product does not run AI generation on your drafts. If you connect your own agent, you decide which external tool receives workspace data through the API.
Page analytics, optional Google Analytics and Cofounder analytics
PostRoom uses DataFast for automatic cookieless pageview estimates and limited blog-to-signup actions: article views, article signup or demo clicks, registration starts and new registrations. These actions include only a known public article slug and button position. Automatic browser payment detection is disabled. You can opt out with the page analytics control in the footer; existing saved analytics declines are preserved. Browser Global Privacy Control and Do Not Track preferences also stop this tracker.
Cookieless does not mean no information is processed. DataFast estimates visitors using a pseudonymous hash derived from IP address, browser user-agent and site domain, with a salt that rotates about every 24 hours. Its script does not use cookies for visitor identification, but may use session storage for the current tab. Your page analytics preference is stored locally so it persists. Read DataFast’s cookieless explanation and privacy policy.
DataFast pageviews and these limited actions pass through PostRoom to remove private review-link tokens, arbitrary query parameters, client content and unrecognized referral paths before forwarding. Only public page categories and allowed campaign labels are retained. We do not send your email, account ID, client names, draft content or feedback. Automatic browser payment detection is disabled.
Google Analytics remains optional. It loads only after you choose “Allow analytics” in Analytics preferences, and uses cookies to measure visits and product actions such as creating a room or requesting review. Advertising personalization and Google signals are disabled. Its page addresses and referrals are sanitized, and consented campaign labels may be retained in tab-scoped session storage. Blog-to-signup measurement uses the same limited actions and article/button labels; the article, button position and registration-start time may be kept in the current tab for up to 30 minutes to distinguish a new registration from signing in. Read Google’s privacy policy.
The same “Allow analytics” choice also enables Cofounder analytics, which is hosted by PostHog. It records sanitized page addresses, campaign tags, the referring site, your browser’s user agent and your screen and window size, sent through getpostroom.com/ingest so that no PostHog script loads in your browser. It receives the same sanitized page addresses, referral origins, allowed campaign labels and named product actions as Google Analytics. It stores a random visitor ID in local storage and a session ID in the current tab, creates no person profiles, and loads no third-party script. Declining clears both IDs. Read PostHog’s privacy policy.
Earlier Dodo checkouts may include a previously consented anonymous DataFast visitor cookie ID; Dodo’s integration may send payment amount, currency, transaction ID and that anonymous ID to DataFast. Creem checkout metadata contains only a random ownership reference, with no analytics visitor ID. The cookieless pageview tracker does not create a visitor cookie ID.
You can decline Google Analytics and Cofounder analytics or opt out of page analytics without affecting the service. Withdrawing a choice stops future tracking for that provider and clears its browser tracking storage; it does not automatically erase data already received by the provider.
Retention and deletion
Workspace data remains stored until it is deleted or removed as part of operating the service. Deleting a draft removes it from the board, but activity records may remain, including the deleted draft’s title, reviewer names and feedback. Deleting a Clerk sign-in account does not currently trigger automatic deletion of PostRoom workspace data. There is no published fixed retention schedule for this beta.
Use the contact page to request access, correction or removal of your information. A reviewer can also ask the workspace owner to help identify the room and content involved. We may need to verify a request before acting on it.