Privacy.

1. Who is responsible

Coslynx, run by an individual based in Bengaluru, India, is responsible for the personal data described here (the “data controller” under the GDPR and the “data fiduciary” under India’s Digital Personal Data Protection Act, 2023). Dodo Payments, our merchant of record, is separately responsible for the payment data it collects, under the Dodo Payments privacy policy.

Questions and complaints about your data go to support@coslynx.com, answered by the person who runs Coslynx.

2. This website

• No cookies, no tracking. The site sets no cookies and runs no analytics, ads or third-party scripts. Its fonts are served from our own server.
• Server logs. Our host’s web server records each request: your IP address, the page, the time and your browser’s user agent. They are used to keep the site running and secure, and are kept by our host for a limited time under its retention settings.
• Abuse limits. The buy and claim forms count requests per IP address in memory for one minute, to stop key guessing and floods. Nothing of that is written to disk.

3. When you buy

• The checkout is Dodo Payments’ page. Dodo collects your name, email, billing address and payment details, and may set its own cookies, under its own privacy policy.
• From Dodo we receive what we need to deliver and support your order: your name and email, your country, the product, the amount, the payment and order numbers, and your licence key.
• Before the checkout opens, you tick a box to accept the terms and ask for delivery to start straight away. We send the time you ticked it to Dodo with your order, as our record of that agreement.
• We never see or store your card details.

4. Repository access

• For Content Factory you give us your GitHub username. We check with GitHub that the account exists, send it to Dodo with your checkout, and record it as the name of your licence key’s activation, at Dodo.
• We then ask GitHub to invite that account to the private repository, so GitHub shows us your account as a collaborator. GitHub’s own privacy statement covers your use of GitHub.
• If you claim access later at /claim, you give your licence key and GitHub username for the same purpose.

5. Support emails

If you write to us, we keep your email and what you send so we can answer it and keep a record of what we agreed.

6. Comments on our Instagram posts

• When you comment on a post on our Instagram account, Instagram sends us the comment, its id and your Instagram account id. We use them only to send you one direct message with a link to our guide or our site, as Instagram allows. No one else receives your comment from us.
• We keep the comment id and your account id for 30 days, so each comment is answered once.
• To have this erased, write to support@coslynx.com.

7. Content Factory on your computer

• Content Factory runs on your own computer. Your keys, channel settings, research, scripts, reels and browser sessions stay there. It sends us no usage data or telemetry.
• What it makes goes only to the services you connect (your AI provider, OpenRouter, ElevenLabs, Claude in Chrome and the sites you post to), under their own privacy policies.
• The licence check. Setup and the health check (npm run doctor) send your licence key to Dodo Payments’ licence service to check it is valid.
• The library store. Each library download sends your licence key, the name of the file and your IP address to our store, which runs on our web host. The store asks Dodo whether the key is valid and caches the answer for up to 24 hours under a one-way hash of the key, never the key itself.
• Updates. You download updates from GitHub with your own GitHub account.

8. Why we use it

• To sell and deliver what you bought, open your repository access and give support: needed to perform our contract with you.
• To keep the site, the store and the licence keys secure and stop abuse: our legitimate interest in protecting the service.
• To keep order and tax records: required by law.
• Under India’s DPDP Act we use your data only for the purpose you gave it for, and for the legal uses that Act allows.
• We don’t sell your data, use it for ads or send you marketing.

9. Who else handles it

• Dodo Payments (payment, tax, receipts, licence keys and refunds).
• GitHub (the repository and its invites).
• Our web host (the website, the library store and their logs) and our email provider (support email).
• Meta’s Instagram (the messages we send to people who comment on our posts).
• Authorities, when the law requires it.

We are based in India, so what you send us goes to India. These providers may handle your data outside your country, including in India, the United States and the European Union. Where EU or UK law needs a safeguard for that, we rely on the providers’ data protection terms, which use the European Commission’s standard contractual clauses (with the UK addendum) or the EU–US Data Privacy Framework.

10. How long we keep it

• Order, licence and GitHub username records: as long as your licence exists, then as long as tax and accounting law requires.
• Repository access: until your licence ends, or until you ask us to remove it.
• Support emails: as long as needed to deal with your request and any follow-up.
• Server logs: a limited time, as above. Store cache: up to 24 hours. Abuse counts: one minute.

11. Your rights

• You can ask us for a copy of the personal data we hold about you, to correct it, or to erase it. Records the law makes us keep are kept until it allows us to delete them. Erasing your GitHub username ends your repository access.
• In the EU, the EEA or the UK, you can also object to our use of your data, ask us to limit it, ask for it in a portable form, and complain to your data protection authority.
• In India, you can also withdraw consent you gave, nominate someone to use your rights if you die or can’t act, and complain to the Data Protection Board of India if we don’t resolve your complaint.
• Write to support@coslynx.com. We answer within one month.

12. Children

Content Factory is sold to adults. Don’t buy it if you are under 18.

13. Changes

If we change this policy, we post the new version here with a new date.