CookMyPost Privacy Policy

Overview

CookMyPost is a Chrome extension that helps users save writing style examples from X posts and rewrite their own rough ideas using those saved style patterns.

This Privacy Policy explains what information CookMyPost collects, how we use it, and how we share it. By using CookMyPost, you agree to this policy.

Information We Collect

Account information: when you sign in, we receive and store account identifiers such as your email address, Clerk user ID, internal CookMyPost user ID, and subscription plan status.

Authentication information: we use session cookies and authentication tokens to keep you signed in and to let the extension communicate with the CookMyPost backend. We do not collect or store your password.

Saved style content: when you choose to save a style from X, we collect the selected post text, post URL, tweet ID, author handle or name when available, selected style aspects, optional notes you enter, and a generated writing style fingerprint.

Draft content: when you ask CookMyPost to rewrite a draft, we collect the rough idea text you submit and process it with your saved style context to generate rewritten versions.

Technical and security information: our servers may process request metadata such as IP address, timestamps, and rate-limit counters to provide the service, prevent abuse, secure the system, and diagnose errors.

Billing information: if paid plans are enabled, we may receive subscription status or plan information from Clerk Billing. Payment card numbers and full payment details are handled by Clerk or its payment processors, not by CookMyPost.

Information We Do Not Collect

We do not collect health information.

We do not collect personal communications such as emails, direct messages, text messages, or chat messages.

We do not collect full browsing history. CookMyPost only processes X post content or draft text when you use a CookMyPost feature.

We do not log mouse movement, keystrokes, scroll behavior, or unrelated user activity for analytics or advertising.

We do not sell personal information and we do not use personal information for personalized advertising.

How We Use Information

We use collected information to provide CookMyPost features, including signing users in, saving selected writing style examples, generating style fingerprints, retrieving saved style context, rewriting drafts, enforcing usage limits, managing plan status, preventing abuse, improving reliability, and responding to support or legal requests.

How We Share Information

We share information only as needed to provide and protect CookMyPost. Service providers may include Clerk for authentication and billing, HydraDB for private style memory storage and retrieval, OpenAI-compatible language model providers for style extraction and rewriting, hosting and database providers, and rate-limiting infrastructure such as Redis providers.

We may also disclose information if required by law, to protect the security or integrity of CookMyPost, or as part of a merger, acquisition, financing, or sale of assets, subject to appropriate protections.

We do not sell your data. We do not transfer your data for advertising, retargeting, or interest-based advertising.

Chrome Web Store Limited Use Disclosure

CookMyPost uses Chrome extension permissions and user data only to provide or improve its single purpose: saving selected X writing style examples and rewriting user-provided drafts using those saved styles.

CookMyPost transfers user data only when necessary to provide or improve this purpose, comply with law, prevent abuse or security issues, or complete a permitted business transaction.

CookMyPost does not use or transfer user data for personalized advertising, retargeting, or interest-based advertising.

CookMyPost does not allow humans to read user content except with your consent for support, when necessary for security and abuse investigation, to comply with law, or after the data has been aggregated and anonymized for internal operations.

Data Storage and Retention

Account records are kept while your account is active or as needed to provide the service, comply with legal obligations, resolve disputes, and enforce agreements.

Saved style examples and generated style fingerprints are kept in your private CookMyPost memory until you ask us to delete them or until your account is deleted, subject to backup and legal retention requirements.

Draft text submitted for rewriting is processed to generate output. CookMyPost does not intentionally store draft text in its primary user database, but draft text may be processed by our language model providers and may appear in transient logs or service-provider systems according to their terms and retention settings.

Rate-limit and security records are kept only as long as reasonably needed for abuse prevention, reliability, and security.

Security

We use HTTPS for data transmitted between the extension and the CookMyPost backend. Session cookies are configured with security protections where available, and access to backend systems is limited to authorized systems and service providers.

No method of transmission or storage is perfectly secure, but we work to protect user data using reasonable administrative, technical, and organizational safeguards.

Your Choices

You can sign out from the extension at any time. Uninstalling the extension removes local extension data from your browser, but it does not automatically delete server-side account records or saved style memory.

You may contact us to request access, correction, export, or deletion of your account data and saved style data.

Children

CookMyPost is not intended for children under 13, and we do not knowingly collect personal information from children under 13.

Changes

We may update this Privacy Policy from time to time. If we make material changes, we will update the Last updated date and, where appropriate, provide additional notice.

Contact

For privacy questions or data requests, contact us at privacy@cookmypost.com.