Legal

Privacy Policy

This document applies to enclava.io and related Enclava services.

PRIVACY POLICY

enclava.io

Effective date: 16 December 2026 (revised; supersedes the 6 November 2026 version)


1. Controller Identity and Contact Details

Enclava is a sole proprietorship (eenmanszaak) established under Dutch law, operated by:

  • Name: M Zulfa Achsani
  • Address: Bastenakenstraat 168, 1066 JG Amsterdam, The Netherlands
  • KVK number: 42072766
  • VAT identification number: NL005473661B29
  • Email: privacy@enclava.io
  • Website: https://enclava.io

Note: Enclava currently operates as a sole proprietorship (eenmanszaak). The sole proprietor bears unlimited personal liability for all data processing activities under the GDPR. Upon incorporation as a B.V. (besloten vennootschap), the legal entity of the controller will change to the B.V., the KVK registration number will be updated, and liability will generally be limited to the corporate entity. A revised version of this Privacy Policy will be published at that time.

2. Scope

This Privacy Policy applies to the processing of personal data of tenant staff members (i.e. employees, contractors, and authorised users of businesses that use the Enclava platform) for which Enclava acts as the data controller within the meaning of Article 4(7) GDPR.

Enclava also processes personal data of end-customers of tenant businesses in its capacity as a data processor on behalf of those businesses. That processing relationship is governed by a separate Data Processing Agreement between Enclava and each tenant. End-customers should refer to the privacy policy of the relevant tenant business for information about how their data is handled.

This Privacy Policy does not apply to individuals under the age of 16. The Enclava platform is a business-to-business (B2B) service and is not directed at children. If we become aware that we have collected personal data from a person under 16 without appropriate parental consent, we will take steps to delete that data promptly. The age threshold of 16 applies in the Netherlands pursuant to Article 5 of the Uitvoeringswet AVG (UAVG), implementing Article 8 GDPR.

3. Personal Data We Collect

When you create a tenant staff account on Enclava, we collect and process the following personal data:

Category Data Elements Source
Account data Full name, email address, phone number Provided directly by tenant staff member or tenant administrator
Authentication data Encrypted password hash, session tokens Generated during account creation and login
Usage data Login timestamps, IP addresses, actions performed within the platform Collected automatically during platform use
AI assistant data (only if your business has switched on Clava, the AI assistant) The requests you type to Clava, the plans it proposes, and which steps you approved or undid. Your name, role and schedule may also appear in a request typed, or a plan approved, by another user of your business Provided by you or by another user of your business; plans are generated by the assistant

In accordance with Article 13(2)(e) GDPR, the provision of account data (full name, email address, and, where applicable, phone number) is necessary to create and operate your tenant staff account and to perform the contract (the Enclava Terms of Service). This data is a requirement to enter into and perform that contract: without it, we cannot create your account or provide you with access to the platform.

4. Purposes and Legal Basis

Purpose Legal Basis (Art. 6(1) GDPR)
Providing and maintaining the Enclava platform and your tenant staff account Art. 6(1)(b) — performance of a contract (the Enclava Terms of Service)
Communicating with you about your account, service updates, and support requests Art. 6(1)(b) — performance of a contract
Ensuring security, monitoring for threats, and preventing fraud or misuse of the platform Art. 6(1)(f) — legitimate interest (security of the platform and protection of users). A Legitimate Interest Assessment has been conducted and is available on request.
Complying with applicable legal obligations (e.g. tax record retention under applicable fiscal law) Art. 6(1)(c) — compliance with a legal obligation
Providing Clava, the AI assistant, where your business's owner has switched it on: reading a request, looking up the business's schedule, and proposing a plan that a person reviews and approves Art. 6(1)(b), performance of a contract (the Enclava Terms of Service)
Platform performance and reliability monitoring Art. 6(1)(f) — legitimate interest (maintaining a reliable service). A Legitimate Interest Assessment has been conducted and is available on request.

4a. Automated Processing and AI

Enclava uses artificial intelligence (AI) technologies, including large language models (LLMs), to process inbound customer messages on behalf of tenant businesses and, where a business's owner switches it on, to run Clava, an AI assistant described below. Message processing extracts structured operational data (the items and quantities requested, a preferred date, and a delivery location) from free-text messages. Contact details are stripped before transmission and are not extracted.

