Data Processing Terms

Last updated: 20 October 2026

These terms are part of the Terms of Service and form the data processing agreement required by Article 28 of the GDPR. They apply when your content in the hosted service contains personal data, such as names and addresses on invoices. You accept them by accepting the Terms of Service; nothing needs to be signed.

Roles

You (the customer) are the controller of personal data in your content. Runecode OÜ is the processor. Our own account and log data is covered by the Privacy Policy, where we are the controller.

What we process

• Data: whatever your templates, assets and render data contain. You decide what that is. If it includes special categories of personal data (such as health or genetic data), you make sure you have a legal basis for it.
• People: typically your customers, employees and business contacts.
• Purpose: storing your content and rendering documents from it, as you instruct through Studio and the API.
• Duration: as long as you use the service, then until deletion as described below.

Our commitments

We:

• process the data only on your documented instructions, which are your use of the service and these terms; if the law requires other processing, we tell you first unless that law forbids it; we tell you if an instruction seems unlawful;
• make sure everyone with access to it is bound to confidentiality;
• protect it with the measures listed below;
• use only the subprocessors listed below, under contracts with the same protections, and remain responsible for them;
• help you answer requests from people exercising their rights, and with security, breach notification, impact assessments and consultations, as far as our part allows;
• tell you without undue delay, and within 48 hours where we can, after we become aware of a breach affecting your data;
• when you stop using the service, return or delete the data, as you choose, as described below;
• give you the information needed to show these terms are met, and allow audits by you or an auditor you appoint, with reasonable notice, at your cost, and no more than once a year unless there has been a breach.

Security measures

• Encrypted connections (HTTPS) for all access to the service.
• Each workspace’s data kept apart from every other workspace’s, enforced on every request.
• Access by role within a workspace; API keys scoped to one workspace.
• Templates’ scripts run in an isolated sandbox for each render.
• Optional two-factor sign-in.
• Encrypted, off-server database backups, with off-site copies at a second provider, and versioned file storage.
• Operating system security updates applied automatically, and application security fixes deployed promptly; access to servers limited to named administrators with SSH keys.

Subprocessors

Subprocessor	What for	Where
netcup GmbH	The servers that run the service and its database	Austria
Hetzner Online GmbH	File storage and backups	Germany
Backblaze, Inc.	Off-site copies of the backups (the database encrypted) and of files	EU (Netherlands)
Cloudflare, Inc.	Passing connections to the service on to our servers; stores no content	Global network
Resend	Email delivery (invitations only, not your content)	EU (Ireland)
Anthropic	Only when you use an AI feature: the file you give it	United States
Functional Software (Sentry)	Error tracking: error messages and stack traces, without your content	EU (Germany)

Billing and payment data is handled by Polar Software, Inc., which sells paid plans as merchant of record. It is not part of your content, and Polar is not a subprocessor of it: Polar receives only the ID of the workspace a purchase is for. Billing data is covered by the Privacy Policy.

We tell you at least 30 days before adding or replacing a subprocessor. If you object on reasonable data protection grounds and we can’t resolve it, you can end your use of the service.

Transfers outside the EU rely on the EU–US Data Privacy Framework or the European Commission’s Standard Contractual Clauses.

Deletion

Finished renders, with their input data and documents, are deleted 30 days after they are created. Assets are deleted when you delete them. A deleted template disappears from Studio and the API, and its published versions are deleted 30 days later; its draft history stays until you shut the workspace down. When you shut down a workspace, its content is removed from the database at once and its files shortly after. Copies in backups and earlier file versions expire within 30 days. If a backup is ever restored, deleted workspaces and accounts are deleted again.

When you stop using the service, you choose whether we return or delete your data. To get it back, export your templates and download your documents in Studio or through the API, or ask us at privacy@runecode.ee and we send you an export. Shutting down the workspace is your choice to delete it.

Contact

Runecode OÜ, Iirise tn 3-3, Tartu linn, Tartu maakond, 51011, Estonia, privacy@runecode.ee