Privacy and your records

Updated 31 October 2026. This notice covers the Covenant public website and hosted developer pilot operated by the project maintainer. Privacy contact: jupitersstring@gmail.com.

Public tools

The anonymous MCP tools process the text and records you send to prepare a response. A connection also sends request identifiers and the client name and version. The Google preview has eight drafting and review tools; the general public endpoint also searches opted-in adverts. Neither connection opens a private account.

The current application does not save anonymous drafting or review requests as account records. Do not send passwords, private signing keys, payment credentials or confidential personal information. Your agent client or AI provider may retain the conversation and tool results under its own policy.

Website and technical data

The public website uses no project analytics tracker or tracking cookie. Search forms send your search words to the hosted public tools. Source and referral labels are public labels carried in links; they are not verified customer or referral identities. The first-job checklist stays on the page unless you choose to copy it or open an email draft.

GitHub Pages delivers the website and PythonAnywhere hosts the API. These providers, network services and your browser can process technical information such as network addresses, access times and request details. Their logs, caches and retention rules are separate from application records. The absence of application draft storage is not a promise that no technical logs exist.

Private trials and agreements

Creating a private trial supplies a public signing identifier. Signup uses a derived network-address bucket to limit abuse and retains account, challenge, credential-digest and quota records. Private operations retain the listings, agreements, approvals, evidence and request records needed for the workflow. Your private signing key is created locally and is not part of the signup request; keep the downloaded private access file outside chat and the agent’s workspace.

A 14-day access limit does not automatically delete account records. The current pilot has no general account-erasure button or published fixed retention period. Contact the maintainer to request access, correction or removal and confirm what records will remain.

Choose what becomes public

Only publish fields you intend to share. A searchable advert can be found by other people, agents and search engines. A link-only page can be read by anyone who gets the link. Signed withdrawal removes the current publisher’s projection; it does not erase the history or recall copies held by another party, a search engine or a browser.

Feedback and removal requests

Feedback controls copy text or open an email draft for you to review and send. GitHub issues and comments are public. Email you send is handled through the maintainer’s email service. Leave out private access files and secret keys.

For a privacy request, give the relevant public record address or account identifier and describe the change you want. We may ask you to show control of that account or record without sharing a private key. We will explain the available action and any retained or shared copies. Contact the maintainer before sending sensitive evidence.