Important clarifications regarding AI processing:

  • AI processing of end-customer messages is carried out by Enclava in its capacity as a data processor on behalf of tenant controllers. The legal basis for this processing is determined by each tenant controller.
  • AI-extracted data is always presented as a draft for human review. No quotes, work orders, invoices, or other operational decisions are made solely by AI.
  • Enclava does not engage in automated individual decision-making producing legal effects or similarly significant effects on data subjects within the meaning of Article 22 GDPR. All operational decisions require explicit approval by tenant staff.
  • Enclava does not use tenant or end-customer data to train or fine-tune AI models.

AI assistant for business owners and managers

Clava is an AI assistant inside the Enclava app. It is off by default, and only a business's owner can switch it on, in Settings. Once it is on, the owner and managers of that business can ask it, in their own words, to change the schedule (for example, to cover the jobs of a staff member who is off). Clava reads the request, looks up the jobs and people it needs, and proposes a plan of separate steps. Nothing changes until an owner or manager reviews the plan, ticks the steps they want and approves it; that person can undo an approved plan within 30 seconds. Clava never chooses a person for a job unless the person asking named them, and never sets a price.

  • What is sent to the AI model: the request as typed and the schedule data needed to answer it, limited to the days and people asked about: the jobs concerned (number, status, day, time window, assignee, service address and job notes), the names, roles and availability of the people concerned, and the names of the customers concerned. Job notes are sent as written, so they should not contain sensitive details either. Clava does not send premises access codes, photos, delivery signatures, or customers' phone numbers and email addresses, and it does not send the text of customers' messages.
  • Where it is processed: the model (GPT-6.1 terra, developed by OpenAI) runs on Amazon Bedrock, operated by Amazon Web Services, in the United States (see Section 6). AWS states that the model's developer has no access to the requests or the responses.
  • How long it is kept: Enclava deletes the text of a Clava conversation 7 days after its last message, and plans that were never approved after 30 days. An approved change is recorded in the job's history, like any other change, with the name of the person who approved it. Amazon Web Services does not store requests after answering them, except that it keeps a request its abuse-detection system flags for up to 30 days, in the US region that processed it.
  • Please do not type health information or other sensitive details into Clava. To say that someone is unavailable, "off" is enough; the reason is not needed.
  • Clava proposes and a person decides, so it does not make decisions based solely on automated processing within the meaning of Article 22 GDPR. Enclava does not use Clava requests or plans to train AI models.

For more information about the AI systems used, see the AI Transparency Disclosure in Section 14 of the Terms of Service.

5. Data Retention

We retain your personal data only for as long as necessary for the purposes set out in this Privacy Policy:

