Data Processing Agreement
Last reviewed 25 October 2026
This is a past version, kept as it was accepted. The current version · What changed
When your organisation connects its directory, signatures and mail to Ascripto, we process personal data on your behalf. This agreement sets out how, as Article 28 of the General Data Protection Regulation (EU) 2016/679 (“GDPR”) requires. It forms part of our Terms of Service and needs no separate signature: accepting the Terms electronically concludes it in the electronic form Article 28(9) allows.
1. Parties and roles
The customer that accepted the Terms of Service is the controller. The processor is Andrii Koptiukh Software Developer, a sole trader registered in CEIDG (the Polish business register), ul. Dąbska 20 lok. 39, 31-572 Kraków, Poland, NIP 5213970831, VAT-EU PL5213970831. Terms defined in the GDPR have the same meaning here.
United Kingdom. Where the UK GDPR applies to you, references to the GDPR include it, this agreement serves as the Article 28 contract it requires, and your complaint route is the Information Commissioner’s Office. The UK treats the European Economic Area as adequate, so our processing in the EEA needs no further transfer tool.
A partner acting for you. If an Ascripto partner accepted the Terms of Service for you when it created your workspace, or manages your workspace with its owner’s approval, you remain the controller and this agreement is between you and us. The partner’s acceptance is provisional until someone at your organisation confirms it, as section 3 of the Terms describes; from then it binds you as your own. The partner’s people act in your workspace as administrators, and what they do there through the service, within the access you have given them, counts as your instructions under section 3. The partner acts for you under your own agreement with it, which you warrant meets Article 28 where the partner processes personal data for you; it is not our sub-processor. If a partner processes data from your workspace for its own purposes, it is the controller of that processing (Article 28(10)), not you and not we. Every action it takes is recorded under its name in your workspace’s history, and your workspace’s owner can remove it at any time. Our Partner Agreement sets out what it may do.
2. Subject matter, duration, nature and purpose
We process customer personal data only to provide Ascripto to you: reading your directory, auditing and deploying email signatures, adding signatures to mail routed through our relay, keeping the message log, hosting brand assets, measuring campaigns, and supporting you. Processing lasts as long as the Terms of Service, plus the deletion period in section 10. The categories of data and data subjects are in Annex 1.
3. Your instructions
We process customer personal data only on your documented instructions. The Terms of Service, this agreement including the retention periods and defaults in Annex 1, and your configuration and use of the service are those instructions. If we believe an instruction infringes data protection law, we tell you. If the law requires us to process data otherwise, we tell you first unless the law forbids it.
Three things we do with data from your workspace for purposes of our own, and therefore as controller, not on your instructions: keeping security and access logs to protect the service, counting the people billed to charge you, and detecting abuse of the relay and of hosted images. Our privacy policy describes each, its legal basis and how long it is kept.
4. Confidentiality
Everyone we authorise to process customer personal data is bound by confidentiality. Our staff do not access customer data except through a support grant that is limited in time, carries a reason, is recorded, and is visible to you.
5. Security
We implement the technical and organisational measures in Annex 2, and keep them appropriate to the risk as the service develops. We may change them as long as the overall level of protection does not fall.
6. Sub-processors
You give us general authorisation to engage the sub-processors in Annex 3. We tell you at least 30 days before adding or replacing one, by email to your workspace owner and by updating Annex 3; where a sub-processor in Annex 3 changes its own sub-processors and tells us, we pass the notice on within the same window. If you object on reasonable data-protection grounds, we will discuss it in good faith; if we cannot resolve it, you may end the agreement for the affected service and pay nothing for it after that. We bind every sub-processor by a written contract to data protection obligations no less protective than these, and remain fully responsible to you for their performance.
Google and Microsoft, whose platforms you connect, are your providers, not our sub-processors. Microsoft is our sub-processor only in the role Annex 3 states: hosting the service on Azure.
7. International transfers
Customer personal data is stored and processed in the European Economic Area, in the Microsoft Azure region Annex 3 names, within Microsoft’s EU Data Boundary. We do not transfer it outside the EEA. Microsoft’s staff outside the EEA may have incidental access when giving us technical support, which Microsoft’s data processing terms cover by the European Commission’s Standard Contractual Clauses, with the EU–US Data Privacy Framework where Microsoft is certified. If we ever need another transfer mechanism, or another lawful mechanism replaces one of these, we tell you as section 6 provides.
8. Helping you
Taking into account the nature of the processing, we help you respond to data subjects exercising their rights, mainly through the service itself. If a request reaches us directly, we pass it to you within 5 business days, tell the person which organisation controls their data, and do not answer it ourselves unless you ask. Our help pages offer wording you can use to tell your people and your recipients what Ascripto records about them. We also give you the information you reasonably need for data protection impact assessments and consultations with a supervisory authority.
9. Personal data breaches
We notify you without undue delay, and in any case within 24 hours, after becoming aware of a personal data breach affecting customer personal data, so that your own 72 hours run with time to spare. The first notice says what we know — its nature, the data and people likely affected, its likely consequences, and the measures taken or proposed — and we add to it as we learn more, in a form you can use for your own notification and records. We keep a register of security incidents, including those we concluded were not breaches and why, and show you the entries that concern your workspace on request. Notifying you is not an admission of fault.
10. Deletion and return
When the Terms of Service end you can request an export of your data for 30 days, in the formats section 12 of the Terms names. Within the 30 days after that window we delete customer personal data, unless the law requires us to keep it. Backups are nightly, kept for 30 days and then deleted, and are not restored except to recover the service.
11. Demonstrating compliance and audits
We make available the information needed to demonstrate compliance with this agreement, including this agreement, Annex 2 and the records it names, and answer reasonable security questionnaires. If that does not suffice, you, or an independent auditor bound by confidentiality, may audit our compliance once a year on 30 days’ notice, during business hours and without disrupting the service or other customers’ data, at your cost. After a personal data breach affecting your data, or when a supervisory authority asks you to, you may audit once more on 14 days’ notice on the same conditions. If we become aware of a vulnerability or a security incident in the service that puts your data at risk, we tell you even where it is not yet a breach. A supervisory authority may always audit as the law provides.
12. Liability and precedence
The liability provisions of the Terms of Service apply to this agreement to claims between you and us, including a claim by one of us to recover compensation or a fine it had to pay because of the other. They do not limit what either of us owes directly to a data subject under Article 82 of the GDPR, and they do not apply to processing we carry out outside your instructions. If this agreement conflicts with the Terms of Service on the processing of personal data, this agreement prevails.
Annex 1 — Data subjects and categories of data
| Data subjects | Personal data | Kept for |
|---|---|---|
| Your employees and other people in your directory | Names, email addresses, directory identifiers, and the other directory fields signatures use (such as job title, department, phone numbers, office); administrators’ changes to them; their current and approved signatures; audit findings about them; where the Outlook add-in is deployed, the Outlook apps they use it in, each app’s version, whether Outlook says a signature is switched on, and when the add-in first and last read or set their signature | While they are in your directory; 7 days in the recycle bin after they leave it, or as you set. Past audit runs: 13 months, the latest until a newer one replaces it |
| People in your directory on the free plan | Whether each holds one of its free seats, and since when | While they hold it and are in your directory |
| People in your directory on a paid plan | Whether and when each last counted towards the month’s bill: a message our relay signed for them, or their signature written, set by the Outlook add-in or found current | 70 days |
| Your administrators and users of Ascripto, including the people of a partner that manages your workspace | Names, email addresses, and the actions they take in your workspace; the email address of an administrator of yours who used a setup link | Audit of actions: 13 months |
| Senders and recipients of mail routed through our relay | Sender and recipient addresses, Message-ID, time, and delivery outcome. Message content passes through in transit and is not stored. The log exists so you can answer “what happened to this message?”; it is not offered for evaluating your people, and telling them it exists is your duty as their employer | 10 days searchable; an archive you control may keep it longer |
| Recipients who click a tracked link or load a banner | The event, its time, the campaign and the sender, the recipient as a keyed one-way hash (HMAC with a key unique to your workspace, so it is pseudonymised, not anonymous: we can relate it to an address in your directory or message log, nobody else can), and the kind of client (browser, mail proxy or scanner), derived from the request and not stored as such. No IP address is stored. Results per person are off until you switch them on; until then we keep only totals per campaign. Loading a banner or following a tracked link stores and reads information on the recipient’s device, and obtaining the consent ePrivacy rules require for that, and telling your people when results per person are on, is your responsibility (section 4 of the Terms) | 90 days; monthly totals for 25 months |
| Anyone shown in your brand assets | Images you upload, served publicly so recipients’ mail clients can load them. You warrant that anyone shown has agreed to it; anyone can ask us to take an image down as section 5 of the Terms describes | Until you delete them |
We do not ask for special categories of personal data. Do not put them in signatures or directory fields that Ascripto reads.
Annex 2 — Technical and organisational measures
- Location: the service runs in Microsoft Azure’s Germany West Central region (Frankfurt).
- Encryption: TLS for all traffic to and between our services; data encrypted at rest by the storage platform. Mail between Exchange Online and our relay uses TLS and is authenticated by certificate.
- Credentials: directory tokens, signing keys and service account keys are kept in Azure Key Vault and never in a database or in code. A workspace’s records hold only a reference to them.
- Separation: every workspace’s data is scoped by its identifier on every read and write. Applications reach the databases only through defined routines, never through direct table access.
- Access: staff access requires multi-factor authentication. Access to a customer’s data needs a time-limited, reasoned and recorded support grant visible to the customer; the record of grants is kept for 13 months. Production access is limited to the people who operate the service.
- Accounts: passwords stored only as one-way hashes; second factors supported for every account; sessions listed and revocable by their owner.
- Minimisation: the relay never stores message content or subjects; the Outlook add-in sends only the signature of a new message, which is checked and not stored; tracking stores no IP addresses and keys the recipient hash per workspace; access to Google and Microsoft directories is read-only.
- Records: administrative actions in a workspace and staff actions are recorded in audit logs that the actions themselves cannot alter.
- Logs: kept for 30 days. The Outlook add-in’s server logs no IP address, and no call that succeeds.
- Testing: dependencies are checked for known vulnerabilities on every build, and a build with an unpatched one fails; these measures are reviewed at least once a year and after every incident.
- Resilience: health of every part of the service is monitored; databases are backed up nightly and kept for 30 days; the relay’s behaviour when it cannot sign mail is set per workspace.
- Evidence: on request we show you the configuration behind each of these measures as it applies to your workspace, the support grants made to it, and the incident register entries that concern it.
Annex 3 — Sub-processors
| Sub-processor | What it does | Where | Its own sub-processors |
|---|---|---|---|
| Microsoft Ireland Operations Limited (Microsoft Azure) | Hosting: servers, databases, storage, key management | Germany (Frankfurt), within Microsoft’s EU Data Boundary; incidental support access as section 7 describes | Microsoft’s Online Services Subprocessor List, published on its Service Trust Portal; we pass its change notices on under section 6 |
We use no other sub-processor. Transactional email is sent through a mail server we operate ourselves. Our payment provider, Stripe, receives the number of people a workspace is billed for and never who they are, so it processes no customer personal data under this agreement; the billing data it does handle, including the workspace owner’s name and email address, is ours as controller, as the privacy policy describes.