Privacy Policy
Last updated: 2026-11-15
This privacy policy explains how Government Procurement Group Oy ("Viran", "we") processes personal data when you visit viran.ai, contact us, use the customer portal app.viran.ai, or are named in material we process in our services Viran Bid Team and Viran Review. It also explains your rights and how to use them.
Version 4.0 · Effective from 15 November 2026
1. Controller and contact
Government Procurement Group Oy, Business ID 3636107-8, Kampinkuja 3, 00100 Helsinki, Finland, is the controller for the processing described in this policy, unless a section states otherwise. Contact for all privacy matters: iivo.angerpuro@viran.ai.
Where we process personal data on behalf of a customer, the customer is the controller and we are its processor. Sections 6 and 9 explain when this is the case.
2. Cookies
The website and the customer portal use cookies and similar browser storage. Analytics is used only if you accept it in the cookie banner, and you can change your choice at any time in the cookie settings. The cookie policy describes each cookie and how long it is kept.
3. Website visitors
Personal data. Only with your consent:
- usage data, such as page views, clicks, errors and browser type;
- recordings of visits (session recordings) and heatmaps, which combine clicks and scrolling from many visits.
Text typed into form fields is not recorded, and IP addresses are not stored.
Purpose. To understand how visitors use the website and to improve it.
Legal basis. Consent (GDPR Article 6(1)(a)). You can withdraw your consent at any time in the cookie settings.
4. Contact requests and demo bookings
Personal data.
- Contact form: name, email address, organisation, role and message.
- Demo booking: name, email address and the time of the meeting.
Purpose. To answer your request, arrange and hold a meeting, start a customer relationship, and send you information about our services that is relevant to your organisation.
Legal basis. Steps taken at your request before entering into a contract (GDPR Article 6(1)(b)). Information about our services: legitimate interest in business-to-business marketing (Article 6(1)(f)). You can opt out of marketing at any time.
5. Customers and their contact persons
This section covers the contact persons of our Viran Bid Team and Viran Review customers.
Personal data.
- Contact persons and delivery recipients: name, contact details, role and notes.
- Our records: meeting notes, contracts, follow-up actions and a record of each delivery.
- For customers who use Hailer: the cards and discussions in their Hailer workspace, including users' names.
- Billing records.
Purpose. To manage the customer relationship, deliver the service through the customer portal, email or the customer's Hailer workspace, bill for it and communicate with the customer.
Legal basis. Legitimate interest in managing the customer relationship and delivering the service (GDPR Article 6(1)(f)). Where the contact person is personally our customer: contract (Article 6(1)(b)). Billing records: legal obligation under the Accounting Act (Article 6(1)(c)).
6. Viran Bid Team: customer material
A Viran Bid Team customer gives us material such as its company profile, company documents, references, pricing and bid material. This material can contain personal data, such as the names of the customer's reference contacts, and material protected by subcontractors' intellectual property rights.
We use this material to assess whether public tenders fit the customer, to produce the weekly briefing and client reports, to deliver results, to prepare bid documents and to simulate pricing.
For this material, the customer is the controller and we are its processor. We process it only on the customer's instructions, under our Data Processing Agreement or a data processing agreement signed with the customer (GDPR Article 28). The customer determines the legal basis. Questions about this processing should be directed to the customer.
7. Public procurement documents
Viran Bid Team collects tender notices, tender documents and procurement decisions from public sources and tender portals.
Personal data. The names and contact details of buyer officials and other persons named in these documents. An assessment that quotes such a passage shows them. To retrieve tender documents, we register accounts on tender portals in the customer's name, and a registration may name a contact person at the customer.
Purpose. To analyse public tenders for our customers. We do not aim to process the personal data in these documents; our purpose is to give customers access to information about public procurement.
Legal basis. Legitimate interest in analysing public tenders for our customers (GDPR Article 6(1)(f)).
8. Customer portal app.viran.ai
This section covers the employees of Viran Bid Team customers who use the customer portal. We are the controller for the data below. For customer material shown in the portal, see section 6.
Personal data.
- Account: name, email address, the companies the user belongs to and role.
- Sign-in and security: one-time sign-in codes (stored only in hashed form), session details, IP address and browser details.
- Activity: sign-ins, case opens, changes to case handling, feedback, help requests and replies, document downloads and membership changes.
- Emails: the recipient's address and the message. Feedback and help requests are emailed to the Viran employee responsible for the customer.
- Only with consent: usage data such as page views, clicks and errors, linked to the user's name, email address and company. Analytics does not store IP addresses, and the portal does not record sessions.
Answers to profile questions become part of the company profile, which we process as the customer's processor (section 6).
Source. The customer company gives us the user's name and email address, and Viran staff create the account. All other data comes from the user's own use of the portal. Signing in requires an email address the customer company has approved; there is no other requirement to provide data.
Purpose. To give the customer's employees access to their company's tender assessments (cases); to sign users in and keep accounts secure; to show unread marks and show Viran staff who has opened a case; to record case handling (status, owner and reason for dropping); to handle feedback, help requests and replies; to send sign-in codes and case notifications by email; to investigate misuse and errors; and, only with consent, to measure how the portal is used.
Legal basis. Legitimate interest (GDPR Article 6(1)(f)) in delivering the service the user's employer has bought, keeping the portal secure and being able to show who did what. We do not rely on contract, because the user is not a party to our contract with their employer; if the user is personally our customer, the basis is contract (Article 6(1)(b)). Analytics: consent (Article 6(1)(a), and section 205 of the Act on Electronic Communications Services (917/2014) for storage in the browser). Consent can be withdrawn at any time under "Cookie settings" in the account menu or at the foot of the sign-in page.
9. Viran Review
Viran Review checks the procurement documents a contracting authority uploads to the service at gov.viran.ai. It checks that the documents are consistent with each other, checks pricing and formulas in price forms and CPV codes, and points out legal risks with references to public decisions of the Market Court and the Supreme Administrative Court. The review is done by AI models processed only in the EU, and the provider does not use the requests to train models. Findings concern documents, not individuals, and are advisory: the contracting authority's staff decide what to do with them.
Our role. For the review material (the documents the authority uploads and everything the service produces from them), the contracting authority is the controller and we are its processor, under the engagement terms (GDPR Article 28). The authority determines the legal basis. We are the controller for user accounts, sign-in and server logs.
Personal data.
- Review material: the uploaded documents and any personal data in them, such as officials' names and contact details, and the findings with quotes and screenshots, users' decisions, comments and questions, and the answers.
- User accounts and sign-in: email address, one-time sign-in codes and sign-in cookies.
- Server logs, which can contain parts of the review material.
Source. The contracting authority uploads the documents and names its users, and Viran creates their accounts. The service does not use analytics.
Purpose and legal basis for our own processing. User accounts, sign-in and server logs: legitimate interest in delivering the service the contracting authority has ordered and keeping it secure (GDPR Article 6(1)(f)).
10. Automated assessments
We use AI models to find public tenders that may fit a customer company and to assess how well each tender fits. The models read the public tender details and tender documents and compare them with the company profile. Fixed rules in our code then turn the result into a verdict: excellent, good, moderate or poor. Some of this processing takes place outside the EU, including in the United States (see section 11).
The assessments concern companies and tenders, not individuals. No decision with legal or similarly significant effects on a person is based on them (GDPR Article 22).
An assessment appears in the customer portal as soon as it is ready, even before staff have marked it reviewed. Notification emails and formal deliveries are sent only after a Viran employee has marked the assessment as reviewed, and staff can hide a case afterwards. Assessments are advisory and can contain errors, so check them against the original tender documents.
We do not use customer material to train or fine-tune AI models, and our AI providers do not use it for training under their terms.
11. Recipients and transfers outside the EU/EEA
We use service providers for hosting, email, AI processing and other parts of our services. Each provider that processes personal data on our behalf is bound by data processing terms (GDPR Article 28). The current list, with each provider's service, location and transfer mechanism, is on our service providers page.
The customer portal and its data are on our server in Helsinki, and Viran Review and its data are in the EU. Some providers process data outside the EU/EEA, mainly in the United States. For a provider certified under the EU-US Data Privacy Framework, the transfer relies on the European Commission's adequacy decision for that framework, and for Switzerland on the Commission's adequacy decision for Switzerland. Otherwise, and as a fallback, we use the Commission's Standard Contractual Clauses. You can request a copy of the safeguards from iivo.angerpuro@viran.ai.
We may also disclose personal data where the law or an order of an authority requires it, or where it is needed to establish, exercise or defend legal claims. If our business or part of it is transferred to a new owner, personal data can be transferred with it, and the new owner must continue to protect it as this policy describes.
12. Retention
We keep personal data only as long as the purpose requires. The periods are:
| Data | How long we keep it |
|---|---|
| Contact requests | 24 months from the last contact. |
| Demo bookings | 12 months. |
| Website and portal analytics | Up to 7 years, so that use can be compared over the years, or until you ask us to delete it. Withdrawing consent stops collection. |
| Website session recordings | 30 days. |
| Customer contact persons, customer records and delivery records | For the customer relationship plus 3 years, the general limitation period (section 4 of the Act on the Statute of Limitations of Debts, 728/2003), so that we can establish and defend legal claims. |
| Billing and accounting material | As long as the Accounting Act (1336/1997) requires. |
| Viran Bid Team customer material and the assessments made from it | For the term of the customer agreement. We delete it within 30 days after the agreement ends, unless the agreement says otherwise. |
| Public procurement documents and the facts extracted from them | 5 years after the tender deadline, so that we can show what an assessment was based on. |
| Portal sign-in codes | 5 minutes. |
| Portal sessions | 30 days from the last renewal. Deleted at once on sign-out or a change in access. |
| Portal accounts | While the membership is active and 3 years after it ends, for the reason given for customer records. |
| Portal activity, case handling, feedback, help requests and notification emails | For the customer relationship plus 3 years, for the reason given for customer records. |
| Portal server logs | Up to 14 days, to find and fix faults. They contain no customer content. |
| Viran Review material, user accounts and server logs | While the engagement with the contracting authority continues. We delete them when the authority asks, or as agreed in the engagement. Database backups are kept for one day. |
| Backups | Up to 30 days. Deleted data disappears from backups as they rotate. |
13. Security
We protect personal data with technical and organisational measures that fit the risk. They include encrypted connections, sign-in with one-time codes, access control so that users see only the data they are entitled to, staff access limited to those who need it, logging and monitoring, and regular backups. A security description is available to customers on request.
14. Legitimate interests
Where this policy names legitimate interest as the legal basis, we have weighed our interest against your interests, rights and freedoms, and concluded that the processing is justified. You can ask us for the balancing test.
15. Your rights
Under the GDPR, you have the following rights:
| Right | What it means |
|---|---|
| Access (Article 15) | You can ask whether we process your personal data and receive a copy of it. |
| Rectification (Article 16) | You can have inaccurate data corrected and incomplete data completed. |
| Erasure (Article 17) | You can have your data deleted where there is no longer a legal reason to keep it. |
| Restriction (Article 18) | You can ask us to restrict processing, for example while we check whether your data is accurate. |
| Data portability (Article 20) | Where processing is based on consent or contract, you can receive your data in a machine-readable format or have it transferred to another controller. |
| Objection (Article 21) | You can object to processing based on legitimate interest, and to direct marketing at any time (section 16). |
| Withdrawal of consent (Article 7(3)) | You can withdraw consent at any time. This does not affect processing before the withdrawal. |
| Complaint (Article 77) | You can lodge a complaint with the Data Protection Ombudsman (section 17). |
To use your rights, contact iivo.angerpuro@viran.ai. We may ask you to confirm your identity. We answer within one month; for a complex request we can extend this by up to two months, and we tell you within the first month. Where we process data as a processor for a customer, we forward the request to that customer and help it answer.
16. Right to object
Where we process your data on the basis of legitimate interest, you can object at any time on grounds relating to your particular situation. We then stop, unless we show compelling legitimate grounds that override your interests, rights and freedoms, or need the data to establish, exercise or defend legal claims. You can object to direct marketing at any time, and we then stop using your data for it. Send your objection to iivo.angerpuro@viran.ai.
17. Supervisory authority
Data Protection Ombudsman (Tietosuojavaltuutettu), Lintulahdenkuja 4, 00530 Helsinki, Finland, tietosuoja.fi.
18. Changes to this policy
If we make a material change, we tell portal users and customers' contact persons by email before it takes effect. The version number and date at the top show the current version, and the change log below lists earlier changes.
Change log
| Version | Date | Change |
|---|---|---|
| 4.0 | 15 November 2026 | Restructured by activity, with a retention table, a rights table and a separate service providers page. Disclosure of personal data where the law requires it and on a transfer of the business added. No change in how we process personal data. |
| 3.2 | 15 November 2026 | Shortened and simplified. No change in how we process personal data. |
| 3.1 | 15 November 2026 | Viran Review section updated to describe the current service. |
| 3.0 | 15 November 2026 | Customer portal app.viran.ai added as its own section, including the source of users' data. Automated assessments described. Legal basis stated for each purpose; legitimate interest replaces contract for customers' employees. Processor list updated, with each provider's legal entity and transfer basis. Session recordings and heatmaps on viran.ai described. Inaccurate statements corrected. Retention period and its reason stated for each type of data. Bid Team deletion period corrected to 30 days. Right to object, withdrawal of consent and notice of changes added. |
| 2.2 | 16 May 2026 | Website hosting (Vercel) moved to the EU region (Frankfurt) under the Vercel Pro plan. GitHub, Inc. added to the subprocessor list for version-controlled storage of project material. |
| 2.0 | 17 April 2026 | Three service-lane structure (website, Bid Team, Review). Subprocessor list refreshed and expanded. DPA and security documentation practices added. |