Data residency
Where your data lives
Vinktar runs on UpCloud in Helsinki, Finland. There is one region, and you cannot choose another.
What broke today?
Ask about your errors and your users. The answer comes from your own data in Vinktar.
Region
Helsinki, Finland
Hosting
UpCloud
Regions to choose from
One
Model providers
None
Checked 2026-10-05.
Storage
What is stored where
The application, the background worker and the event warehouse run on UpCloud. The database is UpCloud’s managed PostgreSQL in the same region.
| Data | Stored in | Location |
|---|---|---|
| Events and errors | ClickHouse, the event warehouse | UpCloud, Helsinki |
| Accounts, workspaces, projects, boards, alerts, event definitions and error-issue metadata | PostgreSQL, managed by UpCloud | UpCloud, Helsinki |
| Caches and rate-limit counters, nothing that outlives them | Valkey | UpCloud, Helsinki |
Backups
What is backed up
The database
UpCloud keeps its own snapshots of the managed PostgreSQL database.
Events and errors
No backup yetThese have no backup today. The warehouse holds the only copy.
Privacy
IP addresses and deletion
IP addresses
An end user’s IP address is reduced to a keyed, non-reversible hash before it is stored. The address itself is not written anywhere.
Deletion
Deleting a project or a workspace purges its events and errors from the warehouse. How long each plan keeps data
Third parties
Who else handles your data
| Company | What it handles |
|---|---|
| Stripe | Billing |
| Sign-in, if you choose it | |
| Resend |
The subprocessor list
Each of the three is on the subprocessor list, added before it first touches data.
Model providers
Vinktar runs no model, so no AI company is a subprocessor. What a coding agent reads goes to that agent’s provider, under your agreement with them. What a connected agent can reach