Security and data
For the person who approves apps in your HubSpot account. Last updated 17 November 2026.
Access requested in HubSpot
- oauth
- Required by HubSpot for every app that installs through OAuth.
- crm.objects.companies.read
- Reads the company name, domain and postal code to search the registry, and the address fields so that filled values are left alone.
- crm.objects.companies.write
- Writes the
cbe_properties: the match status and the time of the check when the card opens on a company, and the registry data after someone confirms a company. Fills empty address, phone, website and year founded fields at that confirmation. - crm.schemas.companies.read
- Lists the company properties to see which BCE/KBO properties already exist, and reads how many custom properties the account may still create.
- crm.schemas.companies.write
- Creates the BCE/KBO property groups and properties (44, or 6 in compact mode) when you click Create the properties.
Tunnus has no access to contacts, deals, tickets, emails or files. It never deletes a record or a property.
What leaves your HubSpot account
Search terms only, sent to the registry service to find matching enterprises:
- the company name, automatically, when the card opens on a company that is not linked yet;
- what people type in the card's search: a company name, an enterprise or VAT number, or a postal code.
What Tunnus keeps
For each HubSpot account that installs it:
- the account id and domain, and the email and user id of the person who installed;
- the access and refresh tokens HubSpot issues, encrypted;
- the dates each setup step was completed;
- a counter of today's registry requests.
Company records and registry data are not stored by Tunnus. They go straight into your HubSpot account.
HubSpot adds the email and user id of the person using the card to each request it sends. Tunnus does not store them, but the hosting provider's request logs can keep them for a short time.
Technical measures
- Every request from the card is signed by HubSpot. Tunnus checks the signature and rejects requests older than five minutes.
- Tokens are encrypted at rest with AES-256-GCM. HubSpot access tokens expire after 30 minutes.
- All traffic uses HTTPS. The app and its token store run in Frankfurt.
- Each account can make 300 registry requests a day, so one account cannot use up the service for the others.
- The install, setup and data deletion pages run on the app's own address, separate from the sisurevops.com website.
Sub-processors
- Vercel
- Hosting of the app, Frankfurt region.
- Upstash
- Token store, Frankfurt region.
- CBEAPI
- Registry lookups. Receives the search terms.
Report a concern
Write to andrea@sisurevops.com.
Remove everything
- On the setup page, click Delete my data. The tokens, the setup progress and the request counters are erased.
- In HubSpot, open Settings, Integrations, Connected Apps, and uninstall Tunnus.
The BCE/KBO properties and their values stay in your HubSpot account. They are yours to keep or delete.