Privacy policy

Last updated: 19 November 2026.

Who is the controller

The controller of the data described here is Pablo del Arco, owner of Arco Rooms, based in Spain. You can find more information about the owner in the legal notice. For any question about your data you can write to privacy@arcorooms.com.

This policy explains how we handle the data of people who have an account. Data about tenants and others that users store in Arco Rooms is processed on behalf of each user, who is its controller; that is explained at the end.

We do not store your IP address. To stop abusive submissions, we keep in our database a fingerprint of the IP made with a secret key (HMAC), which does not show the address, together with the time of the attempt, and we delete it after 24 hours. The legal basis is our legitimate interest in protecting the form from abuse (art. 6(1)(f) GDPR).

Arco Rooms accounts

If you create an account or are invited to an organization we keep:

  • Your name, email address and language.
  • Your password, only in hashed form, or your Google account identifier if you sign in with Google.
  • The organizations you belong to and your role in each.
  • A log of the changes you make, for security and for the organization's history.
  • If you subscribe to a v1 paid plan: name, country and postcode; the eligibility declaration (private-capacity subscription, outside any business or professional activity and without an intra-EU VAT number; in Spain, also without an IRPF withholding obligation on this subscription), with its date, text version and transaction reference; the corroborated country (Stripe billing, payment method or IP) and the review outcome if they do not match; plan, subscription status and Stripe identifiers. Simplified invoices use the necessary details under Articles 4 and 7 of Royal Decree 1619/2012, including tax ID and address when you request them (Articles 7(2) and 7(3)); full invoices use your full name, complete address and tax identifier where required or requested under Article 6. We also retain the minimum place-of-supply evidence with source and date. This flow does not request intra-EU VAT numbers to admit B2B subscriptions or consult VIES; an intra-EU VAT number received through another channel is not ignored. We do not request document copies or a national identity-document number from every foreign consumer merely because they are a consumer. Stripe handles card details; we do not store your full card number. This v1 takes card payments.

We use it to provide the service, keep your account secure, send the emails you need (confirmations, invitations, password resets, service notices) and invoice you. The legal basis is performance of the contract (the terms and conditions) and, for invoices, compliance with legal obligations. We do not use it for advertising, we do not profile you and we do not sell it.

In particular:

  • Charging for the plan and managing the subscription: performance of the contract (Article 6(1)(b) GDPR).
  • Managing enrolment, the country-specific eligibility declaration, payment and subscription: performance of the contract and precontractual steps requested by you (Article 6(1)(b) GDPR). Issuing and retaining invoices/corrective invoices, determining VAT and evidencing customer tax status and location: legal obligation (Article 6(1)(c) GDPR), under Spanish Law 37/1992, Articles 6, 7, 15 and 19 of Royal Decree 1619/2012 and Articles 18 and 24a to 24f of Implementing Regulation (EU) No 282/2011. We do not ask for separate consent for the tax archive; the eligibility declaration is not privacy consent and does not change tax obligations.

We keep it while you have an account. You can ask us to delete your account by writing to privacy@arcorooms.com. We delete your account and any documents you uploaded from our live systems within 31 days of confirming your request. What the law requires us to keep, such as invoices, is retained for the legal period. Data included in encrypted backups may remain for the backup retention cycle: 30 days in GitHub and around six months in the operator’s local copies, under the criteria explained in How we protect your data.

For billing data:

  • Invoices, corrective invoices and payment records, including necessary recipient details: these are retained for the applicable tax and accounting periods, including after the account or organization is closed, with access restricted to that purpose. Article 19 of Royal Decree 1619/2012 refers to the General Tax Act; its Articles 66 to 68 and 70 govern the general four-year limitation period, its starting point, interruptions and evidential obligations. The reference accounting policy is six years from the last entry for the relevant financial year, including closing, based on Article 30 of the Commercial Code, without prejudice to specific legal obligations requiring longer retention of affected records. When the applicable period ends, identifiable information is deleted, subject to blocking where legally required and destruction once liabilities expire. This tax archive does not justify keeping all account or tenant data. The declaration, corroborated country and location evidence are linked to this archive only to the extent and for as long as needed to justify the transaction; data from unsuccessful applications are not retained for six years by default.
  • VIES — outside v1 scope: this flow does not request intra-EU VAT numbers or consult VIES to admit B2B subscriptions from other Member States, which are not available. Verification and a specific retention policy for new VIES evidence are planned for a later phase; before enabling them, we will explain the relevant data, purpose, legal basis and retention periods. This does not change invoice-retention obligations or authorize deletion of earlier evidence that must be kept by law.

