Personal data service agreement

Transaction records and receipts are compared at a computer

Version 1.3 · October 21, 2026

This agreement is an appendix to Vinnras terms of use. If the customer also has a letter of assignment, the agreement is an appendix to that as well.

1. Parties

The customer is the company that has an agreement with us according to the main agreement. The customer is responsible for personal data. This means that the customer decides why and how the personal data is processed.

We are Innova Horizon AB (Vinnra), org.nr 559241-8999, Edebovägen 130, 763 91 Hallstavik, vinnra. We are a personal data processor. This means that we process personal data on behalf of the customer and according to the customer's instructions.

The main agreement means Vinnras terms of use and, if there is one, the assignment letter.

2. Why the agreement exists

2.1 We deliver the Vinnra service according to the main agreement. When we do so, we process personal data on behalf of the customer.

2.2 The agreement regulates that processing according to Article 28 of the EU Data Protection Regulation (EU) 2016/679, GDPR.

2.3 Words in the agreement mean the same as in the GDPR. By processing is meant everything that is done with personal data, for example collecting, saving, reading, sending and deleting them.

3. What we process

Regarding the treatment

Storage and processing of the customer's accounting and financial data in Vinnra.

Purpose

To deliver the service according to the main agreement: accounting, invoicing (including e-mailing invoices to the customer's customers), reports, export, backup, support and troubleshooting. In addition, interpretation of documents and proposals from the AI assistant according to point 4.5, as well as receiving and importing accounting data that the customer has exported from another system, for example in SIE format. SIE is the common language that Swedish accounting programs use to move accounting between each other.

What we do with the data

Collects, records, stores, compiles and reads them. Automatically interprets them into suggestions, also with AI according to point 4.5. Emails them, exports, backs up, restricts and deletes them.

Which persons the information applies to

The customer's customers, suppliers and employees, their contact persons, the customer's representatives and users of Vinnra.

What information

Name, address, e-mail and telephone. Organization number and social security number if they are in the documents. Bank account number, amount and transactions. The content of receipts, invoices and other documents. Information about users needed for authorization and to show who has done what.

How long

As long as the main agreement applies. Then according to point 11.

3.1 Sensitive data. The customer must not enter sensitive personal data in Vinnra, for example information about health (Article 9 of the GDPR). Exceptions are what cannot be avoided in normal accounting documents. Receipts and invoices can contain social security numbers and show what a person has bought, for example at a pharmacy or in healthcare. The customer must therefore ensure that users - cover social security numbers before the document is photographed, whenever possible, and - select "Interpret without AI" for documents with health information.

Invoice texts that are emailed via Vinnra must not contain information about health.

4. Customer's instructions

4.1 We may only process the personal data according to the customer's documented instructions. The Master Agreement and this Agreement are the Customer's instructions. This also applies if data is transferred to a country outside the EU/EES, a so-called third country.

4.2 If a law requires us to process the data in any other way, we must tell the customer before we do so. This does not apply if the law prohibits us from telling.

4.3 If we believe that an instruction contravenes the GDPR or other data protection regulations, we must immediately tell the customer.

4.4 We may not use the personal data for our own purposes.

4.5 AI Interpretation. The customer commissions us to have an AI service within the EU, as specified in Appendix 1, interpret uploaded documents and the users' questions to the assistant. The result is always a proposal. Nothing is posted, created or sent until a user has approved the proposal. We must ensure that - the AI interpretation takes place within the EU/EEA, - the sub-assistant does not use the customer's data to train or improve AI models, - social security numbers are removed from filenames, notes and text before sending anything, as far as this is technically possible. Social security numbers in an image cannot be removed, and - a user can choose to have a document interpreted without AI. Then the document is not sent to the AI service.

5. Duty of confidentiality

5.1 Everyone who is authorized to process the personal data must have promised to keep it secret or have a duty of confidentiality according to law.

5.2 Only those who need access for their work may have it. If we need to access an individual customer's data for troubleshooting, we will only do so with the customer's written consent. Access is time-limited and logged.

6. Security

6.1 We shall have the technical and organizational safeguards required in accordance with Article 32 of the GDPR. The measures are described in Appendix 2.

6.2 The personal data in Vinnra is stored in Sweden. This applies to the database, supporting files and backup copies, which are available at our operating supplier in Stockholm. AI interpretation (point 4.5) takes place with an AI service within the EU/EEA, but outside Sweden. The provider's group companies and support providers, including in the USA and India, may have limited access for maintenance and support, according to Appendix 1. Invoice emails and login links to the demo are sent via an email service within the EU. The emails contain no tracking. Some data is processed by subcontractors outside the EU/EEA, for example IP addresses, access logs and data in support cases. This is evident from the list of assistants (appendix 1).

7. Assistants

A subcontractor is a company that we hire and that processes the customer's personal data for us.

7.1 Through this agreement, the customer gives a general prior written permission for us to engage the subcontractors listed in Appendix 1. Appendix 1 with named subcontractors is shown to the customer before the agreement is approved and is then available in the service. It is also sent on request to vinnra.

7.2 We must notify the customer at least 30 days before we hire a new subcontractor ourselves or replace an existing one. The customer may object during that time. If we do not agree, the customer may terminate the main agreement so that it ends before the change is implemented.

7.3 If one of our subcontractors engages or replaces its own subcontractor, we will notify the customer no later than 3 working days after we have received the notification. The customer may object within 7 days of our notification. If the objection cannot be met, the customer may terminate the main agreement. A sub-assistant may have the right to hire a new sub-assistant without notice to protect the position. We will then notify the customer as soon as we know.

7.4 We shall, by written agreement, give each subcontractor the same obligations to protect the data that we have under this agreement.

7.5 We are fully responsible towards the customer for the assistants doing what they are supposed to.

7.6 We shall without undue delay forward to the customer the messages from the assistants that apply to the customer's information. This applies to personal data incidents, new assistants, requests from data subjects and notifications of transfers to third countries.

8. Transfer to countries outside the EU/EEA

8.1 Personal data may only be transferred to a country outside the EU/EEA if the transfer is listed in Appendix 1 and is supported by Chapter V of the GDPR. The support for each transfer is in Appendix 1. Such support can, for example, be the EU Commission's standard contract clauses, i.e. ready-made contract terms that the Commission has approved.

9. Our help to the customer

A registered person is the person to whom a personal data applies.

9.1 We shall, as far as possible and with technical and organizational measures, help the customer when data subjects use their rights according to Chapter III of the GDPR, for example the right to know what information is available or to have it corrected. If a data subject contacts us directly, we refer to the customer and notify the customer without delay.

9.2 We shall assist the customer in fulfilling the obligations in Articles 32-36 of the GDPR. They apply to security, personal data incidents, impact assessment and prior consultation with the Swedish Privacy Agency. The help is based on how the treatment is carried out and what information we have. For the AI interpretation (point 4.5), we provide the information the customer needs for their own impact assessment. An impact assessment is an analysis of the risks for the data subjects (Article 35 of the GDPR).

9.3 Data that the customer must save according to the Accounting Act, the customer can archive in Vinnra during the time they must be saved. Archiving means hiding the data and restricting its use. Data that does not need to be saved can be deleted by the customer.

10. Personal data incidents

A personal data incident is, for example, that data is lost, destroyed, accidentally changed or reaches unauthorized persons.

10.1 We shall notify the customer without undue delay after we become aware that a personal data incident has occurred, and no later than within 48 hours.

10.2 The notification must, as far as possible, contain - what has happened, - which groups of registered users and approximately how many people and items are affected, - what consequences the incident is likely to have, - what measures have been taken or proposed, and - a contact person.

Information that is not available from the beginning we leave as soon as we have it.

10.3 The customer is responsible for reporting the incident to the Privacy Protection Authority and for informing the data subjects.

11. When the agreement ends

11.1 The customer closes the account in the app and confirms by typing the company name. It is the customer's instruction on what should happen with the personal data.

11.2 We return the personal data by providing the customer with a link to their data: accounting information in SIE format, reports and documents. The link requires login and is valid for 30 days from the end.

11.3 We delete the personal data and existing copies 30 days after termination. Data in backup copies is deleted within 14 days thereafter, according to Appendix 2. This does not apply to data that the law requires us to save. How the customer's accounting information is handled after the end of the agreement is stated in the terms of use (section 11).

11.4 If the customer requests it, we confirm in writing that the data has been deleted.

11.5 We process certain data as personal data controllers for our own purposes, and they are not covered by this agreement. This applies to invoices that we have issued to the customer, the control that the trial period is only used once per company and the log of which conditions were approved. How we treat them is stated in our privacy policy.

12. Review

12.1 We shall provide the customer with all information necessary to demonstrate that we fulfill our obligations under Article 28 of the GDPR. We shall also enable the customer, or a reviewer appointed by the customer, to review and inspect us, and contribute to the review.

12.2 A review must be notified at least 30 days in advance, unless an incident means that a shorter time is needed. Each of the parties bears its own costs.

12.3 Review by a sub-agent takes place within the framework that the sub-agent's conditions allow. If the customer requests it, we provide the security documentation provided by the sub-assistant. The sub-advisor may require the customer to first sign a non-disclosure agreement.

13. Register

13.1 We keep a register of the processing we carry out on behalf of the customer in accordance with Article 30.2 of the GDPR.

14. Liability

14.1 Liability for damage caused by the processing is distributed according to Article 82 of the GDPR. Otherwise, the rules on liability in the main agreement apply.

15. Validity

15.1 The agreement applies as long as we process personal data on behalf of the customer.

15.2 If this Agreement and the Main Agreement say different things on a matter of personal data, this Agreement will control.

Attachments

  1. Sub-assistant list (named sub-assistants) – displayed before approval and in service; sent on request to vinnra
  2. Technical and organizational security measures

Appendix 2 – Technical and organizational security measures

Version 1.3 · October 21, 2026

The appendix describes the security measures that apply today.

1. Measures

1.1 Encrypted traffic. All access to the app is over HTTPS.

1.2 Encryption at Rest. Customer data in the operating provider's data center is encrypted at rest according to the provider's personal data processing agreement. Environment variables are stored encrypted.

1.3 Location. Database, supporting files and backup copies are located in the data center in Stockholm.

1.4 Customer Separation. Each customer's data is kept separate by company ID in the application and in the database keys. The lock is in the app code.

1.5 Login Session. The session cookie vinnra_session is HttpOnly and SameSite=Lax. In a production environment, Secure is set.

1.6 Append-only accounting. Verifications and event logs are protected from modification and deletion with database triggers in the flows built for it.

1.7 Operating logs. The operating provider saves driving logs and access logs for a limited time (currently up to 60 days according to the provider's documentation).

1.8 Backups. Automatic database backup once a day, saved for 7 days. Up to 5 manual backups, saved 14 days. The copies are located in the same data center. Data for a closed account therefore remains in backup copies for a maximum of 14 days after it has been deleted.

1.9 Debugging Access. Access to an individual customer's data for troubleshooting requires the customer's written consent, is time-limited and logged (as per Clause 5.2 of the Data Processor Agreement).

1.10 Email. Outgoing e-mail (invoices, login links and codes, links to data at checkout and demo links) goes via e-mail service within the EU, without a tracking pixel.

1.11 AI Interpretation. Calls to the AI service are only made in the EU region. No web search is linked to the model. Implicit cache of the AI service is turned off. Social security numbers are removed from file names, notes and text before calls (not from images). The user can select "Interpret without AI" per substrate; then no call is made. AI suggestions are never posted without a user's approval.

1.12 Login by e-mail. Login links and codes are valid for 30 minutes and can only be used once. We only save them in hashed form. The number of attempts is limited per code, per IP address and per email address. The IP address is saved for that purpose as an HMAC, i.e. not in clear text. Used and expired links and codes are deleted after 30 days.

1.13 Data at termination. The customer's data is provided via a link that requires login and is valid for 30 days. The account's data is deleted 30 days after termination.

Previous versions: version 1.2