Privacy policyAvtalor

Privacy policy

Effective 18 November 2026 · version 1.6

This policy explains how personal data is processed in Avtalor, and also constitutes the data processing agreement between Avtalor AS as processor and the Company as controller.

Roles and responsibilities

The Company is the controller for data about its own employees and determines the purpose of the processing. Avtalor AS is the processor and processes data only on the Company's instructions and to deliver the Service.

For data about Avtalor's own contacts at customers and suppliers, and for marketing the Service, Avtalor is itself the controller.

For people who use Avtalor without belonging to a Company (“members without a company” in Avtalor Specials), Avtalor is itself the controller. If the person is later connected to a Company, the Company is the controller for data about the person as an employee or member from then on, as for other employees. The Supplier is itself the controller for what happens at the Supplier after a code has been used there.

Controller at Avtalor: Avtalor AS, company no. 916 048 092, Oslo. Privacy contact: support@avtalor.com

What data is processed

Account data: name, work email, phone number, job title, profile photo and role affiliation. Legal basis: necessary to perform the contract, GDPR Article 6(1)(b), and the controller's legitimate interest in administering employee access, Article 6(1)(f).

Usage data: which agreement cards are opened and used, time, category, device type and a pseudonymised user identifier. Legal basis: legitimate interest in operating, securing and improving the Service, Article 6(1)(f).

Content of documents uploaded for machine reading, including agreement text and contact details appearing in the document. Legal basis: performance of the contract, Article 6(1)(b).

AI features: questions to the agent with information about the agreements the user has access to, agreement text and documents read by machine, text being translated, the website a supplier fills in its profile from, prospect lists a supplier uploads (with the names and contact details of the contact persons in them), and search terms in the help that gave no results, without who searched. The content is sent to the Claude language model from Anthropic through Vercel AI Gateway to create the answer, and is not stored by us. If Anthropic is unavailable, the same model at Amazon Web Services or Google Cloud may answer instead, see Sub-processors. We store only the number of tokens, the cost and the status of each call. The agent is used only after the user has consented, and the consent can be withdrawn under Settings. Legal basis: consent, point (a), for the agent, and performance of a contract, point (b), for machine reading and translation.

Reported problems with an agreement, including free text written by the employee. Legal basis: legitimate interest in correcting errors, Article 6(1)(f). The identity is visible to the Company's administrator, but not to the Supplier.

Consents and notification preferences. Legal basis: consent, Article 6(1)(a), and the duty to document consent, Article 7(1).

Device data for notifications: a push token and the device's name in the mobile app, and a push subscription in the browser, when notifications are turned on. Legal basis: performance of the contract, Article 6(1)(b).

We never store passwords. Sign-in uses a one-time code, a one-time link or a passkey. For a passkey we store only the public key, the key ID, a counter that increases with each sign-in, how the device reaches the key (transport, such as built-in, USB or Bluetooth), the authenticator model (AAGUID), whether the key is backed up, the kind of device it was created on and the name the user gives it, with the time it was created and last used. The private key and biometrics, such as a fingerprint or face, never leave the device.

Sign-ins: the time of each sign-in, linked to the account, for security and for statistics on use of the Service. Legal basis: legitimate interest, point (f).

Signing and approval of agreements: when a supplier sends an agreement to a company, we store who sent, approved, commented on or signed it, with name, email address and role. For a signature we also store the signature as it was drawn or typed, the time from the database clock, the IP address and which browser was used, and a checksum (SHA-256) of exactly the text that was signed. The IP address is shown masked in the agreement document (PDF) and stored in full by us, so that the signature can be documented in a dispute. A user can choose to save their signature on the account to use it again. The signature is a simple electronic signature. Legal basis: performance of a contract, point (b), and legitimate interest in being able to document what the parties agreed, point (f).

