Dieplink privacy statement
Dieplink processes two groups of data: data about your account and data an organisation manages in the service. Octofin is the controller for the first group. The organisation or its client is the controller for the second (section 3).
Documents, data from Exact Online and the service's other data are stored in a data centre in Ireland. Sign-in data is also held by a supplier in the United States. Access from the United States is also possible for data stored in Ireland (sections 6 and 7).
Deletion in Dieplink does not erase files the organisation or a staff member keeps outside the service, such as the local copy (sections 6.2 and 9.9). You delete a note in the app; document deletion is requested through contact@octofin.be (section 10.4). After deletion, copies remain temporarily in the trash, in backups and at suppliers (sections 9.3 and 9.6).
Your rights, including the right to object, are in section 11. Send questions about your account to contact@octofin.be. Address questions about an organisation's documents to that organisation.
1. Definitions
This privacy statement refers to Regulation (EU) 2016/679 (General Data Protection Regulation, "GDPR"). The following terms have a fixed meaning in this statement:
- Octofin: Catalin Smuter, trading as Octofin, the provider of Dieplink whose details appear in section 2.1.
- Dieplink: the Windows application and associated cloud service through which organisations working with Exact Online store documents and link them to data from Exact Online.
- the Organisation: the business, firm or other organisation using Dieplink.
- staff member: a person with a Dieplink account belonging to the Organisation, with the role of administrator or member.
- administrator: a staff member with the administrator role, who invites staff, grants access rights and establishes the Exact connection.
- administration: a set of accounts in Exact Online that the Organisation has enrolled in Dieplink.
- Organisation Data: documents, notes and data from Exact Online (Exact data) that Octofin processes on the Organisation's instructions, together with their links, follow-ups and activity log.
- Account Data: personal data for which Octofin itself is controller: accounts and access, the Exact connection, feedback reports, the erasure register and invoicing (section 4.2).
- the cloud service: Dieplink's central environment, consisting of the database, file storage and functions that read Exact data.
- the local copy: the optional copy of all the Organisation's documents and notes in a folder the Organisation chooses.
2. Controller, contact and scope
2.1 Controller and contact
Dieplink is provided by Catalin Smuter, trading as Octofin, enterprise number 0753.817.187, Wilgenstraat 21, 9450 Haaltert, Belgium. Octofin is the controller for the processing in section 4.2. For data processed solely on instructions, the Organisation or its client is the controller (section 3).
Send questions about the processing of personal data to contact@octofin.be or by post to the address above. Octofin has not appointed a data protection officer (DPO). Your questions go directly to the person responsible for protecting personal data at Octofin.
2.2 Service
Dieplink is a Windows application with an associated cloud service. It is intended for any business, firm or other organisation working with Exact Online. Staff store documents in it and link them to bookings, relations and accounts from Exact Online.
Dieplink is a separate application with its own window. It reads Exact Online data exclusively through Exact's official interface (API) and does not change accounting data in Exact Online (section 5.4).
2.3 Scope and availability
This statement is intended for:
- the Organisation's staff;
- the Organisation's invoicing contact;
- people whose data appears in the documents and accounts the Organisation manages with Dieplink, such as its clients, their staff, suppliers and contacts.
This statement is available in the app under Settings → Privacy, in Dutch and English. You can also request a copy before creating an account through contact@octofin.be. The Dutch text is the original.
2.4 The Organisation's duty to inform
As controller, the Organisation informs the people whose data it processes. Where it processes the data as a processor for its client, that duty lies with the client. This statement does not replace that information.
3. Octofin's role
Octofin's role depends on the purpose of the processing. For the processing in section 4.1, Octofin is a processor: it processes data solely on the Organisation's instructions. For section 4.2, Octofin is the controller: it determines the purposes and means itself.
The same data may be processed in both roles for different purposes. For example, Octofin processes a staff member's name as controller to give them access. It processes the same name as processor in the Organisation's activity log.
3.1 Octofin as processor
The Organisation decides which documents it stores in Dieplink, which administrations it works with and how long it keeps its documents. Octofin processes Organisation Data solely to provide the service, following the Organisation's instructions set out in the data processing agreement (Article 28 GDPR).
Where the Organisation itself is a processor for its client, Octofin is a sub-processor: a processor working for another processor. The Organisation or its client determines the legal basis for processing Organisation Data. Octofin does not use Organisation Data for its own purposes.
The obligations the GDPR places on processors continue to apply to Octofin, including data security and confidentiality.
3.2 Octofin as controller
Octofin determines why and how Account Data is processed. Section 4.2 identifies the purpose, data and legal basis for each processing activity.
4. Purposes and legal bases
4.1 Processing on the Organisation's instructions
| Purpose | Data |
|---|---|
| Store, find, display, open, export and delete documents and notes | Documents with their content, file name, type and size; notes; follow-ups |
| Link documents to administrations, journals, bookings, general ledger accounts, customers and suppliers from Exact Online | Exact data (section 5.2); links between documents and that data |
| Record actions within the Organisation (activity log) | Staff member's name and e-mail address, action, technical identifiers (IDs) of the documents and data involved, counts, time |
| Maintain the local copy in the Organisation's folder (optional) | The Organisation's documents and notes |
| Technical backup and archive copies at the supplier for operation and recovery of the cloud service | Cloud-service data; section 9.6 describes the limits of this retention |
4.2 Octofin's own processing
| Purpose | Data | Legal basis |
|---|---|---|
| Accounts and access: sign-in with two-step verification, membership and administration access management, separation of different organisations' data | Name, e-mail address, Clerk user ID, role, membership, access rights, sign-in methods and session data (IP address, device type) | Legitimate interest (Article 6(1)(f) GDPR): give each staff member personal, secure access to the service the Organisation uses and prevent unauthorised access |
| Manage the Exact connection and comply with Exact's limits | Staff member who established the connection; Exact user ID and name of the person who authorised it; Exact call counts | Legitimate interest (Article 6(1)(f) GDPR): a reliable connection and compliance with Exact's terms of use |
| Handle feedback and problem reports and improve the app | Report text, attached screenshots, reporter's name and organisation, app version, screen and time (section 5.3) | Legitimate interest (Article 6(1)(f) GDPR): fix errors and improve the app |
| Erasure register: demonstrate an organisation's erasure and prevent its restoration (section 9.7) | Clerk user IDs of the administrators who requested and confirmed erasure; organisation identifiers as hashes (one-way fingerprints); times and counts | Legitimate interest (Article 6(1)(f) GDPR): demonstrate an erasure and repeat it after restoring a backup |
| Octofin's invoicing and accounting (not during the free pilot) | When invoicing: the Organisation's company and invoice details; its contact's name and e-mail address | Legal obligation (Article 6(1)(c) GDPR) for keeping invoices and accounting records; section 9.10 lists the statutory provisions. Legitimate interest (Article 6(1)(f) GDPR) for contact with the invoicing contact: deliver invoices and handle invoicing questions |
The Organisation decides who is a staff member and who may access each administration. Its administrator makes those decisions on its behalf. Octofin implements them and enforces them on every request.
Octofin determines how sign-in, access control and separation between organisations work. For those purposes it processes the first row's data as controller. The role follows the processing purpose, not the name of the data (section 3).
The supplier copies in section 9.6 may also contain Account Data.
4.3 Balancing of interests
For each activity based on a legitimate interest, Octofin has assessed three points: the specific purpose, the necessity of the processing and its effects on the people concerned. Octofin considers what those people can reasonably expect, and measures that limit the effects: restricted access and the retention periods in section 9.
That assessment is recorded in writing for each activity. An explanation is available on request through contact@octofin.be. Section 11.2 explains the right to object.
4.4 Consent
None of the processing in section 4.2 is based on consent within the meaning of the GDPR. That does not limit your rights, which section 11 describes.
The authorisation an administrator grants Dieplink in Exact Online is a technical authorisation for the connection. It is not consent to process all data in the accounts. Section 10.2 explains how to revoke it.
Section 8 describes storage on the device and how it is cleared.
4.5 Limits on use
We use data Dieplink receives through the app or Exact solely for the service to the Organisation and the purposes in this section.
We do not sell personal data. We do not use documents or Exact data for advertising, marketing or training AI models.
We disclose documents and Exact data only when necessary for the service, security or a legal obligation. Section 6.3 explains when Octofin itself accesses an organisation's data.
4.6 Automated decision-making
Dieplink does not make decisions about people based solely on automated processing and does not carry out profiling. Automatic synchronisation with Exact is not a decision about a person.
5. Categories of personal data and sources
5.1 Sources
We obtain data in five ways:
1. Staff input: documents they add to the app, including e-mails from Outlook, and their notes, links and follow-ups.
2. The official Exact connection: after an administrator authorises Dieplink in Exact Online, we read the data in section 5.2 from the administrations. Exact uses webhooks (automatic notifications) to tell us which list changed; we then read the changes.
3. Sign-in through Clerk: the administrator invites a staff member using their e-mail address. We therefore obtain that address from the administrator. The staff member enters their own name and sets up two-step verification.
4. Use of the service: the activity log, session data and Exact call counts arise automatically when staff use the app.
5. Invoicing: Octofin does not invoice the use of Dieplink during the current free pilot. No separate invoicing data is collected for it.
Exact data is not public. It comes from the Organisation's or its clients' accounts.
5.2 Categories of data
All data in this section is held in the cloud service unless explicitly stated otherwise.
Data about the Organisation and its staff (source: the administrator, staff member and Clerk):
- the Organisation's name;
- each staff member's name, e-mail address, role (administrator or member) and Clerk user ID;
- access rights per administration;
- at Clerk: sign-in methods and session data (IP address and device type).
Exact data (source: Exact):
- administrations: division number, name and currency;
- the Exact connection: the staff member who established it, the Exact user ID and name of the person who authorised it, the last check and any problems found;
- reference data: journals, general ledger accounts, customers and suppliers (code, name, status, city, VAT number);
- booking lines: entry, journal, number, financial year, period, date, description, relation, account, amounts and due date, and the derived amount per booking and relation;
- customers' and suppliers' open items: invoice and entry number, relation, amount, currency, dates, description and customer or supplier reference (Exact's "Your ref." field);
- attachments Exact holds for a booking, such as a PDF or UBL invoice: name and size;
- access keys (tokens) for Exact: stored encrypted in the cloud service and never stored on the device.
We do not store the content of an Exact attachment in the cloud service. When a staff member opens an attachment or drags it elsewhere, the cloud service passes its content to them. A temporary copy then remains on the device (sections 8.4 and 8.5).
Data supplied by staff:
- uploaded documents: content, file name, type and size, with notes, links and follow-ups. Those documents contain data about customers, suppliers and other people;
- feedback reports (source: the staff member sending them): type (problem or idea), typed text, fixed screen name, app version, time, staff member and organisation, and at most 3 images.
Data arising from use of the service:
- activity log: staff member, action, technical identifiers (IDs) of the documents and data involved, counts and time. The log contains no document content, file names, links or access codes;
- Exact call counts per organisation, administration, reason, day and hour, and per Exact user per day (source: use of the service);
- Exact notifications about changed lists (source: Exact). For counts and notifications, we keep only counts, times and technical notification identifiers.
Invoicing data, once invoicing is introduced (not collected during the free pilot; section 5.1, point 5):
- the Organisation's company and invoice details;
- its contact's name and e-mail address.
5.3 Feedback reports
Sending a feedback report is voluntary.
A feedback report is held in the cloud service, at Convex (section 6.4). Dieplink's developer reads it to handle it. We do not disclose it to other recipients, except where a legal obligation requires this (section 6.6).
A feedback report is not intended for the Organisation's client data or other confidential data. The app states this in the reporting window. That statement is a warning, not a legal basis.
If a report contains such data, Octofin uses it solely to handle the report, not to improve the app. Octofin treats it as Organisation Data: under the Organisation's instructions and the data processing agreement. At the reporter's or Organisation's request, we erase the report before its retention period ends (section 9.2).
The following technical limits apply:
- a screenshot shows only the app's window, never the rest of the screen;
- a screenshot is sent only after the staff member has viewed it;
- images are re-encoded without file names or metadata;
- a staff member may send at most 10 reports per hour.
5.4 Read rights in Exact Online
Dieplink's Exact app requests seven read rights and no right to change data: Organization administration, Financial generalledgers, Crm accounts, Financial accounting, Financial receivables, Financial payables and Organization documents.
Dieplink writes no bookings, documents or other data to Exact. The exception is subscribing to and unsubscribing from Exact's automatic notifications (webhook subscriptions). Through these, Exact tells us which list changed.
Dieplink adds nothing to Exact Online's web pages and does not read them.
5.5 Special categories and criminal-offence data
Documents and notes contain whatever types of personal data the Organisation puts in them. These may include special categories, such as health data (Article 9 GDPR), and data about criminal convictions and offences (Article 10 GDPR). Different additional legal conditions apply to these two categories.
The Organisation or its client decides whether to process such data in Dieplink and ensures those conditions are met. Octofin processes it solely within the Organisation's instructions, while remaining bound by its own processor obligations (section 3.1).
We do not analyse document content for our own purposes. Octofin accesses content only in the cases in section 6.3.
5.6 Required and voluntary data
Using Dieplink requires an account with a name, e-mail address and two-step verification. Without that data, a person cannot gain access. Sending feedback and attaching images is voluntary.
During the free pilot, no invoicing data is required to use Dieplink.
5.7 Recording use
Dieplink contains no analytics software. We do not track app use for marketing or behavioural analysis. The app sends no usage statistics to Octofin or Clerk.
Dieplink does record usage data for access, security, the activity log and management of the Exact connection. These records serve only the purposes in section 4:
- the Organisation's activity log (section 5.2);
- sign-in and session data at Clerk (section 6.4);
- Exact call counts, to manage the connection and comply with Exact's limits (section 5.2);
- a limited technical log file on the device, without file names or paths, which does not leave the device (section 8.5).
6. Recipients and access
6.1 Access within the Organisation
An administrator grants each staff member access to designated administrations. A staff member therefore does not automatically have access to every administration.
Only an administrator establishes the Exact connection, views Exact usage and activates the local copy. Through Dieplink, an organisation never has access to another organisation's data.
6.2 Local copy
The local copy is optional. An administrator designates one device that keeps a copy of all the Organisation's documents and notes. The Organisation chooses the folder: on that device, a network drive or a synchronised folder of a service such as OneDrive, SharePoint or Google Drive.
Anyone with access to that folder can read every document of the Organisation, including documents from administrations they cannot access in Dieplink.
The Organisation secures the folder itself (access rights, encryption, backups). It also chooses its location, preferably within the European Economic Area (EEA). The local copy is not a tested backup.
6.3 Access by Octofin
As provider, Octofin has no account within an organisation. It does have technical access to each organisation's data through suppliers' management consoles. We use that access only in four cases:
- technical operation of the service: maintenance and recovery from failures;
- resolving a problem at the Organisation's request;
- security;
- where required by law.
In each case, we access no more data than necessary. Dieplink's developer also reads feedback reports to handle them (section 5.3).
6.4 Suppliers
This section identifies which suppliers receive personal data, for what service and in which role, together with processing locations and transfers outside the EEA. Dieplink uses two suppliers: Convex and Clerk.
Convex
| Attribute | Convex |
|---|---|
| Entity | Convex, Inc. (United States) |
| Role | Sub-processor for Organisation Data; processor for Account Data |
| Service | The cloud service: database, file storage and functions reading Exact data |
| Data | All data in the cloud service (section 5.2) |
| Processing location | Ireland (AWS region eu-west-1), including all backups. Amazon Web Services provides this infrastructure as Convex's sub-processor. Support and operations from the United States are possible |
| Transfer outside the EEA | United States: the data processing agreement permits transfers to Convex and its sub-processors (section 7.1) |
| Transfer safeguard | Standard contractual clauses, module 2. The limitation in section 7.1 applies to Organisation Data |
| Retention after erasure | Section 9.6 |
Clerk
| Attribute | Clerk |
|---|---|
| Entity | Clerk, Inc. (United States) |
| Role | Processor for Account Data; independent controller for some data (see below) |
| Service | Sign-in, two-step verification, sessions, organisations and roles |
| Data | Name, e-mail address, Clerk user ID, membership and role, sign-in methods and session data: IP address and device type. No documents or Exact data |
| Processing location | United States, at Clerk and its sub-processors |
| Transfer outside the EEA | United States |
| Transfer safeguard | Adequacy decision; standard contractual clauses as a fallback (section 7.2) |
| Retention after erasure | Section 9.6 |
Use by suppliers
Convex and Clerk use the data to provide their services to Octofin under their data processing agreements. Two qualifications apply:
- Clerk also processes account information as an independent controller. Its data processing agreement gives examples: names, usernames, login credentials, telephone numbers and e-mail addresses. Clerk uses that information to manage its relationship with Octofin, for its own business operations and for legal obligations. To the extent permitted by law, it also uses it to provide, improve and maintain its service. The agreement does not specify field by field which staff data falls within this category. Clerk's privacy policy applies to that processing.
- Convex's data processing agreement allows it to compile aggregated or de-identified information that cannot identify a person. Information that can still identify someone does not fall within that provision.
Outside the provision on aggregated or de-identified information, Convex does not use documents or Exact data for its own purposes. Clerk receives no documents or Exact data.
Convex and Clerk use sub-processors themselves. Their lists are on Convex's page and Clerk's page.
6.5 Invoicing recipients
During the free pilot, Octofin does not disclose invoicing data about use of Dieplink to an accounting software provider or external accountant. When invoicing is introduced, we will inform the contact in advance about the data, recipients, processing locations and retention periods.
6.6 Exact and public authorities
Exact is not Octofin's supplier. Exact Online is the Organisation's accounting package and the source of Exact data.
We disclose data to a public authority only when a legal obligation requires it.
7. Transfers outside the European Economic Area
7.1 Convex
Convex, Inc. is established in the United States. The database, file storage and all backups of Dieplink's environment are held in AWS EU West, Ireland. This includes daily backups.
Storage in Ireland does not rule out access from the United States. Convex staff may access the data from the United States for support and operations. The data processing agreement also permits transfers to Convex and its sub-processors. Convex's sub-processor list identifies their services and processing locations.
The current data processing agreement with Convex contains the European Commission's standard contractual clauses (Implementing Decision (EU) 2021/914), module 2. That module governs transfers from a controller to a processor. Octofin is the controller for Account Data, but a processor or sub-processor for Organisation Data (section 3). The contractual description of the roles does not cover that latter distinction. EU storage alone does not remove this difference. We do not rely on an adequacy decision for Convex.
7.2 Clerk
Clerk processes account and sign-in data in the United States.
Clerk, Inc. participates in the EU-U.S. Data Privacy Framework. Its registration is active and covers all data except data about Clerk's own staff. It therefore includes data Clerk processes for Octofin. The European Commission has adopted an adequacy decision for that framework (Implementing Decision (EU) 2023/1795). Clerk's registration is available at dataprivacyframework.gov.
For cases where the framework cannot be relied upon, Clerk's data processing agreement incorporates the European Commission's standard contractual clauses (Implementing Decision (EU) 2021/914). Module 2 applies to data Clerk processes as processor. Module 1 applies to data for which it is an independent controller (section 6.4).
7.3 Copies of safeguards
The data processing agreements containing the standard contractual clauses are public through the links in this section. Copies and an explanation are also available through contact@octofin.be.
8. Local storage
8.1 Principle
The app stores on the device what is needed for the use the staff member or Organisation requests: signing in, applying chosen settings, opening and moving documents, updating and maintaining the local copy. None of it serves analytics or advertising. We do not request separate consent for that necessary storage.
8.2 Storage locations
Data is held in the Windows user's %LOCALAPPDATA%\Dieplink\Desktop\ folder. Opened documents are in %TEMP%\Dieplink\. The local copy is in the folder the Organisation chooses.
Uninstalling the app removes the Desktop folder and temporary files. It does not remove the local copy or files a staff member saved elsewhere.
8.3 Data that leaves the device
Three types of data do not remain solely on the device:
- the sign-in session, which works with Clerk (sections 6.4 and 7.2);
- the local copy's folder path, which we keep in the cloud service so administrators can see which folder is used;
- a local copy in a synchronised folder, which also reaches the service the Organisation chose.
Other local settings and the technical log do not leave the device. Documents are transferred for the requested upload or copy.
8.4 Storage by function
| Data | Location | Function | Retention and removal |
|---|---|---|---|
| Clerk sign-in session and cookies | WebView2 profile (Desktop\WebView2\) | Sign in and stay signed in, including after restarting | At most 8 hours; expires after 1 hour without activity. Signing out ends the session and clears cookies and browsing data. Also removed on uninstall |
| Chosen language and animations | WebView2 profile (dl-lang, dl-anim) | Apply the chosen display settings | Until changed or uninstalled. Signing out keeps the language but clears the animation preference |
| Chosen shortcut | hotkey.json | Open the app with that shortcut | Until changed or uninstalled; retained at sign-out |
| Window position and size | window.json | Open the window where the staff member placed it | Screen coordinates, not personal data. Updated on movement; removed at sign-out and uninstall |
| Microsoft WebView2 cache | WebView2 profile | Display the app | Managed by WebView2; cleared at sign-out and uninstall. The local copy's index is excluded at sign-out |
| A downloaded update | updates\ | Update the app | Until installation; removed at the next start |
| Opened documents | %TEMP%\Dieplink\open\ | Open in another program; Windows needs a file on the device for this | Removed at start, sign-out and uninstall. An ordinary document copy is not reused |
| Session copy of an opened Exact attachment | %TEMP%\Dieplink\open\session-…\ | Show the opened attachment again without a second Exact request; the cloud service checks access again | The app checks every 10 seconds, after giving the other program one minute to start. It removes the copy once no window shows the document name and no program holds the file. Also removed at exit and sign-out. A leftover copy is not reused after restarting or signing out |
| An e-mail added from Outlook | drops\ | Upload the e-mail | Removed as soon as the app has taken it; otherwise at the next drag once at least 2 minutes old. Also removed at start, exit and sign-out |
| A document dragged out of the app | dragout\, restricted to the Windows user and system | Pass the file to the other program | For asynchronous transfer, until the other program finishes, at most 10 minutes; for ordinary transfer, one further minute. Otherwise immediately. Locked files are retried every 15 seconds; also cleaned at start, exit and sign-out |
| On the local-copy device only: chosen folder and encrypted device key | mirror\config.json | Maintain the local copy | Until the local copy is stopped or the app uninstalled; retained at sign-out. Only the key is encrypted, for this Windows user |
| On the local-copy device only: file index and progress | WebView2 profile (IndexedDB dieplink-mirror) | Maintain the local copy | Until uninstall; retained at sign-out. A new installation rebuilds the index |
| A document while being copied locally | mirror\staging\ | Check the copy before placing it in the chosen folder | Removed as soon as the copy succeeds or fails. If interrupted, it may remain, including after sign-out; the next start or uninstall clears it |
| Local copy with _dieplink-manifest.json (path and checksum per copy) | Organisation's folder | Keep all documents and notes locally (optional) | Dieplink removes nothing from this folder, including at sign-out, stopping the copy or uninstall. Deleted or unlinked documents go to _verwijderd. The Organisation manages and deletes the folder |
8.5 Technical log and signing out
The technical log host.log serves to investigate app failures. It contains events such as start, shortcut use, show and hide, display errors and exit. It contains no document content, file names or paths; for an opened file, only its extension.
At the next log entry, the file starts over once it is 7 days old or the next entry would take it beyond 256 KB. A log from an older app version is replaced at the first new entry. Signing out clears the log; it then starts again with the sign-out entry. Uninstall also removes it.
The last administration used and recently opened lists are held only in working memory, not on disk. An old saved administration preference is removed at start.
Signing out clears browsing data, temporary opened and dragged files, window position and the animation preference. The language, chosen shortcut and local copy with its settings, staging files and index remain. A downloaded update also remains: it contains only program code.
If another program locks a file, it may remain until the next cleanup attempt or restart. Files the staff member saves elsewhere are outside the app.
9. Retention and deletion
9.1 Principle
Dieplink never automatically deletes documents solely because of their age. The Organisation decides how long to keep its documents; the law sets differing retention periods.
Section 9.2 lists Dieplink's retention periods and their starting points. Sections 9.3 to 9.9 explain them. In this section, "erasure of the Organisation" means erasure of all its data under section 9.8.
The cloud service runs automatic deletion jobs every hour. Data therefore disappears at the first hourly deletion after its period ends. Large volumes may be handled at a subsequent hourly run.
The periods in section 9.2 apply to the database and file storage. After a period ends, data may remain in backups and at suppliers for the periods in section 9.6.
9.2 Overview
| Data | Retention period and starting point |
|---|---|
| Documents, notes, links and follow-ups | Until the Organisation deletes them or is erased. After deletion: 30 days in the trash, starting at deletion (section 9.3) |
| Exact data | Until the Organisation is erased. Section 9.4 applies to data deleted in Exact |
| Activity log, including staff name and e-mail address | Until the Organisation is erased (section 9.5) |
| Membership and access rights | Access and access rights end when the staff member is removed. The historical membership record remains until the Organisation is erased (section 9.5) |
| Clerk account | While the staff member belongs to an organisation. Afterwards: 30 days after removal from the last organisation, or sooner on request (section 9.5) |
| Copies at Clerk after account erasure | Backups: 15 days from backup creation. Logs: 15 to 90 days from recording. Sent messages: at most 37 days from sending (section 9.6) |
| Daily dashboard backups at Convex | Not enabled in the current environment; no such backups exist. This is separate from internal supplier copies (section 9.6) |
| Convex internal backup and archive copies | Under Convex's retention schedule. The data processing agreement specifies no period (section 9.6) |
| Uploads never completed (documents and feedback images) | 24 hours from the start of the upload |
| Feedback reports | Report: 180 days from sending. Images: 30 days from storage. Sooner on the reporter's or Organisation's request, and in any event when the Organisation is erased |
| Exact call counts | 35 days from the end of the day on which calls were counted |
| Exact notifications about changed lists | 7 days from receipt |
| Export files ready for download | 24 hours after the export becomes ready or fails |
| Document download links | Single use, valid for 90 seconds from issue |
| Local-copy change list (technical identifiers and sequence numbers) | 30 days from the change |
| An Exact connection being requested | Unusable 10 minutes after the request starts; deleted no later than 1 hour and 10 minutes after that start |
| Exact access keys | Until disconnection (section 10.3) or erasure of the Organisation |
| Erasure register after an organisation is erased | The two Clerk user IDs: 12 months from erasure. Other data: no end date (section 9.7) |
| Octofin's invoices and accounting records (section 4.2) | Invoices: seven years from 1 January following the year of issue. Other supporting accounting records: seven years. Accounting books: seven years from 1 January following the financial year's closure. Income-tax books and records: until the end of the seventh year following the taxable period (section 9.10) |
| Invoicing contact's name and e-mail address outside invoices and accounts | Not collected separately for invoicing during the free pilot |
| Data on the device | Sections 8.4 and 8.5 |
9.3 Trash
A deleted document or note remains in the trash for 30 days from deletion. During that period it can be restored. Afterwards, we erase the file, links and data from the database and file storage.
Copies may then remain in backups and at suppliers for the periods in section 9.6. The Organisation deletes copies outside Dieplink itself (section 9.9).
The trash period is not a deadline for handling personal-data erasure requests (section 10.5).
9.4 Deletions in Exact Online
We process an Exact deletion when we read it from Exact, usually a few minutes after its notification and no later than the twice-daily check.
A deleted booking line is no longer visible from then on. We erase the line from the database during the weekly full check.
Exception: a relation, account or booking with a document or follow-up still linked is retained marked "Deleted in Exact", so the link is not lost.
9.5 When a staff member leaves
A staff member removed from the Organisation immediately loses access to it through Dieplink. We end their membership and delete their access rights. The historical membership record remains until the Organisation is erased: name, e-mail address, Clerk user ID, role and membership timestamps.
Removal does not erase documents previously saved outside the app. Nor does it change that person's access to the local copy or a shared folder. The Organisation manages that access itself.
The staff member's name and e-mail address remain in the activity log until the Organisation is erased. The activity log is Organisation Data. The Organisation needs to establish who added, linked or deleted a document. The name makes that person recognisable; the e-mail address distinguishes people with the same name.
For removals since this rule was introduced, we delete the Clerk account 30 days after the latest removal if the person then belongs to no organisation. We check this both in Dieplink and at Clerk. Anyone who has become a member again keeps their account. For earlier removals, deletion is on request through contact@octofin.be; staff can also request earlier erasure there. After erasure of an entire Organisation, Octofin deletes within 30 days accounts belonging to no other organisation.
9.6 Copies at suppliers
Convex
Data we erase disappears immediately from Convex's database and file storage.
Daily dashboard backups are not enabled in the current environment. No such backups of the database or document files exist. We therefore promise no daily recovery point. This is separate from the internal copies Convex keeps for its service.
Convex maintains internal backup and archive copies. It deletes them under its own retention schedule, in accordance with section 8 of Convex's data processing agreement. The agreement specifies no period; no maximum duration for all internal copies is publicly specified. The 7-day retention of optional daily dashboard backups does not apply to those internal copies. Legally required retention remains an exception; such data is isolated and not processed for other purposes.
When we restore a backup, we erase again every organisation erased after the backup's timestamp. The erasure register serves this purpose (section 9.7). There is no general automatic replay register for deletions of individual documents, notes and personal data. A restore may contain that data again. Octofin must therefore check and repeat the deletion instructions separately before the restored data is used again.
Clerk
Erasure of a Clerk account is separate from the end of the agreement between Octofin and Clerk.
When an account is erased, the account, identifiers and sessions disappear immediately from Clerk's database. The following copies remain afterwards:
- backups: each expires 15 days after creation;
- logs containing user and session IDs: 15 to 90 days from recording, depending on the logging system;
- messages Clerk sends: e-mail data for at most 37 days from sending; SMS data for 7 days from sending.
At the end of its agreement with Octofin, Clerk deletes the data it processes for Octofin within 90 days, under section 9 of Clerk's data processing agreement.
For data Clerk processes as an independent controller (section 6.4), Clerk determines retention itself under its privacy policy.
9.7 Erasure register
After an organisation is erased, we keep an erasure register for two purposes: demonstrating that erasure was requested, confirmed and executed, and preventing restoration of the erased organisation, including when a backup is restored.
The register contains four types of data:
- Clerk user IDs of the administrator who requested erasure and the administrator who confirmed it;
- organisation identifiers as hashes;
- the times of each step;
- counts.
The register contains no names, e-mail addresses or documents.
The two user IDs are personal data: they refer to a Clerk account. We delete them 12 months after the organisation's erasure. Within that period they provide evidence of the request and confirmation if the organisation disputes the erasure.
We retain the other data without an end date: there is no automatic deletion for it. The hashes prevent a backup or Clerk notification from recreating the erased organisation.
The hashes identify the organisation. Where the organisation is a natural person, or a hash can be linked to a person, the hash is personal data.
9.8 Termination by the Organisation
Before leaving, the Organisation can export all its data. The export includes original documents, an Excel overview, and links, follow-ups, staff, access rights and the activity log in a readable data format. Through export and erasure, the Organisation chooses between return and erasure of its data (Article 28(3)(g) GDPR).
An administrator then requests erasure of the Organisation. An administrator confirms it in a separate step; this may be the same administrator. The administrator submits the request through contact@octofin.be and carries out erasure together with Octofin.
A 30-day grace period starts at confirmation. A different period, at least 7 and at most 365 days, is set when requesting erasure. Erasure can be cancelled during the grace period.
After the grace period, we erase all the Organisation's data and the Exact access keys. First, we attempt to remove Dieplink's webhook subscriptions at Exact. If that fails, erasure waits at most one day. When cleanup is abandoned, subscriptions may remain at Exact; the access keys are nevertheless erased.
The grace period applies only to erasure of the entire Organisation. It does not determine how an individual's personal-data erasure request is handled (section 10.5).
Ending use alone does not start automatic erasure. The Organisation communicates its choice of return or erasure through contact@octofin.be. Data remains stored until the erasure procedure is completed. An Organisation with one administrator can also complete the request and separate confirmation.
9.9 Data outside Octofin's control
The local copy (section 6.2) and documents staff have saved themselves remain with the Organisation. It deletes that data itself.
9.10 Octofin's invoices and accounting records
Four statutory retention periods apply to Octofin's own invoices and accounting records:
- invoices: seven years from 1 January following the year of issue (Article 60 of the Belgian VAT Code);
- other supporting accounting records: seven years (Article III.86 of the Belgian Code of Economic Law);
- accounting books: seven years from 1 January following the financial year's closure (Article III.88 of the Belgian Code of Economic Law);
- income-tax books and records: until the end of the seventh year following the taxable period (Article 315 of the Belgian Income Tax Code 1992).
The seven-year VAT and income-tax periods follow from the Act of 18 December 2025 containing various provisions. If a record falls under more than one period, we keep it until the latest expires.
Where a longer special statutory period applies or a legal claim is ongoing, we retain only the data needed for that purpose for longer. These periods do not apply to the Organisation's documents in Dieplink.
10. Exact connection, authorisation and erasure
The actions in this section are separate. The overview identifies each action's effect and what data remains. Sections 10.1 to 10.5 explain them.
| Action | Effect | Data that remains |
|---|---|---|
| Revoke authorisation in Exact Online (section 10.2) | Dieplink stops reading Exact data | Data already in Dieplink |
| Disconnect Exact in Dieplink (section 10.3) | Synchronisation stops; Dieplink attempts to remove its webhook subscriptions and erases the access keys | The authorisation in Exact Online and data already in Dieplink; webhook subscriptions may remain at Exact if cleanup fails |
| Delete a document or note (section 10.4) | 30 days in the trash, then erased from database and file storage (section 9.3) | Copies in backups and at suppliers for the periods in section 9.6; copies outside Dieplink (section 9.9) |
| Remove a staff member from the Organisation (section 9.5) | Access and access rights disappear immediately; the Clerk account follows section 9.5 | The historical membership record and activity log; that person's access to the local copy or a shared folder |
| Request erasure of personal data (section 10.5) | Assessment by the controller within the deadlines in section 11.3 | Data covered by the three exceptions in section 10.5 |
| Erase the Organisation (section 9.8) | All Organisation data erased after the grace period | Erasure register (section 9.7); backups and supplier copies (section 9.6); local copy (section 9.9) |
10.1 Withdrawing consent
None of the processing in section 4.2 is based on consent within the meaning of the GDPR (section 4.4). For that processing there is therefore no consent to withdraw.
The rights you can exercise depend on the processing and its legal basis. Section 11 describes those rights and their conditions.
Authorisation in Exact Online is not GDPR consent; section 10.2 explains its revocation. Section 8 covers storage on the device and how it is cleared.
10.2 Revoking authorisation in Exact Online
The administrator who authorised Dieplink in Exact Online can revoke that authorisation in Exact Online at any time. Dieplink then stops reading data from Exact.
Data already in Dieplink remains stored until the Organisation has it erased.
10.3 Disconnecting Exact in Dieplink
An administrator can also have the Exact connection disconnected in Dieplink. They request this through contact@octofin.be and carry it out together with Octofin. There are three steps:
1. Synchronisation stops immediately.
2. We attempt to remove Dieplink's webhook subscriptions at Exact. If that fails, we retry hourly for at most 7 days. If Exact refuses the grant, cleanup stops earlier.
3. We erase the Exact access keys, including when cleanup is abandoned and subscriptions remain at Exact.
Disconnection does not revoke authorisation in Exact Online or erase data already in Dieplink. The other actions in this section serve those purposes.
10.4 Deleting a document or note
A staff member deletes a note (Information) in the app using Delete.
To delete a document, a staff member requests it through contact@octofin.be. Octofin carries it out together with an Organisation administrator.
A deleted note or document first remains in the trash for 30 days (section 9.3).
10.5 Requesting erasure of personal data
For personal data in the Organisation's documents or accounts, address your request to the Organisation. This applies, for example, if you are its client. Use the contact details it has given you.
The controller decides on the request: the Organisation, or its client where it acts as processor for that client. Octofin assists the Organisation as processor.
If Octofin receives such a request directly, we forward it to the Organisation without undue delay, sharing only the data needed to handle it.
For your staff account, feedback reports and other Account Data, send your request to contact@octofin.be.
An erasure request is assessed separately and handled within the deadlines in section 11.3. Neither the trash period (section 9.3) nor the grace period (section 9.8) postpones that handling.
Erasure is not always complete and immediate:
- data the Organisation or Octofin must keep by law remains for as long as the obligation applies, solely for that purpose;
- data needed to establish, exercise or defend a legal claim remains for as long as necessary for that purpose, solely for that purpose;
- erased data remains in backups and at suppliers for the periods in section 9.6. We no longer use it during that period.
11. Data subjects' rights
11.1 Overview of rights
Under the conditions of the GDPR, you have the following rights:
- access: access your data and receive a copy;
- rectification: correct inaccurate data and complete incomplete data;
- erasure: have your data erased in the cases in Article 17 GDPR. Section 10.5 lists the exceptions;
- restriction: restrict processing, including while accuracy or your objection is assessed;
- portability: receive data you supplied in a commonly used digital format or have it transferred;
- objection: see section 11.2.
Portability applies to data you supplied that is processed automatically on the basis of consent or a contract with you. None of the processing in section 4.2 relies on those bases. The right therefore does not apply to Account Data.
For Organisation Data, the controller assesses your request (section 10.5). The Organisation can export all its data (section 9.8).
11.2 Right to object
The right to object does not apply to processing based on a legal obligation. It is not the same as withdrawing consent (section 10.1).
11.3 Making a request
Send a request concerning data for which Octofin is controller to contact@octofin.be or by post to Octofin, Wilgenstraat 21, 9450 Haaltert, Belgium. No account is required. Address requests about data in an organisation's documents and accounts to that organisation (section 10.5).
Requests are free of charge. We request additional identity information only where we have reasonable doubts about your identity.
We respond as soon as possible and no later than one month after receipt. For a complex request or numerous requests, that period may be extended by two months. We notify you of the extension and its reason within one month of receipt.
If we do not act on your request, we give our reasons within one month of receipt and inform you of your right to complain and seek a judicial remedy (section 11.4).
11.4 Complaints
If you disagree with how we process your data, you may tell us through contact@octofin.be.
You have the right to complain to the Belgian Data Protection Authority (Gegevensbeschermingsautoriteit, GBA) through its complaint page. You may also contact another competent supervisory authority, such as in the country where you live or work. You may also seek a judicial remedy.
12. Security
- Sign-in. Each staff member has a personal account with mandatory two-step verification. A session lasts at most 8 hours.
- Separation. On every request, the cloud service checks which organisation and administrations the staff member may access. On every software change, automated tests attempt to access other people's data.
- Encryption. All connections are encrypted (HTTPS). Convex encrypts stored data and files. We additionally encrypt Exact access keys with a key held outside the database.
- Fetching and uploading files. These use single-use access codes only. A download code is valid for 90 seconds and stored only as a hash. Nobody receives a direct storage link.
- Exact. Dieplink sends only pre-approved requests to Exact: read requests, token requests and creation or deletion of its own webhook subscriptions. The software refuses every other request.
- Activity log. The log records which staff member performed which action, without document content, file names, links or access codes.
- Local copy. Only an administrator activates it, for one registered device. Each copy is checked for authenticity. A staff member who is no longer an administrator immediately loses that device's access. Files already in the folder remain; the Organisation manages folder access itself (section 6.2).
- Backup. The current environment has no daily dashboard backups. Section 9.6 applies to Convex's internal backup and archive copies.
No security measure eliminates every risk. Dieplink holds no certification within the meaning of the GDPR.
13. Changes
The version and date appear at the top of this statement.
We announce substantive changes in advance in the app and to organisations' administrators. These include new purposes, new suppliers and changes to how rights are exercised. For a new purpose, we provide the information before using data for that purpose.
Send questions and comments about this statement to contact@octofin.be or by post to Octofin, Wilgenstraat 21, 9450 Haaltert, Belgium.