Privacy Policy

Who we are

Quill is a LinkedIn writing tool operated by Anagar Media ("we", "us"). We are the data controller for the information described below. Contact us at gaurav@anagarmedia.com.

What Quill accesses on LinkedIn

Signing in uses LinkedIn OAuth. Quill requests exactly three permissions:

• openid and profile — to identify you: your name, email address, and your LinkedIn member identifier.
• w_member_social — to publish posts to your profile, only when you schedule or publish them.

Quill cannot read your LinkedIn feed, messages, connections, or existing posts. LinkedIn does not offer an API for reading your own post history, which is why analysis relies on the data export you upload yourself. We do not scrape LinkedIn.

What we store

• Account — your name, email address and LinkedIn member ID.
• LinkedIn tokens — the access and refresh tokens that let Quill publish for you. Both are encrypted at rest.
• Posts you upload — the contents of the LinkedIn data export you provide, together with numeric representations (embeddings) used to find posts similar to a topic.
• Your voice profile — a description of your tone, rhythm and vocabulary, derived from those posts.
• Drafts and schedule — generated posts, your edits, scheduled times, and the identifier of anything published.
• Usage records — for each AI request, the number of tokens used and its cost, so we can measure and control spend.

We do not use analytics, advertising or tracking cookies. The only cookie Quill sets is your sign-in session: it is HTTP-only, signed, and expires after 30 days. It is strictly necessary for the service to work.

Who we share it with

We do not sell your data or share it for advertising. We use these processors:

• Anthropic — post text is sent to Claude to analyse your voice and to write drafts.
• OpenAI — post text is sent to generate embeddings used for similarity search.
• LinkedIn — receives only the posts you choose to publish.
• Railway and Vercel — host the application and database.
• Resend — sends notification emails, if enabled.

Content sent to Anthropic and OpenAI is processed to return a result under their respective API terms. We do not grant permission for your content to be used to train models.

Why we are allowed to process it

We process this data to perform the service you asked for (contract), and — for keeping the service secure and controlling cost — on the basis of our legitimate interests. You give consent through LinkedIn when you authorise Quill, and you can withdraw it at any time.

How long we keep it

We keep your data while your account is active. If you ask us to delete it, we remove your account, uploaded posts, voice profile, drafts and tokens within 30 days, except where we must keep records to meet a legal obligation.

You can delete a post from Quill at any time. For a post already published to LinkedIn, Quill can also delete the live post from your feed on request — choose "Also delete it from LinkedIn" when removing it. If LinkedIn refuses the deletion we tell you, rather than reporting it as removed. You can always delete the post on LinkedIn directly instead.

Your choices and rights

• Revoke access at any time — LinkedIn → Settings → Data Privacy → Permitted Services. Quill can no longer publish once you do.
• Delete individual posts — in Quill, on any draft or published post, optionally removing the live LinkedIn post too.
• Access, correct, export or delete your whole account — email us and we will action it. Full account deletion is handled on request rather than by a self-service button.
• Object or complain — you may object to our processing, and if you are in the UK or EU you may complain to your data protection authority.

Security

Traffic is encrypted in transit. LinkedIn tokens are encrypted at rest with a key held separately from the database. Sessions use signed, HTTP-only cookies. No system is perfectly secure, and we cannot guarantee absolute security.

Other

Quill is not intended for anyone under 18. Data is processed on servers that may be outside your country; where required, transfers rely on appropriate safeguards. If we change this policy materially we will update the date above and, where the change is significant, tell you in the app.