Who else handles it

We use the following providers to deliver the service, under contracts governing data protection. Stripe acts as a processor for some processing and as an independent controller for other processing, as explained below:

  • Supabase Pte. Ltd. (Singapore): database, sign-in and document storage. Data is hosted on servers in the European Union (Frankfurt, Germany). Supabase and its affiliate Supabase, Inc. (United States) may access it from Singapore or the United States for support and service operations. Those transfers rely on the standard contractual clauses approved by the European Commission (Implementing Decision (EU) 2021/914), included in its data processing agreement.
  • Vercel Inc. (USA): hosts the website. Server functions run in Frankfurt (EU) and its content delivery network is global. That global network may process your IP address and session cookies outside the EU. The transfer relies on the EU-U.S. Data Privacy Framework, under which Vercel is certified.
  • GitHub, Inc. (USA): stores encrypted daily database backups as artifacts; each artifact is retained for 30 days. The transfer relies on the EU-U.S. Data Privacy Framework, under which GitHub is certified.
  • Plus Five Five, Inc. (USA), which operates the Resend service: sending emails. It stores email delivery data in the United States. The transfer relies on the EU-US Data Privacy Framework, under which it is certified, and on the standard contractual clauses in its data processing agreement.
  • Cloudflare, Inc. (USA) and Google LLC (USA): messages you send to help@arcorooms.com or privacy@arcorooms.com go through Cloudflare's email routing service and are received in a Gmail account held by the owner. The transfer relies on the EU-US Data Privacy Framework, under which both are certified.
  • Google LLC (USA): provides sign-in with your Google account. In the current integration, when Google Identity Services is enabled, the browser loads Google scripts when the sign-in and sign-up pages open, before you press "Continue with Google". Authentication with your account is completed if you choose that option; the initial loading and possible storage are described in the cookies section. The transfer relies on the EU-US Data Privacy Framework, under which Google LLC is certified.
  • Stripe: paid-plan payments, subscriptions, billing portal and invoices, once payments are enabled. It receives the necessary billing and payment-method details. Section 2 of its Data Processing Agreement (DPA) distinguishes two roles: it acts as a processor when processing data on our instructions to provide its services; it acts as an independent controller when determining its own purposes and means, including fraud prevention, legal and identification obligations and selecting financial providers. We do not describe all Stripe processing as processing on our behalf. If you use Link, Stripe also handles the data you give that service under its terms and privacy policy.

Some of these providers are outside the European Economic Area (United States or Singapore) and may access data from there. In that case the transfer relies on the EU-US Data Privacy Framework, where the provider is certified, or on the standard contractual clauses approved by the European Commission, as stated for each provider.

For Stripe, its DPA provides for transfers to Stripe, LLC in the United States, and possible transfers to affiliates and providers in other countries. Covered transfers to Stripe, LLC rely on the EU-U.S. Data Privacy Framework (DPF), under Commission Implementing Decision (EU) 2023/1795. The official DPF list and Stripe, LLC profile were checked on 5 November 2026: the profile showed Active for the EU-U.S. framework, including non-HR data. Its Data Transfers Addendum (DTA) gives priority to the DPF and provides for standard contractual clauses where another mechanism applies. Coverage is limited to the entities and transfers included; it does not mean every Stripe provider is certified. You can ask for information about safeguards at our privacy email address.

Tenant data

