What we record, and what we don’t

1. 1. Who is responsible

   marketinque.com and the console at app.marketinque.com are operated by Max Zeshut (“we”). For anything on this page, write to max@marketinque.com.

2. 2. Visitors to the public site

   No cookies, no third-party analytics. The site does not set cookies and loads no analytics, advertising or tracking scripts from anyone else.

   First-party measurement. When you view a page, use one of the free tools, or share something, your browser sends us the kind of event, the page or tool it happened on, and, when a link carried one, the channel it came from. That is the whole record: it contains no IP address, no device fingerprint and nothing that identifies you. We use it to see which pages and tools are worth keeping.

   Progress kept in your browser. The public launch plan and backlink index remember what you tick in your browser’s local storage. Nothing leaves your device unless you import it into a project yourself.

   Server logs. Like every web server, ours writes a line per request — the address the request came from, the URL, the browser’s user-agent string and the time. These logs are capped at thirty megabytes per service and roll over within days. They are read only to diagnose faults and abuse, and never joined to anything else.

3. 3. The waitlist

   If you join the waitlist we keep your email address and which page you joined from. We use it for one thing: to tell you when projects open. Every message carries an unsubscribe link, and you can ask us to delete the address at any time.

   An agent connected over MCP can add you only after you have said yes in that session; the record notes that it came that way.

4. 4. Projects

   A project is your marketing workspace in the console. It stores what you and the agent put there: your product profile and notification address, the brand dossier, confirmed facts, ideas and drafts, the submission kit, plan progress, recorded directory listings, and short summaries of agent sessions.

   • Tokens. The console sign-in and each project’s API tokens are yours to keep. For a token we store only a one-way hash; the secret is shown once and never again.
   • Your model key and connector credentials are encrypted at rest with a key that is held outside the database, and are used only to act on your project’s behalf — to call the model provider you chose, or the platform you connected.
   • The audit log records every agent decision and every human action on a project, stamped with who took it. It is append-only and hash-chained: an entry cannot be edited or removed on its own. The whole project can be.

5. 5. Who else sees data

   We run the service on infrastructure and services we do not own. These are the ones that touch data:

   • DigitalOcean hosts the server and its database, in New York.
   • Brevo delivers the email we send: waitlist notices, approval requests, session summaries.
   • Anthropic or Moonshot AI — whichever model provider a project chose — receives the project content a draft needs (the product profile, the brand dossier, the facts, the brief) when a draft is generated, under your key. The two first-run drafts that follow onboarding are made with our own key; everything after that is yours.
   • IndexNow (Bing and Yandex) receives the URLs of pages we publish on our own site. No personal data is involved.
   • The platforms you connect — a newsletter service, Bluesky, Dev.to, Discord and the rest — receive exactly what you approve for publishing, and nothing before you approve it.

   We do not sell data, and we do not share it with anyone else.

6. 6. Agents connected over MCP

   A project token lets an agent (Claude Code, or any MCP client) read a project and, with the write scope, record to it. Every call is counted against a daily allowance, and everything an agent records lands in the console stamped as the agent’s. Decisions — approvals, rejections — need the approve scope and are attributed the same way. Revoking the token ends the access.

7. 7. How long we keep it

   • Visitor events: as long as the site measures its own pages; they identify nobody.
   • Server logs: days, by rotation.
   • Waitlist addresses: until you unsubscribe or ask us to delete them.
   • Project data: until you delete the project. Deleting a project removes all of it at once — profile, drafts, log, tokens and keys — and there is no separate copy to restore it from.

8. 8. Your rights

   You can ask what we hold about you, have it corrected, have it deleted, or have a copy of your project’s data. Write to max@marketinque.com and a person answers. If you are in the EU or the UK you also have the right to complain to your data-protection authority.

9. 9. Children

   The service is for people running a business. It is not directed at anyone under sixteen, and we do not knowingly keep their data.

10. 10. Changes

    When the software changes in a way that changes what this page says, the page changes with it and the date at the top moves. Material changes to how we treat waitlist or project data are announced to the addresses on file.

Questions about this document: max@marketinque.com.