Security and data · DPA
Sign our data processing agreement in three steps
Using our add-ons for your company, school or clients? Then you need a data processing agreement under GDPR Article 28. Ours is ready: download it, sign it and email it to us. It costs nothing, on every plan.
- 1
Download the DPA
Pick English or Danish. Both say the same thing. The Word file is ready to fill in.
- 2
Fill in and sign
Add your company, registration number and the email address we should use if there is ever a security incident. Sign it.
- 3
Send it to us
Email the signed copy to [email protected]. We sign it and send it back to you.
Does your company use its own DPA template? Send it to us, and we will go through it. The agreement covers our Google Workspace add-ons. For geoa, the Shopify apps or the Nordic Data API, write to us.
Read the agreement first
The full English text is below. Læs den på dansk.
Version 1.0 · 14 November 2026
This Data Processing Agreement (the "DPA") is entered into between the customer who signs below (the "Controller") and AddonNordic ApS, CVR 46495985, Denmark (the "Processor"). It covers AddonNordic's Google Workspace add-ons listed in Annex 1 and forms part of the terms of service for those add-ons. If this DPA and the terms of service conflict on the processing of personal data, this DPA prevails.
1. Subject matter and roles
The Controller uses one or more of the add-ons in Annex 1. When it does, the Processor processes personal data on the Controller's behalf. Annex 1 describes the subject matter, nature and purpose of the processing, the types of personal data, the categories of data subjects and the duration (GDPR Article 28(3)).
The Controller is responsible for having a lawful basis for the processing and for the instructions it gives. The Processor processes the personal data only to provide the add-ons the Controller has chosen.
Account, billing and support data that the Processor needs to run its own business (for example invoices and bookkeeping) are processed by the Processor as an independent controller under its privacy policy, not under this DPA.
2. Instructions
The Processor processes personal data only on documented instructions from the Controller, including with regard to transfers to third countries, unless EU or Danish law requires otherwise. In that case the Processor informs the Controller of the legal requirement before processing, unless the law forbids it (Article 28(3)(a)).
This DPA, the terms of service and the Controller's settings and actions in the add-ons are the Controller's complete instructions at the time of signing. Further instructions must be in writing.
The Processor informs the Controller immediately if, in its opinion, an instruction infringes the GDPR or other EU or Danish data protection rules (Article 28(3), second subparagraph).
3. Google user data
Where the add-ons access data through Google Workspace APIs, the Processor complies with the Google API Services User Data Policy, including the Limited Use requirements, and with the Google Workspace API user data and developer policy. In particular the Processor:
(a) uses Google user data only to provide or improve the user-facing features the Controller sees in the add-on; (b) does not transfer the data to others except as necessary to provide those features, to comply with law, or as part of a merger or acquisition with notice to users; (c) does not use or transfer the data for advertising, and does not sell it; (d) does not let humans read the data, unless the user has given explicit consent for specific data, it is necessary for security purposes, to comply with law, or the data is aggregated and anonymised for internal operations; (e) does not use the data to develop, improve or train generalised or non-personalised AI or machine-learning models.
4. Confidentiality
The Processor ensures that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality (Article 28(3)(b)). At the date of this DPA, the only person with access is the Processor's owner and director.
5. Security of processing
The Processor takes the technical and organisational measures required by Article 32 GDPR. The measures in place at the date of this DPA are described in Annex 2. The Processor may change the measures, provided the overall level of security does not fall.
6. Sub-processors
The Controller gives the Processor general written authorisation to engage the sub-processors listed in Annex 3 (Article 28(2)).
The Processor informs the Controller at least 30 days in advance of any intended addition or replacement of a sub-processor, by email to the address the Controller has given and by updating the list at addonnordic.dk/trust. The Controller may object in writing within that period on reasonable data protection grounds. If the parties cannot agree, the Controller may terminate the affected add-on subscription, and the Processor refunds any prepaid fees for the remaining period.
The Processor imposes on each sub-processor, by contract, data protection obligations that offer at least the same level of protection as this DPA, in particular sufficient guarantees for appropriate technical and organisational measures. The Processor remains fully liable to the Controller for the performance of the sub-processor's obligations (Article 28(4)).
Systems that the Controller itself connects to an add-on, such as the Controller's own accounting system or Notion workspace, are not sub-processors of the Processor. The Processor reads from or writes to them only on the Controller's instruction, and the Controller's own agreement with that provider governs the data there.
7. Transfers outside the EU/EEA
The Processor's own servers for the add-ons run in the EU (Railway, region europe-west4, the Netherlands). Some sub-processors in Annex 3 are established in, or may access data from, the United States. Such transfers take place only on the basis stated for each sub-processor in Annex 3, which is either an adequacy decision (including the EU-US Data Privacy Framework for certified companies) or the European Commission's Standard Contractual Clauses (Article 46(2)(c)).
8. Assistance with data subject rights
Taking into account the nature of the processing, the Processor assists the Controller by appropriate technical and organisational measures in responding to requests from data subjects to exercise their rights under Chapter III GDPR (Article 28(3)(e)). If the Processor receives such a request directly, it forwards it to the Controller without undue delay and does not respond itself unless the Controller instructs it to.
9. Assistance with security, breaches and impact assessments
The Processor assists the Controller in ensuring compliance with Articles 32 to 36 GDPR, taking into account the nature of the processing and the information available to the Processor (Article 28(3)(f)).
The Processor notifies the Controller without undue delay, and no later than 48 hours after becoming aware of it, of any personal data breach affecting the Controller's data (Article 33(2)). The notification describes, as far as known at the time: the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed. Information not available at once is provided in phases. Notifications go to the Controller's contact email below.
The Processor provides the information the Controller reasonably needs to carry out a data protection impact assessment or prior consultation with a supervisory authority.
10. Deletion and return
When the Controller stops using an add-on or this DPA ends, the Processor deletes the personal data processed for that add-on, at the latest within 30 days, unless EU or Danish law requires storage (Article 28(3)(g)). The Controller can export or delete its own content in its Google account and connected systems at any time; the add-ons do not keep a separate copy of that content, except as described in Annex 1.
Data the Processor must keep as an independent controller, for example invoices under the Danish Bookkeeping Act, are not covered by this clause.
On request, the Processor confirms the deletion in writing.
11. Information and audits
The Processor makes available to the Controller all information necessary to demonstrate compliance with Article 28 GDPR and allows for and contributes to audits, including inspections, conducted by the Controller or an independent auditor mandated by the Controller (Article 28(3)(h)).
The Controller gives at least 30 days' written notice of an audit, and an audit takes place no more than once a year unless a personal data breach or a supervisory authority requires otherwise. The Controller bears its own costs and the auditor's costs. The Processor does not hold certifications such as ISO 27001 or SOC 2; information is provided as written answers and documentation.
12. Liability
Each party's liability under this DPA follows the limitation of liability in the terms of service, except where Article 82 GDPR or mandatory law provides otherwise.
13. Term, changes and governing law
This DPA applies for as long as the Processor processes personal data on the Controller's behalf. Changes must be agreed in writing, except updates to Annex 3 made under clause 6 and updates to Annex 2 that do not lower the level of security.
This DPA is governed by Danish law. Disputes go to the Danish courts, with the City Court of Copenhagen (Københavns Byret) as the court of first instance.
Signatures
Controller
Company, registration no., address, contact email for breach notices, name, title, date, signature
Processor
AddonNordic ApS, CVR 46495985, Solvangen 15, 9210 Aalborg SØ, Denmark, [email protected]
Annex 1: Details of the processing
Subject matter and purpose: providing the add-ons the Controller installs, as described at addonnordic.dk/trust.
Nature of the processing: reading content in the Controller's Google account or connected systems on the Controller's request, transforming it (for example into a report, PDF, calendar event or Notion page) and returning it; storing the limited records listed below; checking the user's plan.
Duration: for as long as the Controller uses the add-on, followed by deletion under clause 10. Content that passes through is held only for the time the request takes.
Special categories of personal data (Article 9) are not intended to be processed. If the Controller's own documents or emails contain such data, they pass through only where stated, and are not stored.
Types of personal data and categories of data subjects, per add-on:
| Add-on | Personal data | Data subjects |
|---|---|---|
| e-conomic to Google Sheets (Accounting to Sheets) | Email address of the user; name of the connected company; encrypted access token. Accounting data (which may contain names of customers, suppliers and employees) passes through in memory and is not stored. | The Controller's users; persons named in the Controller's accounting data |
| Peppol & VAT Checker | Email address; VAT, company and IBAN numbers; company names sent for sanctions screening | The Controller's users; sole traders whose VAT or company numbers are checked |
| Supplier Check for Gmail | Email address of the user; sender domain or display name of the open email | The Controller's users; senders of emails the user opens |
| File Upload for Google Forms (No Sign-in) | Email address of the form owner; encrypted Google token; respondent label (an answer or email address) and file names | The Controller's users; respondents to the Controller's forms |
| MailDock (Gmail to Notion) | Email address of the user; content of emails the user chooses to save (passes through); Notion token (encrypted) | The Controller's users; senders and recipients of saved emails |
| DocMargin (PDF with Comments for Google Docs) | Hashed email address; document content and comment authors' names (passes through in memory) | The Controller's users; people who wrote comments in the document |
| Accessibility Checker for Google Docs & Slides | Email address; document content (passes through); single images sent for alt-text suggestions; Resend: email address and the tips opt-in | The Controller's users; people shown or named in the documents |
| MailFile (Save Email as PDF to Google Drive) | Email addresses of paying users and team members; Resend: email address and the tips opt-in | The Controller's users |
| DocMerge (Mail Merge to Docs & PDF) | Email addresses of paying users and team members; Resend: email address and the tips opt-in | The Controller's users |
| Sheet Solver | None on our server; Stripe holds the paying customer's billing details | The Controller's paying users |
| Sheets to Calendar | Email addresses of paying users and team members (in Stripe); Resend: email address and the tips opt-in | The Controller's users |
| Scheduled PDF Reports for Google Sheets | Email address of paying users (in Stripe); Resend: email address and the tips opt-in | The Controller's users |
| Calendar to Sheets (Google Calendar Timesheet) | Email addresses of paying users and team members (in Stripe) | The Controller's users |
| Form to Calendar | Email addresses of paying users and team members (in Stripe) | The Controller's users |
| Icons for Google Slides & Docs – SlideIcons | Email addresses of users and team members; saved colours | The Controller's users |
Annex 2: Technical and organisational measures
- Hosting in the EU: all add-on servers and their storage volumes run at Railway in region europe-west4 (the Netherlands).
- Encryption in transit: the add-ons only call our servers over HTTPS; Google's allow-list in each add-on lists HTTPS addresses only. The servers behind license., peppol., maildock. and upload.addonnordic.dk sit behind Cloudflare.
- Authentication: every request from an add-on carries an identity token signed by Google, which the server verifies (signature, issuer, expiry and audience) before it does anything.
- Encryption of stored secrets: access tokens for e-conomic, Dinero, Tripletex, Moneybird, Notion and Google Drive are encrypted with AES-256-GCM with a random IV. The key is kept as a server setting, separate from the database.
- Least privilege towards Google: add-ons use current-file scopes (spreadsheets.currentonly, documents.currentonly, presentations.currentonly, forms.currentonly) and drive.file where Google offers them, and no restricted scopes.
- Data minimisation: document, email, spreadsheet and accounting content is processed in memory and not stored, except the specific records listed in Annex 1. Seven add-ons do all content processing inside the Controller's own Google account or browser.
- Automatic deletion: OAuth states after 1 hour; unfinished uploads after 24 hours; unused accounting and Notion connections after 365 days; MailDock saved-email links and usage after 400 days; Icons usage after one month; lookup caches after 2 or 24 hours in memory.
- Error reports: error messages sent from the add-ons are stripped of email addresses and long identifiers and cut to 300 characters before they are logged.
- Abuse protection: public endpoints are rate-limited; Stripe webhooks are verified with an HMAC-SHA256 signature.
- Payment card data never reaches the Processor; Stripe handles it.
- Access: only the Processor's director has access to the production systems.
Annex 3: Approved sub-processors
| Sub-processor | Purpose | Location | Transfer basis |
|---|---|---|---|
| Railway Corporation, USA | Runs our add-on servers and their storage (Every add-on with a server) | Servers and storage in Amsterdam, the Netherlands (europe-west4). Railway's own staff may access from the USA. | EU-US Data Privacy Framework (certified) and EU Standard Contractual Clauses in Railway's DPA |
| Stripe Payments Europe, Limited, Ireland | Payments, subscriptions and invoices (Paid plans of every add-on) | Ireland and other Stripe group companies, including in the USA | Stripe, LLC is certified under the EU-US Data Privacy Framework; Standard Contractual Clauses in Stripe's DPA |
| Cloudflare, Inc., USA | Encrypted connection and protection in front of some of our servers (MailFile, Peppol & VAT Checker, Supplier Check, MailDock, File Upload for Google Forms) | Global network, the request is handled close to the user | EU-US Data Privacy Framework (certified) and Standard Contractual Clauses in Cloudflare's DPA |
| OpenRouter, Inc., USA | Passes one image to the AI model for an alt-text suggestion, only when the user clicks (Accessibility Checker) | USA. Every request requires zero data retention: the image and the answer are not stored, and only providers that do not train on the data are used. | Standard Contractual Clauses in OpenRouter's DPA |
| Amazon Web Services, Inc. (Amazon Bedrock) or Google LLC (Vertex AI), USA | Runs Anthropic's Claude model that writes the alt-text suggestion (Accessibility Checker) | USA. Zero data retention and no training on the data. | EU-US Data Privacy Framework (certified) and Standard Contractual Clauses |
| Plus Five Five, Inc. (Resend), USA | Service emails, and tips and the monthly summary only for users who opt in (DocMerge, Scheduled PDF Reports, Sheets to Calendar, MailFile, Accessibility Checker) | USA (Resend's main processing takes place in the USA) | EU-US Data Privacy Framework (certified) and Standard Contractual Clauses in Resend's DPA |