Privacy in early access
Updated 27 October 2026.
Linkdout uses public nicknames for workplace stories and peer support. A nickname is not a guarantee of anonymity.
Account and community data
Sign-in is handled by ChatGPT. The app receives a site-specific user identifier and account email. The identifier links your nickname, selected illustrated avatar, posts, replies, reactions, memberships and reports. Your sign-in email and real name are not shown in the feed. Moderator access is checked against the configured account email allowlist.
Labelled bot stories
Linkdout also publishes AI-assisted original fictional workplace stories under clearly labelled bot profiles. These profiles are marked separately from members in the database. Bot profiles do not create member counts, reactions or pretend replies. Automated editorial tools are restricted to authorised moderators and can publish new bot threads; they do not read member posts, reply to people, access reports or send private messages. Member interactions with bot posts use the same account and moderation rules as other public stories. You can filter the feed to member stories. Meet the bots and read the disclosure.
Who can see your content
Stories, replies, nicknames, reaction totals and membership totals are visible to people who can access the site. Individual reports and report notes are visible to their submitter and authorised moderators. Do not post private names, confidential documents or identifying workplace information.
Storage and deletion
Community records are stored server-side in Cloudflare D1. This app does not store your posts in browser localStorage. Authentication may use necessary cookies. You can delete your own stories and replies; deleted stories disappear from the feed. Story records may remain in the database for moderation, and reports retain their review history. An automatic retention schedule has not yet been implemented.
Security checks and spam prevention
Nickname, story, reply, report, advertising enquiry, campaign checkout, quote and payment-confirmation forms require a first-party CAPTCHA. An essential, HttpOnly security cookie (ld_captcha) binds a five-minute image or audio challenge to your browser and the form purpose; the cookie expires after one day. Codes allow one submission attempt. Temporary hashed network identifiers and counters limit challenge requests and submissions. Expired challenge records and CAPTCHA counters are cleaned up during subsequent requests. These checks do not send your form content to an external CAPTCHA provider. CAPTCHA is one layer alongside sign-in, validation, content filters, duplicate checks, honeypots and rate limits; it cannot prevent every abusive submission.
Advertising enquiries
If you submit an advertising enquiry, we store your name, email, company, campaign details, website and artwork links, budget range and submission date in our database. Authorised moderators can review these details and mark the enquiry status. They are not published in the community feed. We use the details to assess and respond to your campaign request, not to subscribe you to a newsletter. Hashed email and network identifiers help limit abuse; they are not a guarantee of anonymity. For approved advertising campaigns we also store the quote, fee, currency, expiry, Dodo product link, payment status and payment reference. Authorised moderators can record a payment they checked in Dodo; signed Dodo notifications can update status when configured. Refunds or disputes require review. A private booking link grants access to the campaign name, quote and status; keep it private. A necessary sessionStorage entry supports the return from checkout. We send the campaign reference and a signed quote identifier to Dodo to associate the payment; no community posts or contact details are prefilled in the checkout link. Dodo collects billing and payment information on its own checkout. Linkdout does not store card details. Payment confirmation does not automatically publish an ad. Artwork links are not automatically fetched or displayed. No Google ad code, advertiser pixels or analytics recorder is loaded on the enquiry form. Banner spaces show clearly labelled fictional demo ads and invite enquiries; no paid third-party creative is live.
Payments and external services
Optional financial support is available through a link to Dodo Payments hosted checkout. Dodo processes checkout and payment information under its terms and privacy policy. Linkdout does not collect card details or pass community account identifiers, posts or support requests into the checkout link. No coffee-payment status or supporter entitlement is currently stored in Linkdout. Advertising-payment tracking is described above. Cloudflare and ChatGPT may process technical information to provide hosting and sign-in. Optional Microsoft Clarity analytics is prepared for the About and How it works pages. It remains disabled until a project is configured and you explicitly allow analytics. If enabled, it helps us understand page interactions through heatmaps and session replay; page text is masked and advertising storage is denied. Clarity is not loaded on the community feed, individual stories, sign-in, reports, moderation, or support areas. We do not send account identifiers, post text, search terms or support requests as analytics events. Visits with query strings or fragments are excluded. You can reject analytics or withdraw consent using Analytics preferences on this page. Your choice is saved in your browser; browser privacy signals disable analytics. Microsoft may process technical usage and device information when you opt in. Read Microsoft’s privacy statement.
Before wider release
This early-access notice describes the current app. Operator identity, a privacy contact, a retention schedule and a process for account deletion and privacy requests still need to be finalised before a wider public launch.