Skip to main content

App developer agreement (DPA)

DRAFT — not legal advice; must be reviewed by Growmax legal before the first external developer signs.

Version: 2026-11-01. This is the version ARC asks you to accept when you become a developer and when you draft a public app (see Developer signup). If the agreement changes, the version changes, and ARC asks you to accept the new one.

This agreement sets the rules for how you, the app developer, handle data that ARC organizations share with your app. It follows standard data-processor terms (in the style of GDPR Article 28). It is written in plain language on purpose.

1. Who is who​

  • Growmax runs the ARC platform.
  • A tenant is an ARC organization that installs your app. The tenant controls its own data.
  • You are the developer: the person or company that owns the developer account and the app.
  • Tenant data is any data your app receives from or about a tenant through ARC. This includes data about the tenant's customers, vendors, staff and products, and anything derived from it.

For tenant data, you act as a processor (or sub-processor) on the tenant's behalf. You act only on the tenant's instructions. Installing your app and granting it scopes are those instructions.

2. Use data only for what the scopes allow​

  • Use tenant data only to provide the features of your app that the tenant installed.
  • Use only the scopes the tenant granted. Ask for the fewest scopes your app needs.
  • Do not combine one tenant's data with another tenant's data, unless the tenant asks for that feature.
  • Do not use tenant data for your own purposes, such as marketing or profiling.

3. No sale or resale of tenant data​

  • Do not sell, rent, license or trade tenant data.
  • Do not give tenant data to anyone else, except a sub-processor under section 7, or where the law requires it (see section 10).

4. No AI training on tenant data​

  • Do not use tenant data to train, fine-tune or evaluate any AI or machine-learning model.
  • This applies to your own models and to any third party's models.
  • If your app sends tenant data to an AI service to deliver a feature, that service must not keep the data or train on it. List that service as a sub-processor (section 7).

5. Never hand an ARC app token to an AI​

  • Never give an ARC app token, client secret or session token to an AI model, chatbot or agent.
  • This includes pasting it into a prompt, a tool setting, or a file an AI can read.
  • An app token acts on tenant data directly, with no approval step. AI assistants connect through ARC's MCP connector instead, where every change waits for a person to approve it.

6. Security​

Keep tenant data and your credentials safe. At a minimum:

  • Encrypt tenant data in transit (HTTPS/TLS) and at rest.
  • Store client secrets and tokens in a secret store, never in source code or logs.
  • Verify every ARC webhook and session token signature before you trust it.
  • Give your own staff access to tenant data only when their work needs it.
  • Keep your systems patched, and keep access logs.
  • Rotate a client secret at once if you think it has leaked.

7. Sub-processors​

  • A sub-processor is any third party that handles tenant data for your app, such as a hosting provider, database service, email service or AI service.
  • List every sub-processor in your app listing or privacy policy. Say what each one does and where it stores data.
  • Bind each sub-processor to terms that protect tenant data at least as well as this agreement.
  • Tell Growmax and your tenants before you add or replace a sub-processor.
  • You remain responsible for what your sub-processors do.

8. Breach notice within 72 hours​

  • If tenant data is lost, leaked or accessed without permission, tell Growmax within 72 hours of finding out.
  • Say what happened, which tenants and data are affected, and what you are doing about it.
  • Keep Growmax updated as you learn more. Help Growmax and the affected tenants respond.
  • Do not contact affected tenants' customers about the breach without first agreeing it with Growmax, unless the law requires you to.

9. Deletion on uninstall​

  • When a tenant uninstalls your app, ARC revokes its tokens and deletes the app's data held in ARC within 48 hours.
  • You must also delete the tenant data your app holds, including copies and backups, within 48 hours of the app.uninstalled webhook.
  • If the law requires you to keep some data longer, keep only that data, only for as long as the law requires, and do not use it for anything else.
  • If a tenant asks you to return or delete its data at any other time, do so promptly.

10. Requests from tenants, people and authorities​

  • If a person asks you to see, correct or delete their data, pass the request to the tenant. Help the tenant answer it.
  • If a court or authority asks you for tenant data, tell the tenant and Growmax first, unless the law forbids it. Give only what the law requires.

11. Audit and cooperation​

  • Keep records that show how you meet this agreement.
  • On request, give Growmax the information it needs to check that you follow this agreement. This may include security reports, certifications, or answers to a security questionnaire.
  • Growmax may audit your app, or ask an independent auditor to do so, with reasonable notice.
  • Help Growmax and tenants meet their own legal duties about tenant data.

12. Termination​

  • You may stop at any time by deleting your apps and closing your developer account.
  • Growmax may suspend or remove your app, or close your developer account, if you break this agreement. Growmax may act at once to protect tenants.
  • When this agreement ends, delete all tenant data you hold within 48 hours, as in section 9.
  • Sections 3, 4, 5, 8, 9, 10 and 11 still apply to any tenant data you hold after the agreement ends.

13. Changes​

Growmax may change this agreement. A change gets a new version. ARC asks you to accept the new version before you sign up again or submit an app for review.