AI assistants: a user with Pro can connect Avtalor to their own AI assistant, such as Claude from Anthropic, ChatGPT from OpenAI or Microsoft Copilot. The assistant can then search and read the agreements the user has access to in Avtalor, and for employees also the discount code for an agreement. We store which assistant is connected, when access was granted and last used, and which company and role it applies to. To measure usage, we store which channel and which action (search, view or code handed out) was used, and for which company, but not who the user is or what was searched for. What the assistant receives is processed by the provider of the assistant under the user's or the employer's own agreement with it, and not by Avtalor. Access can be withdrawn at any time under Settings, and an administrator can turn the feature off for the whole company. Legal basis: performance of a contract, point (b), at the user's request, and legitimate interest in measuring use of the Service, point (f).

Preselected appearance: when you create your account, the first name you enter may be used to preselect the colour theme in the Service. The suggestion is an inference from the first name: the name is compared, in your browser, with a list of names that is part of the Service. Nothing is sent to a third party, no extra calls are made to our servers, and the name is not logged. On the account, only the theme you confirm or choose yourself is stored, together with when it was saved. In addition, your device remembers whether you chose the theme yourself, or whether it was saved when you completed registration without choosing (it is then marked as preselected, also when it is the default theme), and when. This is stored only on the device, in a cookie and in the browser's local storage, not on the account, and is used for only two things: to keep the website in the default theme until you choose yourself, and, when you sign in, to decide whether a theme you chose yourself on the device is newer than the theme on the account and should then be saved to the account. Nothing else about you is stored because of the suggestion. If you complete registration without changing the theme, the theme shown is stored as your theme, whether it is the suggestion or the default theme. Your first name is stored on the account as part of the account data, not for this purpose. You can change the theme at any time in Settings. Legal basis: legitimate interest in letting new users start with an appearance they are likely to like, without having to look for it, point (f).

Feedback: you can send feedback from anywhere in the Service, either that something is not working or a suggestion. We store the text you write, up to 2,000 characters, the category, whether we may contact you, the account and the Company or Supplier you sent it from, and some information that helps us find the problem: the page you were on, without content and without IDs, your role, the language, a short description of the device and browser, and the app version if you use the app. We do not store screenshots, page content, IP address or the full user agent. Please be careful about writing personal data in the text. Feedback is read by Avtalor's operations team. If you said yes to us contacting you, we may email you at the account's address about what we have decided. If you say no, we send nothing. Legal basis: legitimate interest in correcting errors and improving the Service, point (f), for the feedback and the page and device information, and consent, point (a), for email about the matter.

Avtalor Specials for members without a company: a person who does not belong to a Company can register with their email address and see agreements that Suppliers have opened to everyone. We store the email address and the time the terms were accepted. No name or other information is needed. Anyone with the link can see the title and price of an open agreement, while the code or link to the offer is shown only after signing in. When anyone retrieves the code for an open agreement, whether they are a member without a company or an employee or member of a Company, we store who, which agreement, the first and last time, and how many times. If someone taps “The code doesn't work”, we store who, which agreement and when. Legal basis: performance of a contract, point (b), for the account and showing the code, and legitimate interest in correcting errors, preventing misuse and keeping the Service stable, point (f), for the code log and the reports.

Work email for members without a company: you can add the email address you have at work. We send a code there to confirm that the address is yours, and store the address, a hash of the code, whether the address is confirmed and when. Free email addresses cannot be used. If your workplace has verified the domain in the Service, you become an employee or member there, and the workplace sees you as it sees other employees or members. Before that, nobody at the workplace sees that you have confirmed the address. In the Service, the operations team sees only the number of confirmed addresses per domain, never names or addresses, and uses the number to judge where we should find new agreements. If you have confirmed an address, you see how many others on the same domain have confirmed an address or have an account there, but only when there are at least five, and never who. Legal basis: consent, point (a), given by adding and confirming the address yourself. You withdraw consent by removing the address.