Data that users store about their tenants, teams and contacts is each user's responsibility, and Arco Rooms only processes it on their behalf to provide the service, under the data processing annex of the terms. If you are a tenant and want to exercise your rights, contact whoever manages your rental; if you write to us, we will pass your request on to them.

Your rights

You can ask to access, correct, delete, restrict, object to or port your data by writing to privacy@arcorooms.com from the email address you signed up with. We will reply within one month.

If you think we have not handled your data properly, you can complain to the Spanish Data Protection Agency (aepd.es).

How we protect your data

Our database and server functions are in the European Union (Frankfurt, Germany); the website and your session handling go through Vercel's global network. Your tenants' DNI, NIE or passport numbers are stored encrypted. Only the last 4 characters are shown on screen; the full number can only be viewed, when needed, by people with permission in your account. Copies of documents you upload are stored on EU servers with our provider's encryption at rest, and only people with permission in your account can view them. You can ask us to delete your account by writing to privacy@arcorooms.com. We delete your account and any documents you uploaded from our live systems within 31 days of confirming your request.

We keep encrypted database backups as GitHub artifacts for 30 days. We also keep encrypted local copies on equipment operated by the service operator, retaining the 14 most recent copies and the first copy of each month for six months. This cycle means retention of around six months in the local archive, not immediate, individual deletion of each account’s data.

These database backups include the metadata of files in Supabase Storage, but not their contents. They are used only to restore the service after a failure; the included data is removed as copies expire under each retention cycle. What the law requires us to keep is retained separately.

Cookies

Arco Rooms does not use analytics, advertising or tracking cookies, or third-party analytics tools. We use cookies and local storage for the functions listed below. The consent exemption in Article 22.2 of Spanish Law 34/2002 is limited to technical storage or access for transmitting communications or what is strictly necessary to provide a service you have expressly requested; it does not automatically cover all third-party cookies or determine the legal basis for requests the browser sends to third parties. Google’s current loading before a click is described separately; the legal basis for these requests and any storage exemption must be validated.

Scrollable table 1
NameOwner and domainWhat it is forDurationType
NEXT_LOCALEArco Rooms, www.arcorooms.comRemembering the site language (Spanish or English). It is created when you switch language or when the page language does not match your browser's.Until you close the browserFirst-party cookie, technical
themeArco Rooms, www.arcorooms.comRemembering whether you prefer the light or dark theme.Until you delete it in your browserFirst-party local storage, technical
arco:calendar-layoutArco Rooms, www.arcorooms.comInside the app, remembering whether you prefer the calendar as a list.Until you delete it in your browser or go back to the normal viewFirst-party local storage, technical
sb-…-auth-token (if it is large, it is split into sb-…-auth-token.0, .1…)Arco Rooms, www.arcorooms.com (handled by Supabase, our sign-in provider)Keeping you signed in and checking it is you on every page of the app. It is created when you sign in.Deleted when you sign out; if you do not sign out, the browser keeps it for up to 400 daysFirst-party cookie, technical
sb-…-auth-token-code-verifierArco Rooms, www.arcorooms.com (handled by Supabase)Storing the PKCE verifier to securely complete the sign-in and authentication-code exchange requested by the user. It is used exclusively for this technical purpose.Maximum configured lifetime of 400 days (34,560,000 seconds)First-party cookie, technical and strictly necessary for the requested service; exempt from consent (Article 22.2 LSSI)
sb-…-auth-token-flow-…-code-verifier and sb-…-auth-token-flows-code-verifierArco Rooms, www.arcorooms.com (handled by Supabase)Storing the PKCE verifier for each attempt and the index of pending attempts to securely complete the sign-in and authentication-code exchange requested by the user. They are used exclusively for this technical purpose.Maximum configured lifetime of 400 days (34,560,000 seconds)First-party cookies, technical and strictly necessary for the requested service; exempt from consent (Article 22.2 LSSI)

Google on the sign-in and sign-up pages

