Draft, under review

Data Processing Agreement

Last edited 2026-09-04. This is a working draft written by the operator in plain language to describe what Fishpond actually does. It is reviewed, and where needed replaced, before the first paid subscription is taken. Until then the trial is offered on these terms as written.

Parties and roles

You, the account holder, are the controller of the personal data you place in your Fishpond account: your customers, leads, partners and anybody else your records describe. The operator (Aryan F, legal name Franz Dsa, hello@mynato.app) is the processor, and processes that data only on your documented instructions. Using the service through the dashboard, the API or the MCP server is the instruction.

What is processed

Whatever you store: typically names, email addresses, company names, tags, pipeline stages, notes, activity timelines, subscription and payment facts received from services you connect, and email deliveries, opens, bounces and complaints. Fishpond does not require any special-category data and you should not store any.

The processor’s obligations

Process only on your instructions, and tell you if an instruction appears to break the law.
Keep the data confidential. The operator is one person, and no other person has access to the systems.
Apply the measures on the security page: per-account isolation at the query, encryption of third-party credentials at rest, scoped keys, an append-only audit log, soft deletes, and an export route. That page is the current statement of the measures and is updated before, not after, they change.
Help you answer a data subject’s request. Export, correction, erasure and restore are routes you can call yourself; anything a route does not do, ask by email.
Tell you about a personal data breach affecting your data without undue delay after becoming aware of it, by email to the account owner, with what is known.
Delete or return the data when the account ends, at your choice, subject to the retention of audit rows described in the terms.
Make available the information needed to show these obligations are met, and allow an audit on reasonable notice, at your cost.

Sub-processors

Who	What for	Where
Cloudflare, Inc.	Hosting: Workers, D1, KV; TLS; DNS	Cloudflare’s global network; data at rest in the region Cloudflare places the database
The payment processor named at checkout	Taking payment for the subscription, as merchant of record	Its own terms and locations
Services you connect (email sending, payments, Google)	Only what you instruct Fishpond to send them	Per that service

Adding a sub-processor is announced by email 30 days ahead, and you may object; if the objection cannot be resolved you may end the account and the data is deleted.

International transfers

Cloudflare operates globally. Where data leaves the jurisdiction it was collected in, the transfer relies on Cloudflare’s standard contractual clauses and data processing addendum, which the operator has accepted. If your customers are in a jurisdiction that needs more than that, say so before you rely on the service.

Term

This agreement lasts as long as the account does, and the obligations about confidentiality, deletion and breach notification survive it.