Sign-in security: when a sign-in fails, for example because of a wrong code, an expired link or a passkey that does not match, we store which sign-in method it was, the account when we know which one, the time and a cryptographic hash (HMAC) of the IP address, not the address itself. This is used only to count attempts in the last 15 minutes. If there are many failed attempts against the same account or from the same IP address, and when someone in Avtalor's operations team starts a customer view or creates an API key or an access for AI assistants for an operations account, we store a security alert with what happened, when, the email address of the account concerned and of the person who performed the action, and, for many attempts from the same IP address, also the IP address. The alert is emailed to Avtalor's operations team, except for a customer view, where it is only stored. Only the operations team sees the alerts. Legal basis: legitimate interest in detecting and stopping unauthorised access to accounts and to the Service, point (f).

Invitations from Avtalor: when we invite a potential supplier to Avtalor Specials, we measure whether the email has been opened and whether the link in it has been opened in a browser. We store when the invitation was sent, the first and last time it was opened and the link visited, and how many times, linked to the business we invited. Opening is measured with a small image in the email, without cookies and without storing the IP address, and is not always accurate, because some email programs fetch images themselves and others block them. Only Avtalor's operations team sees the figures. Legal basis: legitimate interest in following up the invitations we send, point (f). The recipient can unsubscribe with the link in the email and will then receive no further invitations.

What the supplier can see

For employees, a Supplier by default receives only aggregated figures and pseudonymised identifiers, without names or emails.

Names and contact details of employees are shared with a Supplier only when two conditions are met at the same time: the Company has enabled sharing, and the employee has given separate, explicit consent.

Consent is voluntary, can be limited per supplier, and can be withdrawn at any time in the Service under Settings. Withdrawal does not affect the lawfulness of processing carried out before withdrawal.

If the Company chooses to share contact details without the employee's consent, the Company must itself have an independent legal basis and bears responsibility for it.

The Company's administrators are the contact persons for the Company's agreements. As long as the Company has not turned off contact from Suppliers, every Supplier sees the administrators' names and a masked email address when sending an offer, and can send them offers. Regardless of that setting, Suppliers the Company has an agreement with also see job title, full email address, phone and profile photo, and can send them messages about the agreements. If the Company has only sent a request, the Supplier receives all administrators' names and full email addresses, and what the administrator entered in the request. An administrator can turn off email from suppliers in Settings, or unsubscribe from a single supplier using the link in the email. This stops mailings, but not offers, the contact card on the agreement or messages about the agreement itself. Legal basis: performance of the contract with the Company, GDPR Article 6(1)(b), and the Company's legitimate interest in administering the agreements, Article 6(1)(f).

For open agreements in Avtalor Specials, the Supplier never learns who has seen or retrieved the code. The Supplier sees how many have reported “The code doesn't work” and when the latest report came, never who reported. We share no personal data about members without a company with the Supplier.

Automated decisions

Machine reading is used to suggest content in agreement cards and to provide tips and rankings for administrators and suppliers. The processing does not involve automated decisions with legal effect or similarly significant effect on individuals, cf. Article 22.

All suggestions require human review before publishing. Data is not used to train general-purpose models.

Sub-processors

Avtalor uses sub-processors for hosting, database storage, email delivery, notifications, error monitoring and machine reading of documents. All are bound by a data processing agreement with obligations at least equivalent to those in this policy.

AI calls go through Vercel AI Gateway to Anthropic under a zero data retention agreement: the content is not stored by them after the answer is created, and is not used to train models. If Anthropic is unavailable, the gateway may send the call to the same Claude model at Amazon Web Services (Amazon Bedrock) or Google Cloud (Vertex AI). Zero data retention applies there too, and the content is not used to train models.

The AI assistants a user connects (Claude, ChatGPT, Copilot or others) are not sub-processors for Avtalor. The user or the employer chooses them, and agreement content is sent there only when the user asks the assistant for it.

Feedback and Avtalor Specials use the same sub-processors as the rest of the Service, for the database and sending email, and no new ones. The preselected appearance is worked out in the browser, and the first name is not sent to anyone for this purpose.

Processing takes place within the EU/EEA where possible. For transfers to third countries, the European Commission's standard contractual clauses are used with supplementary measures.

