TMA — Data Processing Addendum

Effective date: October 15, 2026

This Data Processing Addendum ("DPA") forms part of the TMA Terms of Service between TIME.MONEY.ASSETS.INC ("TMA," "we") and the customer ("Customer," "you"). It applies whenever Customer Content stored in the Service includes personal information about people other than you — your contacts, prospects, clients, recruits, team members, and booking invitees.

1. Roles

  • Customer is the controller (or "business") of personal information in Customer Content: you decide what is collected and why, and you are responsible for having a lawful basis and any required consents.
  • TMA is the processor (or "service provider"): we process that information only to provide the Service to you, on your documented instructions, and never for our own purposes. We do not sell it, rent it, or use it for advertising, profiling, or training general-purpose AI models.

Customer's instructions are: these Terms, this DPA, your configuration of the Service, and your use of its features. We will inform you if, in our view, an instruction would violate applicable privacy law.

2. Details of Processing

Subject matterHosting and processing of Customer Content in the TMA platform
DurationThe life of your account, plus the deletion window in Section 9
Nature and purposeStorage, organization, display, transmission, backup, and AI-assisted processing you invoke — to provide a business productivity platform
Data subjectsCustomer's contacts, prospects, clients, recruits, team members, and booking invitees
Categories of dataNames, contact details (email, phone, address), employer/role, meeting and booking details, notes and history the Customer records, communications content
Prohibited categoriesPer the Terms: government ID numbers, full payment card or financial account numbers, health information, data about minors. Do not store these.

3. Applicable Law

"Applicable privacy law" means the privacy and data protection laws that apply to the personal information in Customer Content, which may include Canada's PIPEDA, Alberta's PIPA, Quebec's Law 25, and U.S. state privacy laws (such as the CCPA/CPRA). This DPA is to be read so that both parties can meet their obligations under those laws.

4. TMA's Obligations

We will:

  1. process Customer Content only on your instructions (Section 1), unless the law requires otherwise — in which case we will tell you first unless the law forbids it;
  2. ensure everyone we authorize to access Customer Content is bound by confidentiality;
  3. protect it with the technical and organizational measures in Annex A, which we will not materially weaken;
  4. limit access to personnel and systems that need it to operate the Service;
  5. assist you, by appropriate technical and organizational measures, in responding to data-subject requests and in meeting your security, breach-notification, and impact-assessment obligations, taking into account the nature of the processing;
  6. make available information reasonably necessary to demonstrate compliance with this DPA (Section 8);
  7. delete or return Customer Content at the end of the engagement (Section 9).

5. Subprocessors

Customer-connected assistants are not subprocessors. When Customer connects an AI assistant or agent of its own choosing (through TMA's authorization flow or an API token), Customer instructs TMA to disclose Customer Content to that assistant. Its provider acts for Customer, not for TMA, and is outside this DPA; Customer is responsible for having a lawful basis and appropriate terms with that provider.

You authorize the subprocessors in Annex B. We will: (a) bind each subprocessor to data-protection obligations materially equivalent to this DPA; (b) remain responsible to you for their performance; and (c) give you at least 30 days' notice (email or in-app) before adding or replacing a subprocessor that will process Customer Content. If you reasonably object on data-protection grounds and we cannot offer an alternative, you may cancel the affected subscription and receive a pro-rata refund of prepaid fees for the unused period — this is the one exception to the no-refund rule in the Terms.

6. Data-Subject Requests

If a person contacts us directly to exercise privacy rights over Customer Content, we will not respond on the merits (except to direct them to you) and will pass the request to you without undue delay. The Service's built-in tools (viewing, correcting, exporting, and deleting records) are the primary means of assistance; we will provide reasonable further help where the tools are not enough.

7. Security Incidents

If we become aware of a breach of security leading to accidental or unlawful destruction, loss, alteration, or unauthorized disclosure of or access to Customer Content, we will: (a) notify you without undue delay, and in any event within 72 hours of confirming it; (b) describe what happened, the data and people affected (as then known), the likely consequences, and the measures taken or planned; (c) keep you updated as the investigation progresses; and (d) reasonably cooperate with your own notification obligations. Our notice is not an admission of fault.

8. Audits and Compliance Information

Once per 12-month period (or after a confirmed security incident affecting your data), you may audit our compliance with this DPA by written request. We satisfy audits by providing: our current security documentation, completed security questionnaires, and summaries of any third-party assessments or certifications we hold. On-site or technical audits are available only where required by applicable law for your compliance, on 30 days' notice, at your cost, during business hours, without access to other customers' data.

9. Deletion and Return

You can export Customer Content at any time using the Service. On termination or expiry of your subscription, you have 30 days to export. After that, we delete Customer Content from live systems, and it ages out of encrypted backups within 90 days, unless the law requires longer retention of specific records. On written request, we will confirm deletion.

10. Financial-Services Customers (GLBA and Similar Rules)

If you are subject to financial-sector privacy or safeguarding rules — such as the U.S. Gramm-Leach-Bliley Act Safeguards Rule or equivalent Canadian requirements — then, with respect to the "nonpublic personal information" of your clients that you store in the Service: we act as your service provider, we will maintain the safeguards in Annex A, we will use that information only to provide the Service, and we will cooperate reasonably with the oversight you are required to exercise over service providers. You remain responsible for determining that the Service is appropriate for your regulatory obligations before storing client data in it.

11. Cross-Border Processing

Customer Content is processed in the locations listed in Annex B (primarily the United States). The parties agree this DPA and the subprocessor contracts provide the contractual protection required for those transfers under applicable Canadian law. If a future law applicable to your data requires additional transfer mechanisms, the parties will cooperate in good faith to put them in place.

12. Liability and Precedence

This DPA is subject to the limitations of liability in the Terms of Service, which apply in aggregate across the Terms and this DPA. If this DPA conflicts with the Terms on the subject of processing personal information in Customer Content, this DPA controls. This DPA terminates automatically when we no longer hold any Customer Content.


Annex A — Security Measures

  • Encryption: TLS 1.2+ for all data in transit; encryption at rest for databases and backups.
  • Access control: role-based access; authentication through a dedicated identity provider; least-privilege access to production systems, limited to personnel who operate the Service; credentials and secrets stored in managed secret storage, never in code.
  • Application security: input validation and output escaping, rate limiting on APIs, security review of changes, dependency-supply-chain controls (minimum package release-age policy), audit logging.
  • Infrastructure: hosted on managed cloud infrastructure (Annex B) with provider-managed physical security, network isolation, and patching; production and development environments separated.
  • Backups and resilience: automated encrypted backups; documented restore capability.
  • Incident response: monitoring and alerting on errors and anomalous activity; a documented process to triage, contain, remediate, and notify per Section 7.
  • Personnel: confidentiality obligations for anyone with production access; access revoked promptly on role change or departure.
  • Data minimization: prohibited-data rules (Section 2) reduce the sensitivity of what the Service holds by design.

Annex B — Authorized Subprocessors

SubprocessorPurposeLocation
Clerk, Inc.Authentication and identity managementUnited States
Stripe, Inc.Payment processing (Customer billing data, not Customer Content)United States
Railway Corp.Application hosting, database, backupsUnited States
Resend, Inc.Transactional email deliveryUnited States

This list is kept current at timemoneyassets.com/dpa.


Executed versions. For customers who require a signed copy, this DPA may be executed by both parties; otherwise it is agreed by acceptance of the Terms of Service.

TIME.MONEY.ASSETS.INC — 1122 3 St SE, Ste 1906 #414, Calgary, AB T2G 0E7 — privacy@timemoneyassets.com