In the current integration, when Google Identity Services is enabled, your browser loads Google’s service from accounts.google.com/gsi/client and the Google resources it requests when the sign-in or sign-up pages open, without waiting for you to press "Continue with Google". These requests disclose your IP address and technical browser data to Google. The service may use cookies, including g_state, at this stage. Completing sign-in with your Google account requires you to choose that option.

⚠️ Pending review by qualified legal counsel: the legal basis for the initial communications to Google must be validated, as must, separately, whether storage on or access to your device before that choice is exempt from consent under Article 22.2 LSSI. Being an authentication system does not in itself establish an exemption. Informing you does not replace consent where it is required. Before the definitive version is published, an exemption must be established for each purpose, or non-exempt storage and access, including scripts causing them, must be prevented until valid consent has been obtained.

Scrollable table 2
NameOwner and domainWhat it is forDurationType
g_stateGoogle, stored on www.arcorooms.comGoogle’s service may create it to remember the state of its sign-in on this site, for example whether you closed its window or signed out.Up to 180 days, according to the technical inventory pending revalidationGoogle cookie on our domain; consent exemption pending validation
Google cookiesGoogle, accounts.google.comIdentifying you with your Google account and protecting that sign-in. Google sets and controls them.As set by GoogleThird-party cookies; necessity and any consent requirement must be assessed for each purpose

Google handles those cookies and your Google account data under its own policy, available at policies.google.com/technologies/cookies. Not pressing "Continue with Google" does not in itself prevent the initial loading of the service or guarantee that g_state will not be created.

If we ever use other cookies

If we add analytics, advertising or any other cookies that are not needed for the service, we will not switch them on without your consent. We will ask first with a notice where rejecting is as easy as accepting, with both buttons at the same level, and you will be able to change your mind at any time. We will update this table before doing so.

How to delete them

You can see and delete cookies and local storage in your browser settings. If you delete the session ones, you will need to sign in again; if you delete the language or theme ones, the site will go back to its defaults.

Changes

If we change anything important in this policy, we will let you know by email or in the app before it applies.

Bank connection for rent reconciliation

This feature is not available yet. This section will apply when we activate it, and we will notify you beforehand.

Connecting a bank account is optional. The initial version is restricted to authorised accounts used for the operator’s own or family rental activity; it is not available to other landlords. Only connect an account whose holder has authorised access for this purpose and for which you have sufficient authority.

Who decides how data is used. For the operator’s own rentals, the landlord is the controller of payment and counterparty data. If this feature is made available to other landlords, each landlord will be the controller of their bank data and Arco Rooms will process it on their instructions under the data processing annex. The Arco Rooms operator is the controller of the minimum user-account, security and connection-request records: user, organisation, date, notice version and requested scope. The legal bases are performance of the contract for a requested feature where the user is a party, and legitimate interests in security and recording instructions; these records do not contain transaction contents.

Data and purpose. Through Enable Banking, the connection reads designated accounts to reconcile rent receipts. It stores the account’s technical identifier, name, currency and masked IBAN. For imported booked credits within the 90-day window, it stores the booking date and value date if supplied, amount, currency, transaction identifier, counterparty name, payment description and last four IBAN characters where supplied. Balances are not requested, and debits or complete bank responses are not added to the history. Only accounts marked as dedicated to rentals are imported; that designation does not itself verify that every credit is rent: unrelated incoming payments may appear and must be dismissed. Current text processing masks IBANs but does not guarantee removal of sensitive information from names or descriptions. The feature is not used for advertising, AI training or creditworthiness assessment.

Reconciliation necessary for a tenancy agreement may rely on performance of that agreement for the tenant’s data. For other payers or counterparties, the landlord assesses their legitimate interest in identifying and evidencing rent payments, with data minimisation and a right to object. The account holder’s authorisation is not consent on behalf of third parties appearing in transactions. For the operator’s own activity, reconciliation relies on that legitimate interest; an internal connection does not create a contract with oneself. The landlord must inform tenants and other individuals about the data categories and bank source, interests pursued, recipients, retention and rights under Articles 13 and 14 GDPR.

