Privacy Policy
Last updated: October 1, 2026
This Privacy Policy explains how Heddle Studio ("Heddle", "we", "us") processes information when you use heddle.studio and related services. Contact: support@heddle.studio.
1. Information we process
- Account information: authentication identifiers, name, email, profile image and sign-in method provided through Clerk.
- Connected accounts: X or LinkedIn profile details, access and refresh tokens, permissions and connection status needed to manage and publish through accounts you authorize.
- Your material and work: imported URLs and document text, extracted insights and source references, uploaded and generated images, prompts, conversations, research boards, outlines, draft versions and publishing records.
- Personalization: writing preferences, their scope and supporting conversation excerpts, proposed memories, the edits you make to generated drafts (on the canvas, and in the editor before publishing) and the writing patterns detected from them, saved content history and your choices about using it. Search indexes and embeddings help retrieve saved material and memories.
- Usage and billing: plan, credit balance, transaction references, feature use and model usage. Creem handles payment-card information; Heddle does not store card details.
- Technical information: request and error logs, device/browser information, authentication state and local preferences. Diagnostic records may include task or model content when diagnostic tracing is enabled.
Information from Google Sign-In
If you choose to sign in with Google, Google shares your name, email address and profile picture with Heddle through our authentication provider, Clerk. We request only the basic openid, email and profile permissions. Heddle does not request access to Gmail, Google Drive, Google Calendar, Google Contacts or any other Google account data.
We use this information only to create and secure your Heddle account, recognize you when you sign in, and show your name and picture inside Heddle. We do not sell it, use it for advertising, or use it to train AI models. We share it only with Clerk to provide sign-in, or where required by law.
Heddle's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
You can remove Heddle's access at any time in your Google Account permissions. To delete the account data Heddle holds, contact support@heddle.studio.
2. Why we use it
We process this information to authenticate you, store and retrieve your work, analyze sources, generate and review content, personalize writing, publish when you request it, process billing, provide support and protect the Service against abuse.
You can edit or decline proposed memories before saving them. An explicit request to remember a preference can save it directly, with undo. Suggested historical references require your selection; an explicit request to recall past work can authorize direct retrieval. Current instructions take priority over saved preferences. Closing a session does not itself authorize automatic memory extraction. We compare generated drafts with your edits to detect recurring writing-style patterns, such as removing emoji or shortening posts. These comparisons use fixed rules, not AI models. A pattern is only suggested after it recurs across three writing sessions. It takes effect only if you confirm it, and confirmed changes can be undone. Edit analysis covers writing style only; it does not learn facts from your content.
3. Service providers and sharing
We use providers to operate the Service and do not sell personal data.
| Provider | Information and purpose |
|---|---|
| Clerk | Account information and authentication |
| Creem | Payments, subscriptions, tax and invoicing; image prompts sent for content moderation |
| OpenRouter and the model providers it routes to, including Anthropic and Google | Relevant prompts, instructions, source material, selected memories and drafts for generation and review; image prompts for image generation |
| Tavily and SocialData | Search queries and context needed for web or X research |
| X and LinkedIn | Account authorization and content/media you request to publish |
| Hosting, storage and delivery providers | Storage and delivery of application data and media |
Provider retention and data-use practices depend on the provider, service tier and account configuration. We do not promise universal zero retention or that every provider has the same training policy. See OpenRouter provider policies. Processing may occur outside your country.
Uploaded and generated media are served through URLs. Anyone with a media URL may be able to access it. Do not treat media links as private storage. Content you publish is also governed by the destination platform's visibility settings and policies.
4. Retention and deletion
Idle writing sessions may be closed, but their transcripts remain in History; they are not automatically deleted after 24 hours. Free-plan History access is limited to the last 30 days; that viewing limit does not itself delete older stored sessions. Saved articles, drafts and memories can remain available until you delete them or request removal. Closing a session, deleting a saved memory and deleting a library item are separate actions.
You can manage saved preferences, content history, sessions and library items using the available settings and deletion controls. For account deletion or removal of remaining stored copies, media or indexes, contact us. Account deletion does not automatically retract posts already published on X or LinkedIn, erase independent copies held by others, or remove records providers must retain for billing, security or legal reasons. Backups and diagnostic records may follow separate retention cycles.
5. Your choices and requests
Depending on applicable law, you may have rights to access, correct, export or delete data, or object to or restrict processing. Send requests to support@heddle.studio. We may verify your identity before acting. Disconnecting a social account removes its connection from Heddle; you can also revoke access on the platform itself. Review your subscription separately before deleting your account.
6. Security
We use access controls, authenticated application endpoints and encrypted transport in deployment. No system is completely secure. Share only material you are entitled to process and avoid including unnecessary sensitive information in prompts or uploads.
7. Children
The Service is not intended for individuals under 16. We do not knowingly collect personal information from children under 16.
8. Cookies and local storage
Authentication and core functionality use cookies and browser storage. Stored items can include preferences, active workspace identifiers and local draft state. Clearing browser storage can remove locally saved work. We do not use advertising cookies in the current application.
9. Changes and contact
Material changes will be posted here with an updated date. Heddle Studio — support@heddle.studio.