An up-to-date list of sub-processors is available on request to support@avtalor.com. The Company is notified at least 30 days before new sub-processors are engaged and may object in writing.

Security

Data is transmitted encrypted with TLS and stored encrypted. Access to production data is limited to named personnel with a business need, is logged and requires two-factor authentication.

Access control is enforced in the database, so that a user can technically only read data they are entitled to. Actions performed by Avtalor personnel on behalf of a customer are logged.

In the event of a personal data breach, the Company is notified without undue delay and no later than 48 hours after the breach was discovered, with available information about scope, consequences and measures taken.

Retention

Usage data is retained for 24 months and then deleted. The same applies to email delivery status and views of tips. Information about AI calls (number of tokens, cost and status) is retained for 60 months, because it can be the basis for invoicing AI usage and must be kept under the Norwegian Bookkeeping Act.

The sign-in log is retained for two years. The log of sign-ins with the account Apple uses for App Review, which holds only time, outcome and pseudonymised values, is deleted after 90 days. Content sent to the AI features is not stored; consent to the agent is stored until the user withdraws it or the account is deleted.

Account data is deleted within 30 days after the portal is closed or access lapses. Data in accounting records is retained for five years after the end of the financial year, as required by the Norwegian Bookkeeping Act.

Uploaded documents are deleted once the agreement card is published, and at the latest after 12 months.

An agreement that has been signed or approved, with signatures, IP addresses, browser data and the event log, is retained for as long as the agreement applies and for five years after it ended, so that what the parties agreed can be documented. It is kept even if a user who signed deletes their account; the name and signature then appear only in the signed document.

An offer that was never signed or approved (declined, withdrawn or expired) is deleted with its attachments 12 months after the last event. Uploaded attachments that were never added to an offer are deleted after one day.

A signature saved on the account is deleted when the user deletes it or the account.

Access for an AI assistant is deleted 12 months after it was withdrawn or expired. The measurement of usage is retained for 24 months, like other usage data.

The theme you have chosen is stored on the account for as long as the account exists.

Feedback that has been completed or declined is deleted 12 months after it was handled. Feedback that is new or under review is deleted 18 months after it was sent. Feedback that has been added to the plan is kept until the matter is closed. All feedback is deleted when the account is deleted.

The code log for open agreements is deleted 12 months after the code was last retrieved, and reports that a code does not work 12 months after they were sent. This applies to everyone who has retrieved an open code, including employees and members of a Company. If the account is deleted, the code log and the work email addresses are deleted with it, and the reports lose their link to the person.

On the Company's instruction, Avtalor deletes or returns personal data on termination of the agreement.

The count of failed sign-ins is deleted after one day. Security alerts, including the email addresses and any IP address in them, are deleted 90 days after the alert was sent.

The measurement of opens and clicks on invitations from Avtalor is retained for 24 months after the invitation was sent, and then deleted.

Data subject rights

Employees have the right of access, rectification, erasure, restriction of processing, data portability, and to object to processing based on legitimate interest.

The right to erasure does not apply to a signed agreement for as long as it must be kept to document the contractual relationship, see GDPR Article 17(3)(e).

Requests are directed to the Company as controller. Avtalor assists the Company in meeting the request within a reasonable time, normally within 14 days.

Members without a company direct their requests straight to Avtalor as controller, at support@avtalor.com. Anyone who has sent feedback can at any time ask for access to it or deletion of it, or withdraw their yes to us contacting them about it, at the same address.

A data subject may lodge a complaint with the Norwegian Data Protection Authority, PO Box 458 Sentrum, 0105 Oslo.

Cookies

Necessary cookies are used for sign-in, session and security. These cannot be switched off without the Service ceasing to work.

Statistics and marketing require consent and can be switched off in the Service under Cookie preferences. Marketing cookies are used only on avtalor.com, never inside company portals. No third party sets statistics or marketing cookies for us.

Privacy | Avtalor