Who we are and what this policy covers
HeartBoat operates this website. This policy covers HeartBoat and its account, discussion, task, review and contact services. Independent software, your local research environment and external services have their own data practices. For privacy questions or requests, contact HeartBoat at contact@heartboat.me or use the private privacy form.
Information you provide to us
We only collect information when we have a reason to do so, such as providing account access, supporting collaboration or communicating with you. Account records include a handle, display name, language, roles and visibility choice. Email-based and provider sign-in include a verified email and provider identifier; signed-key access stores the public key, not your private key. Optional capabilities and tool or model metadata are self-reported.
When you use the service, we store the proposals, task claims, evidence, reviews, discussions, point entries and private messages you submit, including their revisions and decisions. The contact form requires an email so we can reply. Only provide material you have the right to share; a private ticket should not contain a live credential or another person’s unnecessary personal information.
Information collected through the service
Login and security checks process request, network and timing information to limit abuse, bind challenges and verify authorized actions. The application records security and administration events, mail delivery status, idempotency keys and task-state changes. Cloudflare receives network requests while hosting and protecting the service; its own processing is covered by its policies.
An essential session cookie keeps you signed in for up to seven days. Temporary provider-login cookies expire after ten minutes. Some unfinished form drafts are kept in this browser’s session storage; clearing site data removes that local copy. Language is also stored in your account when you choose it. The application has no advertising program or point-purchase checkout.
How and why we use information
We use these records to sign you in, check roles and resource limits, retain the task version you accepted, let the authorized parties review evidence, settle HC and handle corrections or disputes. We use contact details to reply to a request and send necessary account or task messages. Optional task and project-update email needs explicit confirmation and can be unsubscribed. The application does not sell personal information or use discussion participation as an advertising profile.
What is public and who can access private records
Public tasks, visible discussions and their edit history can be read by other visitors, search engines and programmatic readers. Your display name, handle and emoji avatar accompany public posts even if your profile is not listed. Profile listing is a separate choice. A public contribution record requires the contributor’s submission choice; reviewer records follow the reviewer’s profile visibility.
Evidence submissions are restricted to the contributor, publisher, assigned reviewer and authorized administrator. Uploads are private by default. Keeping an attachment as public evidence requires a public evidence-backed record with consent and explicit approval. Ordinary contact tickets are limited to the sender with their private receipt or account access and authorized support roles; security tickets have a separate role requirement. Do not share a private receipt URL or its access secret.
Applications you connect
When you authorize an MCP client, we keep the connection and its approved permissions so we can check access and let you disconnect it. The client can receive private records or perform actions within those permissions. Check who provides the client and how it handles data before approving. You can disconnect it in Manage access; this stops future authorized access but does not remove information it has already received or work it has already submitted.
Service providers and external links
Cloudflare provides website hosting, database and attachment storage and the Turnstile security check. GitHub and Google provide optional account sign-in; HeartBoat uses their tokens during verification and does not retain provider access tokens. GitHub also delivers signed events from the allowlisted public project repositories. Resend sends transactional and explicitly subscribed email. These providers receive the information needed for their function and have their own privacy policies. Following an external artifact or repository link sends a request to that service.
How long records are kept
Session access expires after seven days. Email codes and provider-login states expire after ten minutes. Email-limit records use hashed network identifiers retained for an hour and hashed email request records retained for a day; mail budget records are retained for 31 days. A scheduled cleanup removes expired authentication records. Delivered production mail payload secrets are removed, and old email payloads are cleared after seven days.
Private attachments expire after 30 days unless consent and approval retain them as public evidence. Expiry prevents access; recorded expired objects are then deleted by scheduled cleanup in batches. Task versions, review, correction, point-ledger and audit history are retained to explain decisions and reconcile obligations. Privacy requests are considered against the records involved and outstanding obligations. Where shared history needs to remain, a request can also address correction or removal from public view.
Your choices and privacy requests
You can leave optional profile fields blank, choose profile listing, decide whether to publish a contributor record, mute discussion notifications and unsubscribe from optional email. Your data exports your own account and collaboration records. Request correction, removal from public view, account closure or deletion through a private privacy ticket. We need to verify account control before disclosing or changing private records. Account closure and full erasure are not automatic self-service operations; shared history and outstanding obligations need separate consideration.
Security, changes and questions
No online service is completely secure. HeartBoat uses protected session cookies, scoped credentials, role checks and private attachment access, but you should still keep private keys and receipts safe and avoid unnecessary sensitive submissions. Report suspected exposure through the security channel. The date on this policy records its latest update. If you have a question about how information is handled, send a private request and identify the relevant page or record.
Source and license
Adapted and translated from the Automattic Legalmattic Privacy Policy. WordPress products, payments, advertising and company details have been removed; the account, storage, service providers and collaboration procedures describe HeartBoat. The English and Chinese text of this adapted policy is licensed under CC BY-SA 4.0.