Enable Banking. Enable Banking Oy (Finland) provides account information services under its own AISP registration and is an independent controller for that service, not merely an Arco Rooms subprocessor. Before access, review its API terms and API privacy notice, and explicitly authorise access in the banking flow. Its notice states that its cloud providers process data in the EEA; account data passes through its API for a maximum of 60 seconds, authorisation-session data is retained for up to 180 days, and IP address and browser information for 30 days. These are its retention periods, not those for Arco Rooms history. The actual authorisation may be shorter depending on the bank. Manage authorisations at Enable Banking.

Retention and disconnection. The daily job selects unreconciled incoming payments for deletion when their booking date is earlier than the current day minus 90 days, and dismissed payments when at least 24 hours have elapsed since their last update. Deletion occurs when the job runs, not necessarily within 24 hours of dismissal; execution failures can delay it. Until reimport is blocked by external transaction identifier, a dismissed and deleted transaction may reappear if the bank returns it again within the import window. Disconnecting disables reads for that connection and the operation deletes unreconciled incoming payments from active systems and minimises reconciled ones.

During the 90-day review window from the booking date, recently reconciled payments retain the supplied payer name and description for reconciliation review, together with the last four IBAN characters and value date. These fields are removed on disconnection, when the account is unmarked, or when the daily job applies minimisation after the window expires; reconciliation alone does not remove them. Execution failures can delay minimisation. The auxiliary archive retains amounts, booking dates, currencies, technical identifiers and account and reconciliation metadata, including the link to a receipt where retained. That link can identify the individual: the data is not anonymous.

⚠️ Proposed retention policy, subject to Finance and tax-adviser approval and implementation of the prior review: the purely auxiliary archive is reviewed for deletion six years after the end of the year of the booked bank entry (`booking_date`); this is not an absolute maximum or a universal tax retention period. It may be deleted earlier if no longer necessary. Before deletion, sufficient evidence must exist in a valid archive, and the auxiliary data must no longer be needed as payment evidence for a claim, inspection, official request, interrupted or still-open limitation period, or subsequent tax effects. Exceptions must be documented and reviewed; lifting a hold or deleting a receipt is not sufficient. The auxiliary archive is independent of receipts, invoices and tax records, which follow their own policies and legal retention periods. Purging must not change accrued, collected or outstanding amounts or receipts’ original dates. The current implementation does not yet guarantee this prior review, and this policy does not authorise unconditional automatic deletion.

We also request revocation of the Enable Banking session. If it cannot be confirmed, the connection remains disabled locally and you can retry or manage the authorisation with Enable Banking or your bank. The daily job retries automatically up to the configured limit of eight automatic retry cycles or until the authorisation expires. Once the limit is reached, manual action is needed. Stopping reads is not confirmation of revocation at the bank. The session identifier is kept encrypted and separately for revocation; it is erased when confirmation is recorded or when a purge run detects expiry. Queue metadata is erased in a later purge run after 24 hours have elapsed since settlement. A job error code does not itself establish that an operator has received an alert.

Data is held in the infrastructure described in this policy, with access restricted by organisation and role. Backups containing bank data follow the general cycle described here: 30 days in GitHub and around six months in the operator’s encrypted local copies. A documented manual procedure exists to export and reload the available erasure register and run erasure replay. In the current implementation, it does not guarantee that dismissed and purged transactions cannot reappear, and a complete restoration of real backups has not been verified. We do not guarantee that all erasures are reapplied before access. Restoration involving live data remains blocked until these defects are corrected and verified; deleting a transaction does not individually erase it from every backup. European storage does not remove the providers’ access and international transfers described in this policy.

To exercise rights concerning a tenancy, including objecting to processing based on legitimate interests, contact your landlord. Requests we receive as a processor are forwarded to the controller. For Arco Rooms account data, use the privacy contact in this policy; for the AIS service, use Enable Banking’s channels. You may complain to the Spanish Data Protection Agency (AEPD).