Legal
Privacy Policy
What Moneyline collects, what it does not, and what changes when you run the software yourself.
Not yet in force
Who we are
[Legal entity name], [registered address] operates the Moneyline managed service and this website. For privacy questions, contact us at the address at the end of this document.
What we collect
Account information
Name, email address, organization name, and authentication identifiers. If you sign in with Google or GitHub, we receive the profile fields those providers release, not your password.
Documents you submit
Files you upload to the managed service, and the structured output produced from them. These frequently contain personal and financial information about your own customers. We process them to provide the service and for no other purpose.
Usage and billing data
API request metadata (endpoint, timestamp, response status, document counts) used for rate limiting, billing, debugging, and abuse prevention. Payment details are handled by our payment processor; we store a customer reference and the last four digits of a card, never a full card number.
Website analytics
Aggregate page-level analytics for this marketing site. [Confirm the analytics provider, whether it sets cookies, and whether IPs are truncated.]
What we do not do
- We do not train models on your documents. Parser improvements come from fixtures we own or have explicit rights to redistribute.
- We do not sell personal information, and we do not share it with advertisers or data brokers.
- We do not read your documents except where you ask us to investigate a specific support issue, or where we are legally compelled to.
Why we are allowed to process it
For customers, processing is necessary to perform our contract with you. For security logging and abuse prevention, we rely on legitimate interests. Where you submit documents containing other people's personal data, you are the controller and we act as your processor under the data processing agreement.
How long we keep it
| Data | Retention |
|---|---|
| Submitted documents and parsed output | [Configurable per organization; state the default and the maximum] |
| Account records | [Retention after account closure] |
| Request and audit logs | [Retention window] |
| Billing records | [As required by tax law in the operating jurisdiction] |
Deleting a document through the API removes the stored file and its parsed output. Backups age out on their own schedule; deletion is reflected in backups within [window].
Where it is processed
Documents are processed in the region selected for your organization. [List available regions.] Where data moves outside its region of origin, that transfer relies on [transfer mechanism, for example Standard Contractual Clauses].
Who else touches it
The managed service runs on a small set of infrastructure providers, each bound by a data processing agreement. [Maintain the current subprocessor list here or link to it, and state the notice period for changes.]
Your rights
Depending on where you live, you may have the right to access, correct, export, or delete your personal data, to object to or restrict processing, and to complain to a supervisory authority. Account data can be exported and deleted through the dashboard; for anything else, write to us and we will respond within [statutory window].
Security
TLS in transit, encryption at rest, scoped and revocable API keys, and an audit trail on document access. The full set of controls is described on the security page, and the code implementing them is public.
Changes
Material changes are announced to account holders by email before they take effect. The revision date at the top of this page always reflects the current version.
Contact
Privacy questions and rights requests: privacy@moneyline.co. Security reports: security@moneyline.co. [Add the postal address, and an EU or UK representative if one is required.]
Other documents
Terms of ServiceSecurity