Data Category Retention Period
Tenant staff account data For the duration of the account. Data is deleted within 30 days of account deletion, unless retention is required by law.
Financial records and invoices 7 years from the end of the fiscal year in which the record was created, under Article 52 of the Dutch Algemene wet inzake rijksbelastingen (AWR) and, where Enclava is registered for tax in another country, any longer period that country requires (for example 10 years under Article 28(11) of Indonesia's UU KUP, or 7 years from the end of the tax period under Article 56 of UAE Federal Decree-Law No. 47 of 2022).
Usage data (logs) 12 months from the date of collection, unless a longer retention is necessary for security incident investigation.
Support communications For the duration of the account plus 12 months, or as long as necessary to resolve the inquiry.
AI assistant (Clava) data Conversation text: 7 days after the conversation's last message. Plans never approved: 30 days. Approved or undone changes: kept with the job's history for as long as that history is kept, with any free text cleared if the record is erased.

6. Recipients and Sub-processors

We share your personal data with the following categories of recipients, solely to the extent necessary for the purposes described in Section 4:

Recipient Purpose Location Safeguard
Supabase, Inc. Primary database and authentication (GoTrue) European Union (aws-1-eu-central-1) Personal data resides in the EU. DPA signed; Supabase's DPA incorporates EU Standard Contractual Clauses as a backstop for any access from outside the EEA.
Railway Corp. Application hosting (API and background worker) and application/runtime logs European Union (EU West) Personal data resides in the EU. DPA signed; incorporates EU Standard Contractual Clauses as a backstop.
Cloudflare, Inc. CDN, WAF, Access, Pages, and R2 object storage (tenant logos and uploaded files such as job photos) Global edge; R2 object storage in Cloudflare's automatic location, not pinned to the EU DPA in effect; R2 is a restricted transfer. For tenant-staff data (web traffic metadata via the CDN, WAF, and Access, where Enclava is the controller) the EU Standard Contractual Clauses apply as Module 2 covering any transfer outside the EEA; Cloudflare's storage of end-customer uploads in R2 is governed by the tenant Data Processing Agreement (Module 3).
Resend, Inc. Transactional email delivery (quotes, invoices, account notifications) United States EU-US restricted transfer covered by a DPA in effect, which incorporates EU Standard Contractual Clauses as the transfer basis.
Amazon Web Services EMEA SARL and Amazon Web Services, Inc. (Amazon Bedrock) Runs the AI model behind Clava, the AI assistant, for businesses whose owner has switched it on; processes the request typed by an owner or manager and the schedule data needed to answer it, including the names, roles, availability and jobs of the staff concerned United States (AWS regions us-east-1, us-east-2 and us-west-2) EU Standard Contractual Clauses (Module 2), incorporated into the AWS Data Processing Addendum, which forms part of the AWS Service Terms. Amazon.com, Inc.'s certification under the EU-US Data Privacy Framework covers Amazon Web Services, Inc. for non-HR data; Enclava does not rely on it as the primary basis. AWS does not store requests after answering them, except that requests flagged by its abuse-detection system are kept for up to 30 days in the US region that processed them. AWS states that the model's developer (OpenAI) has no access to requests or responses.
Expo Project, Inc. Delivery of push notifications to your mobile device; processes your device push token, and notification bodies that may contain an end-customer's name and service address United States No separate transfer instrument is in place and no transfer impact assessment has been carried out. This is an open gap, recorded here rather than omitted
Functional Software, Inc. (Sentry) Application error monitoring; error reports may incidentally contain data present in the failing request European Union (de.sentry.io) Standard Data Processing Addendum; EU Standard Contractual Clauses for any onward transfer

Where personal data is transferred outside the European Economic Area, namely to Resend, Inc. and, for businesses using Clava, to Amazon Web Services in the United States, Enclava relies on appropriate safeguards under Chapter V GDPR: Resend's Data Processing Agreement incorporates the EU Standard Contractual Clauses (Module 2 for tenant-staff account emails, where Enclava acts as controller, and Module 3 for end-customer notifications, where Enclava acts as processor), and so does the AWS Data Processing Addendum (Module 2 for tenant-staff data sent to Clava, where Enclava acts as controller, and Module 3 for end-customer data, where Enclava acts as processor). The EU-hosted infrastructure providers (Supabase and Railway) process personal data within the EU, with Standard Contractual Clauses as a backstop for any access from outside the EEA. Cloudflare operates at the global edge and its R2 object storage is in Cloudflare's automatic location, which is not pinned to the EU; Cloudflare's Data Processing Addendum incorporates the EU Standard Contractual Clauses, which for tenant-staff data (Enclava as controller) apply as Module 2 covering any transfer outside the EEA (end-customer uploads in R2 are addressed in the tenant Data Processing Agreement, Module 3). All sub-processor Data Processing Agreements listed above are signed or in effect.

OpenAI, L.L.C. is not listed in the table above, because the OpenAI API receives no tenant-staff account data from Enclava. The model behind Clava is developed by OpenAI but runs on Amazon Bedrock, listed above. The table also omits Nominatim (OpenStreetMap Foundation) and the OSRM public demo server, which receive end-customer postal addresses and delivery coordinates respectively; neither is under contract, both are under remediation, and both are listed for tenants in the Data Processing Agreement and at https://enclava.io/sub-processors. For inbound message extraction, OpenAI receives end-customer message content (model gpt-4o-mini), under Enclava's separate processor relationship with each tenant; the safeguards for that transfer (the EU Standard Contractual Clauses, Module 3, as the operative Chapter V basis; OpenAI also self-certifies under the EU-US Data Privacy Framework, subject to verification; the no-training commitment; and OpenAI's retention of API inputs for a limited abuse-monitoring window of up to approximately 30 days, after which they are deleted) are addressed in the tenant-facing Data Processing Agreement. Separately, when the Business Presence website builder is enabled (off by default, gated by per-plan generation caps), OpenAI is also used to generate website drafts (model gpt-4.1-mini) from the tenant's business profile and contact details (business name, description, contact email, phone, WhatsApp); drafts are human-reviewed before publishing. This is a distinct processing of tenant business data, separate from end-customer message extraction, under the same EU Standard Contractual Clauses (Module 3) transfer basis and the same US transfer profile described above.

A current list of sub-processors is also published at https://enclava.io/sub-processors.

7. Your Rights as a Data Subject

Under the GDPR (Articles 15 through 22) and the Dutch Uitvoeringswet AVG (UAVG), you have the following rights with respect to the personal data we process about you as a controller:

Right Description
Access (Art. 15) You may request confirmation of whether we process your personal data and, if so, obtain a copy of it.
Rectification (Art. 16) You may request correction of inaccurate personal data or completion of incomplete data.
Erasure (Art. 17) You may request deletion of your personal data where it is no longer necessary for the purposes for which it was collected, or where you withdraw consent (if applicable).
Restriction (Art. 18) You may request that we restrict the processing of your personal data in certain circumstances (e.g. while we verify its accuracy).
Data portability (Art. 20) You may request to receive your personal data in a structured, commonly used, machine-readable format (e.g. JSON or CSV), and to transmit that data to another controller.
Objection (Art. 21) You may object to processing based on our legitimate interest (Art. 6(1)(f)). We will cease processing unless we demonstrate compelling legitimate grounds that override your interests.
Withdraw consent (Art. 7(3) / 13(2)(c)) Where processing relies on your consent (for example, newsletter subscriptions), you may withdraw that consent at any time. Withdrawal does not affect the lawfulness of processing carried out before the withdrawal.
Not to be subject to automated decision-making (Art. 22) You have the right not to be subject to a decision based solely on automated processing which produces legal effects concerning you or similarly significantly affects you. Enclava does not currently engage in such automated decision-making.

To exercise any of these rights, please contact us at privacy@enclava.io. We will respond to your request within one month, as required by Article 12(3) GDPR. In complex cases, this period may be extended by a further two months, in which case we will inform you of the extension and the reasons for it.

We may ask you to verify your identity before processing your request.

8. Right to Lodge a Complaint

If you believe that our processing of your personal data infringes the GDPR or applicable data protection law, you have the right to lodge a complaint with your local data protection authority. Depending on your country, this may be:

Netherlands: Autoriteit Persoonsgegevens (AP) — Hoge Nieuwstraat 8, 2514 EL Den Haag — https://autoriteitpersoonsgegevens.nl — +31 (0)70 888 8500

Indonesia: Kementerian Komunikasi dan Digital (Komdigi) — https://www.komdigi.go.id, until the personal data protection agency provided for by Law No. 27 of 2022 begins operating

UAE: UAE Data Office — https://u.ae/en/about-the-uae/digital-uae/data/data-protection-laws

We encourage you to contact us first at privacy@enclava.io so that we may attempt to resolve your concerns directly.

9. Security

We implement appropriate technical and organisational measures to protect your personal data, including: HTTPS encryption for all data in transit; schema-per-tenant database isolation in PostgreSQL; Fernet-based encryption of sensitive tokens at rest; role-based access control; regular security reviews; and encrypted backups.

A Data Protection Impact Assessment (DPIA) has been conducted for the AI-based message extraction feature, and a separate one for Clava, the AI assistant, in accordance with Article 35 GDPR. Both are available on request.

10. Cookies and Tracking Technologies

We use cookies and similar technologies on enclava.io and within the Enclava platform. For detailed information about the cookies we use, their purposes, and how to manage your preferences, please see our Cookie Policy.

In summary:

  • We use strictly necessary cookies for authentication, session management, and security. These do not require your consent under Article 11.7a of the Dutch Telecommunicatiewet.
  • We use no functional cookies, and we display no cookie consent banner, because we place no cookie that requires consent.
  • We do store a small amount of state in your browser: localStorage for the language you chose, the work view you last used, and whether you dismissed the getting-started checklist; and sessionStorage, cleared when you close the tab, to carry anti-forgery values and your place in account setup across a redirect. The `localStorage` entries are not sent to us. Some `sessionStorage` entries are, by design, because carrying a value across a redirect is what they are for; the Cookie Policy says which, and why. The Cookie Policy names each key.
  • We do not currently use analytics or marketing cookies.
  • We do not use third-party advertising cookies.

11. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices or in applicable law. When we make material changes, we will notify you by email or through a notice on the platform. The date at the top of this document indicates the most recent revision.

12. Governing Law

This Privacy Policy is governed by and construed in accordance with the laws of the Netherlands. Any disputes arising from or in connection with this Privacy Policy shall be submitted to the competent court in the Netherlands.


Enclava Privacy Policy — Version 2.3