Where is My Data Stored?
Where VULK stores conversations, project files and media, and how storage differs from CDN delivery and AI processing.
Where is My Data Stored?
Configuration checked: 19 September 2026.
VULK uses different services for its database, file storage, application servers and content delivery. Each service has its own location, listed below.
Storage locations
| Data or service | Provider | Current location or configuration |
|---|---|---|
| Main database, including account records, Studio conversations and stored project source | AWS RDS PostgreSQL | Frankfurt, Germany (eu-central-1); encrypted at rest |
| Uploaded images and other media stored as files in the Studio media store | Cloudflare R2 | Cloudflare reports Western Europe (WEUR); the bucket uses the default jurisdiction |
| Separate project-file storage, including mobile build artifacts | Cloudflare R2 | Cloudflare reports Eastern Europe (EEUR); the bucket uses the default jurisdiction |
| Automated backups of the main RDS database | AWS RDS | Regional backups with a configured retention of 30 days |
| Application servers inspected for this configuration | Hetzner | Falkenstein, Germany |
| PostgreSQL service for VULK-managed application backends | Hetzner-hosted backend service | Falkenstein, Germany; separate from the main VULK database on AWS RDS |
| Help center and self-hosted support inbox, including its local database and attachment storage | Hetzner, with Chatwoot operated by VULK | Helsinki, Finland; separate from the Studio database and generated-application backends |
Text attachments that are incorporated into a Studio conversation are stored as message content in the main database. Images and other media stored as files follow the R2 storage path. Project content can also be copied into preview, build or publishing environments when those features are used.
Data in applications you create
The main VULK database stores builder conversations and project source. The managed backend of a generated application uses a separate PostgreSQL service, listed in the table above. The location and 30-day automated backup setting described for the main RDS database apply to the main RDS database.
An external backend or integration selected for an application has its own storage and processing scope. Publishing the application through Cloudflare serves the application from Cloudflare, while its database stays with the backend that hosts it.
What the R2 location means
Cloudflare's regional location and its jurisdiction restriction are separate settings. Our R2 buckets are located in Europe — Western Europe (WEUR) for the Studio media store and Eastern Europe (EEUR) for project files — and use the default jurisdiction, as listed in the table above.
Cloudflare describes these settings in its R2 data location documentation.
CDN delivery and publication
Cloudflare also delivers content through its global network. Media served through the CDN and published applications have a delivery path separate from the underlying database or object store: they are delivered from Cloudflare locations worldwide, close to each visitor.
AI processing
AI features send the input needed for a request to the services used for that feature. This can include prompts, relevant project files and attached media. Each of those services processes requests in its own region, independently of the storage region.
When the assistant uses the backend inspection tool, a limited sample of application records can also be included in the model request. The tool masks values in columns identified as credentials, such as passwords and tokens; other fields, including any personal data they hold, are sent as stored.
Support conversations
The chat in this help center is a support conversation, separate from project-building conversations in the Studio. Support messages are stored in the support inbox listed in the table above.
The help-center chat sends visitor messages to VULK's self-hosted Chatwoot inbox so the support team can follow up. The AI assistant processes the current message and relevant conversation history through OpenRouter. Escalation notifications can also send excerpts and contact or technical context to Telegram. These are separate processing paths, each with its own location; the support inbox itself is hosted in Finland.
The widget sends the visitor's message to the inbox separately from requesting the AI answer, so the AI answer and inbox delivery are two independent steps. The inbox receives the visitor's messages; the AI assistant's replies stay in the widget. The displayed conversation is held in the current widget state; a browser session identifier reconnects the visitor to the support inbox.
Starting a new chat clears the widget's current conversation state. Previously stored support conversations are deleted on request: contact [email protected].
Data protection enquiries
For institutional requirements, a data processing agreement (DPA/AVV), or a specific residency requirement, contact [email protected]. The agreed scope needs to cover the services and data involved in your use of VULK.
An agreement between VULK and your organization is its own document, separate from any supplier's DPA and from your subscription. Request it through [email protected], and the signed agreement sets which services and guarantees it covers.
See also our subprocessor and GDPR information and Privacy Policy.