Legal
Data Processing Agreement
This Data Processing Agreement ("DPA") forms part of the agreement between the business using Basilum ("Customer") and Vaisor ApS ("Processor"). It applies automatically where Vaisor ApS processes personal data on the Customer's behalf through Basilum.
Version 1.0 · 6 October 2026
01
Parties and scope
The Customer is the data controller and Vaisor ApS, CVR 46710495, Denmark, is the data processor. This DPA governs processing carried out to provide Basilum and supplements the Terms of Service. If this DPA conflicts with the Terms on data protection, this DPA prevails.
02
Customer instructions
The Processor will process personal data only on documented instructions from the Customer, including instructions given through the Customer's use and configuration of Basilum, support requests and this DPA, unless EU or Member State law requires otherwise. In that case, the Processor will inform the Customer before processing unless the law prohibits that notice.
The Processor will promptly inform the Customer if, in its opinion, an instruction infringes applicable data protection law. The Customer is responsible for the lawfulness, accuracy and transparency of the personal data and instructions it provides.
03
Details of the processing
- Subject: providing the Basilum AI marketing service, integrations, storage, support and related security.
- Duration: for the term of the Customer's account and the deletion period described below.
- Nature and purpose: collecting, hosting, organising, retrieving, analysing, generating, transmitting and deleting data as necessary to operate Basilum and follow the Customer's instructions.
- Data subjects: the Customer's users and personnel; contacts, customers and website users represented in connected services or Customer content; and individuals appearing in public website material selected by the Customer.
- Data categories: names, business contact details, account identifiers, website and business content, Google Analytics and Search Console data, WordPress content, technical and usage logs, instructions, prompts and generated work.
Basilum is not intended for special-category data, criminal-offence data, national identification numbers, payment-card data or other highly sensitive personal data. The Customer must not submit such data unless expressly agreed in writing.
04
Confidentiality
The Processor ensures that persons authorised to process personal data are bound by confidentiality obligations and receive access only where needed to provide and secure the service.
05
Security
Taking account of the state of the art, implementation costs and processing risks, the Processor will maintain appropriate technical and organisational measures, including:
- encryption in transit and encryption at rest where supported by the platform;
- authentication, role-based access and least-privilege access controls;
- tenant-level access controls and separation of Customer workspaces;
- logging, monitoring, backups and recovery measures appropriate to the service;
- secure development, dependency maintenance and vulnerability remediation; and
- procedures for security incidents, access changes and deletion requests.
06
Personal data breaches
The Processor will notify the Customer without undue delay after becoming aware of a personal data breach affecting Customer personal data. The notice will include, as information becomes available, the nature of the breach, likely consequences, measures taken or proposed, and a contact point. The Processor will take reasonable steps to contain and remediate the breach and assist the Customer with its notification duties.
07
Assistance
Taking account of the nature of the processing and information available, the Processor will reasonably assist the Customer with data-subject requests, security, breach notifications, data protection impact assessments and consultations with supervisory authorities. If a data subject contacts the Processor directly about Customer data, the Processor will direct the request to the Customer unless legally required to respond.
08
Sub-processors
The Customer gives general written authorisation for the Processor to use sub-processors. The Processor remains responsible for their performance of equivalent data protection obligations and will give at least 30 days' notice before adding or replacing a sub-processor that materially processes Customer personal data.
The Customer may object on reasonable data protection grounds during that notice period. The parties will work in good faith on a solution; if none is reasonably available, the Customer may stop the affected processing or terminate the affected service before the change takes effect.
| Provider | Purpose | Data involved |
|---|---|---|
| Lovable | Application hosting, managed cloud and AI gateway | Account, workspace, prompts and service data |
| Supabase | Database, authentication and storage infrastructure | Account, workspace and generated content |
| Google (Gemini) | AI model processing through the Lovable AI Gateway | Selected website content, prompts and generated output |
Google, WordPress and similar services connected by the Customer may also act as the Customer's own providers. They are sub-processors only to the extent Vaisor engages them to process personal data on the Customer's behalf.
09
International transfers
Where personal data is transferred outside the EU/EEA to a country without an adequacy decision, the Processor will ensure an appropriate transfer mechanism, such as the European Commission's Standard Contractual Clauses, together with supplementary safeguards where required.
10
Deletion and return
During the subscription, the Customer may request export or deletion where supported by the service. After termination, the Processor will delete or return Customer personal data on request and delete remaining copies within 90 days, unless applicable law requires retention. Data in protected backups may remain until overwritten in the ordinary backup cycle and will remain protected and unavailable for ordinary use.
11
Information and audits
The Processor will make available information reasonably necessary to demonstrate compliance with Article 28 GDPR. The Customer may conduct one audit per 12-month period on at least 30 days' notice, and additional audits following a material breach or where required by a supervisory authority. Audits must protect other customers, confidential information and service security, avoid unreasonable disruption and use available reports and remote documentation before an on-site inspection. Each party bears its own costs unless material non-compliance is found.
12
Liability, term and contact
This DPA begins when the Customer accepts the Terms or first uses processing covered by it and ends when the Processor has deleted the relevant personal data. Liability under this DPA is subject to the limitation of liability in the Terms, except where liability cannot lawfully be limited. Danish law and the dispute provisions in the Terms apply.
Data protection questions and notices may be sent to hello@basilum.com.