Eventro is a service provided by Finn AB (company registration no. 556859-7040), Klubbacken 18, 129 39 Hägersten, Sweden. In this policy, “Eventro”, “we” and “us” refer to Finn AB.
Our role
Eventro is a platform for career fair management and CRM used by organisations (“Customers”), such as student organisations.
Eventro as processor
When a Customer uses Eventro to manage its events, members, business contacts, sales and recruitment, the Customer is the data controller and Eventro is its data processor. We process that data only on the Customer’s instructions, under a Data Processing Agreement, and never for our own purposes.
If you have registered for an event or been contacted by an organisation using Eventro, please read that organisation’s privacy notice and contact them to exercise your rights.
Eventro as controller
Eventro is the data controller for data about people who use or buy Eventro itself, such as Customer staff with Eventro accounts, and for our own sales and support contacts.
Data we process on behalf of Customers
Depending on how the Customer uses Eventro, this may include:
- Contact details, such as name, email, phone, university and programme, or employer.
- Event registrations, attendance and preferences, such as food preferences.
- Membership, purchase and payment records.
- Email communications, including engagement with emails (opens and clicks), and emails synced from connected Gmail accounts.
- Job and programme applications, and notes made by the Customer’s staff.
The Customer decides what data is collected, why, and for how long it is kept.
Data we process as controller
| Data | Purpose | Legal basis |
|---|---|---|
| Account details (name, email, organisation and login data) | Providing the Eventro service to Customer staff | Performance of a contract |
| Usage and technical data, such as log, error and analytics data | Keeping Eventro secure, fixing errors and improving the service | Legitimate interest |
| Contact details and correspondence with Customers and prospects | Sales, support and invoicing | Legitimate interest; legal obligation for accounting records |
Service providers
We use the following service providers to run Eventro. They process personal data only on our instructions.
| Provider | Purpose | Location |
|---|---|---|
| Amazon Web Services (AWS) | Hosting and database storage | EU (eu-north-1, Stockholm) |
| Cloudflare | Network proxy and security; AI infrastructure for the Eventro Slack assistant | Global |
| Sentry | Error monitoring | EU region (Germany) |
| PostHog | Product analytics | EU region (Frankfurt, Germany) |
| OpenRouter | Routing requests to AI language models for the Eventro Slack assistant | Global infrastructure, including the United States. Eventro’s current integration is not EU-restricted; EU-only processing requires OpenRouter’s dedicated EU endpoint. |
| Resend | Sending emails from Eventro | United States; the email sending region may vary |
We will inform Customers before adding or replacing a subprocessor, giving them the opportunity to object.
Where a provider processes data outside the EU/EEA, we rely on appropriate safeguards such as the EU Standard Contractual Clauses or the EU–US Data Privacy Framework.
We do not sell personal data, and data belonging to one Customer is never shared with another Customer. We may disclose data if required by law, or as part of a merger or acquisition, with notice to affected users.
Google user data
This section applies when a user connects a Gmail account to Eventro. Eventro processes this data on behalf of the Customer and the connecting user.
5.1 Google data we access
Eventro requests only the following Google OAuth scopes:
| Scope | What we use it for |
|---|---|
https://www.googleapis.com/auth/gmail.readonly | Read the Gmail profile, list and search threads, read message bodies and headers, and keep Eventro in sync with your mailbox using Gmail history. |
https://www.googleapis.com/auth/gmail.send | Send new emails and replies from Eventro on your behalf. Only granted to users whose organisation has given them permission to send email from Eventro. |
Users without sending permission are asked only for gmail.readonly. We do not request permission to modify, delete or label your email, or access any other Google service.
5.2 How we use Google data
We use Google user data only to provide and improve user-facing features in Eventro:
- Showing email conversations with contacts inside the CRM.
- Keeping those conversations in sync with Gmail.
- Sending emails and replies you choose to send from Eventro.
- Answering questions about your email through Eventro’s AI assistant, when you or your organisation use it.
- Detecting and fixing errors, and keeping the service secure.
What we never do
- Sell Google user data.
- Use or transfer it for advertising, including personalised, retargeted or interest-based ads.
- Use it to determine creditworthiness or for lending purposes.
- Use it to develop, improve or train generalised AI or machine-learning models.
- Allow humans to read it, except with your explicit consent for specific messages; when needed for security purposes such as investigating abuse; to comply with applicable law; or after the data has been aggregated and anonymised for internal operations.
5.3 What we store
Stored in our database
- Email bodies in HTML and plain text
- Selected headers, including sender, recipients, subject and date
- Gmail message and thread IDs
- Sender and recipient email addresses
- Synchronisation metadata, such as history IDs and sync status
- OAuth access and refresh tokens, stored with an additional layer of encryption
Not stored
- Gmail labels
- File attachments
These may be processed in memory while syncing but are not saved.
5.4 Who can access Google data
Google user data is accessible only to Finn AB and the service providers below:
| Provider | Google data involved |
|---|---|
| Amazon Web Services (AWS) | All stored data listed in section 5.3 |
| Cloudflare | Data in transit; content included in AI assistant requests |
| OpenRouter | Email content included in AI assistant requests |
| Sentry | Limited email data that may be included in error reports |
| PostHog | Limited email data that may be included in usage events |
Our AI providers are not allowed to use Google user data to train AI models.
Your AI client and Eventro’s MCP server
If you connect your own AI client to Eventro’s Model Context Protocol (MCP) server, Eventro sends the data you request to that client. You or your organisation choose and control the client and its provider under their own terms. Eventro does not send Google data to any AI provider through MCP on its own.
5.5 Retention and deletion of Google data
We keep Google user data so that email history stays available in the CRM. To delete it, email us or close your organisation’s Eventro account.
Synchronisation stops. Previously synced threads and messages remain until you email us to request deletion.
Synchronisation stops and Eventro can no longer access Gmail. Previously synced data remains until you email us to request deletion.
Email support@eventro.se and we will delete your Google user data within 30 days. This works whether or not Gmail is still connected, and organisation administrators can request it for users who have left. We may confirm the request with your organisation first.
All associated Google user data is deleted within 30 days.
You can revoke Eventro’s access in your Google Account. Detailed deletion instructions are available at eventro.se/articles/delete-your-data.
5.6 Google API Services User Data Policy
Eventro’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Security
Data is encrypted in transit using TLS and stored encrypted at rest. Access to personal data is limited to personnel who need it, and they are bound by confidentiality.
Retention
- Customer data is kept according to the Customer’s instructions. When a Customer stops using Eventro, we delete its data within 30 days.
- Google user data is kept and deleted as described in section 5.5.
- Account data is kept while the account is active and deleted when it is no longer needed after the account is closed, unless applicable law requires longer retention.
- Accounting records are kept for 7 years, as required by Swedish law.
Deleted data may remain in encrypted backups for up to 30 days, after which it is permanently erased. Backups are not used for any other purpose.
Your rights
Under the GDPR, you have the right to access, correct, delete, restrict or object to processing of your personal data, and to data portability. You may also complain to the Swedish Authority for Privacy Protection (IMY) at imy.se.
If your request concerns data Eventro processes on behalf of a Customer, we may forward it to that Customer.
Contact
Finn ABKlubbacken 18129 39 Hägersten, Swedensupport@eventro.seChanges to this policy
We will update this page and change the “Last updated” date if we make changes, and notify Customers of material changes. If changes significantly affect how we use Google user data, we will notify users and ask for consent again where required.