Data processing agreement
This English text is a translation for convenience. The Danish version prevails.
This agreement is part of the terms and applies when the customer uses wikiaio. It meets the requirements of Article 28(3) of the General Data Protection Regulation (GDPR). Enterprise customers may negotiate their own agreement; a signed agreement prevails in case of conflict.
1. Parties and roles
The customer is the controller. Sjøbeck Digital, CVR 34358702, is the processor.
2. The processing
- Purpose: providing wikiaio: storing, displaying, searching and answering questions from the customer's knowledge bases.
- Nature: storage, structuring, search, indexing (including computing text vectors), display, AI-based answering, export and deletion.
- Categories of data subjects: the customer's staff and other users the customer invites or lets in through Microsoft sign-in; people mentioned in the customer's pages.
- Types of data: name, e-mail, role, sign-in data, pages and files (which may contain personal data, including sensitive data if the customer adds it), questions and answers, usage statistics (daily totals of page views and searches, plus which users were active on a given day — shown only as counts, never per person; deleted after 90 days), an audit log on Business and Enterprise and during the trial (who viewed, changed, shared, granted access, signed in, exported or asked an AI question, and when — ids and metadata only, never page text, titles, file names, the wording of questions or IP addresses; visible to owners and admins only; deleted after 12 months, on Enterprise after up to 36 months as the customer chooses; nothing is recorded on other plans), technical logs without content.
- Duration: while the customer uses the service, plus the export period after cancellation.
3. Instructions
The processor processes the data only on documented instructions from the controller. The terms, this agreement and the customer's use of the service's features constitute the instructions. If the processor believes an instruction infringes data protection law, it informs the controller immediately.
4. Confidentiality
Only people who need access to provide the service get it, and they are bound by confidentiality. We have no standing access to customer content; access happens only for troubleshooting or support at the customer's request and is logged.
5. Security
The processor implements appropriate technical and organisational measures under Article 32. They are described in Annex B.
6. Sub-processors
The controller gives general authorisation to the sub-processors listed in Annex A. The processor announces changes at least 30 days in advance by e-mail and on the list of sub-processors. The controller may object; if the parties can't agree, the controller may terminate without cost. The processor imposes the same obligations on sub-processors and remains liable for them.
7. Transfers to third countries
Data is processed only in the EU/EEA. If the controller enables Microsoft sign-in or Microsoft Teams/Outlook, identity data (name, e-mail, tenant id) is processed by Microsoft as described in Annex A — never content.
8. Assistance
The processor assists the controller in responding to data subject requests (access, rectification, erasure, export), with impact assessments and prior consultations, to a reasonable extent. Most of this the controller can do in the service: edit and delete pages, remove users and export everything.
9. Personal data breaches
The processor notifies the controller without undue delay and at the latest 48 hours after becoming aware of a breach, with the information the controller needs to notify the authority within 72 hours.
10. Deletion and return
On termination, the controller can export everything for 30 days. Then the workspace's database is deleted and its encryption key destroyed at once, so files and other encrypted data can no longer be read. Page text may remain in the daily encrypted database backups for up to 14 days and in the weekly encrypted copy in a second EU region for up to 8 weeks, after which it is gone. The processor confirms deletion in writing on request.
While the agreement runs, the controller's owners and admins can delete data for good themselves, for example on an erasure request or when a personal identification number was entered by mistake: “Delete version permanently” removes an earlier version of a page, and “Delete permanently” or “Empty trash” removes deleted pages with all their history, AI index and attached files. Earlier versions can only be seen by people who can edit the knowledge base. Deleted pages are deleted automatically after a number of days the controller chooses (default 30). Questions to the AI assistant and their answers are kept for the period the controller chooses (default 12 months, or no time limit); questions from the current month are kept until it ends, because they count towards the AI quota. Answers that were based on a deleted page or version lose their text. Automatic deletion runs every night. This also applies to permanently deleted pages and versions: the daily database backups are deleted after 14 days and the weekly encrypted copy after 8 weeks, so data deleted in the workspace is gone from the backups no later than 8 weeks after. Until then, backups are used only for disaster recovery and are never restored into live service for any other purpose.
11. Audits and documentation
The processor makes available the information needed to demonstrate compliance and allows audits with reasonable notice. An independent ISAE 3000 report is planned but not issued.
12. Liability and term
Liability is governed by the terms. This agreement applies as long as the processor processes data for the controller.
Annex A — Sub-processors
| Company | Country | Purpose | Data | Location of processing |
|---|---|---|---|---|
| Scaleway SAS | France | Servers, databases, key management (Key Manager), AI models (Generative APIs), sending e-mail | All content, user accounts, questions and answers, logs | EU (Paris, France; weekly encrypted backup copy in Amsterdam, Netherlands) |
| Mollie B.V. | Netherlands | Payments and subscriptions | Billing contact, payment details | EU. Mollie uses its own sub-processors: according to Mollie's own list, the Mollie dashboard is hosted on Google Cloud Platform in the EU (Belgium, the Netherlands, Germany and Finland). |
| BunnyWay d.o.o. | Slovenia | DNS for wikiaio.eu (in use since 23 October 2026). CDN not used | DNS queries: the IP address of the server making the lookup (the resolver) and the name looked up. No customer content | EU |
| Microsoft Ireland Operations Ltd (US parent) | Ireland | Only if the customer enables Microsoft sign-in or Teams/Outlook: confirms the user's identity | Name, e-mail, Microsoft tenant id — never content | EU (Microsoft's EU Data Boundary); any transfer takes place under the EU-U.S. Data Privacy Framework and the EU standard contractual clauses |
Annex B — Technical and organisational measures
Customer separation
- Every customer has its own database. No tables are shared between customers.
- Every database has its own password. It is stored encrypted with keys in Scaleway Key Manager (envelope encryption) and cryptographically bound to the individual customer.
- Every customer has its own key in Scaleway Key Manager, protecting the customer's sign-in keys and files (images and attachments). If the key is destroyed, that data can't be read again.
- The customer a request belongs to is determined only from the address (name.wikiaio.eu), and sign-in tokens are cryptographically bound to the individual customer: a token from one customer doesn't work at another.
Access control
- Roles (owner, admin, editor, reader) and access per knowledge base. Search and AI answers filter on the user's access before the language model sees anything.
- Sign-in by one-time e-mail link, Microsoft (identity only), passkey or one-time recovery code. We store no passwords; recovery codes only as salted hashes.
- Every request is checked for permissions on the server; automated tests try access across customers and roles.
Encryption and network
- HTTPS (TLS) on all traffic, HSTS and a strict Content Security Policy.
- Customer-specific keys in Scaleway Key Manager. Key material never leaves Key Manager.
- The database disk is encrypted at rest (AES-256 in XTS mode) with a key managed by Scaleway.
AI
- Language models run at Scaleway in the EU. Only excerpts from pages the user may see are sent with the question.
- Page content is treated as data, not instructions, and answers without valid sources are rejected.
Logging
- Security and audit logs contain metadata (who, what, when), not page content or question text. Personal data in logs is masked automatically.
Operations and continuity
- Hosting at Scaleway in Paris. The database is backed up automatically every day as snapshots of the encrypted database disk, and they are kept for 14 days. Snapshots are encrypted at rest as part of the disk encryption and are stored at Scaleway in the same region as the database.
- In addition, a logical copy of all databases is made every week to a second EU region (Scaleway in Amsterdam, the Netherlands). The copy is encrypted before it leaves the server (AES-256-GCM with a fresh data key for every database in every run, protected by keys in Scaleway Key Manager) and stored with an object lock for 8 weeks: nobody, including us, can delete or change it early. It is then deleted automatically. Files (images and attachments) are not in the weekly copy.
- Restores are tested on production: on 30 October 2026 the latest database snapshot was restored to a temporary, private instance and every workspace was checked against the live system (all data present); the temporary instance was then deleted.
- The customer can always export all content.
Development
- Automated security checks on every change (static analysis, secret scanning, dependency checks, a check that no US vendor is in the data path) and a security review before release.
Corrected 28 October 2026: clarification of deletion, backups and encryption at rest. Corrected 29 October 2026: backups are encrypted snapshots, not logical exports; added a weekly encrypted copy in a second EU region; deleted data may remain in that copy for up to 8 weeks.