Cloudlabels Data Processing Agreement
Last updated: 12 November 2026
1. About this agreement
1.1 This Data Processing Agreement ("DPA") is between you, the business that uses Cloudlabels (the "Customer"), and Furø Tech ENK, a sole proprietorship in Norway, org. no. 911 872 900 ("Furø Tech", "we", "us"). It applies when we process personal data on the Customer's behalf in Cloudlabels (the "Service").
1.2 This DPA is part of our Terms of Service (/terms/) and is accepted electronically when the Customer accepts the Terms of Service. No separate signature is needed. Article 28(9) of the GDPR allows this agreement to be in electronic form. The Customer can download or print this page at any time.
1.3 In this DPA, "GDPR" means Regulation (EU) 2016/679 as it applies in Norway through the Norwegian Personal Data Act. Terms such as "controller", "processor", "personal data", "processing", "data subject", "personal data breach" and "supervisory authority" have the meaning they have in the GDPR. "Customer Personal Data" means personal data that the Customer or its users store in or send to the Service, and that we process on the Customer's behalf. "Sub-processor" means another processor we engage to process Customer Personal Data.
2. Roles and scope
2.1 The Customer is the controller of Customer Personal Data, and Furø Tech is its processor. If the Customer is itself a processor for someone else, Furø Tech is its sub-processor, and the Customer confirms that it is authorised to engage us on these terms.
2.2 This DPA does not cover personal data that we process as a controller for our own purposes, as described in our Privacy Policy (/privacy/). This includes the account details of users (name, email address, sign-in), billing and accounting data, website and security logs, emails sent to us, and our own service and marketing emails.
2.3 The subject matter, nature, purpose, duration, types of personal data and categories of data subjects are described in Annex 1.
3. Instructions
3.1 We process Customer Personal Data only on the Customer's documented instructions, including with regard to transfers to countries outside the EEA, unless Norwegian or EEA law requires us to process it. In that case we tell the Customer about that legal requirement before the processing, unless the law forbids it on important grounds of public interest.
3.2 The Customer's documented instructions are: this DPA, the Terms of Service, the Customer's own settings and use of the Service (for example what it imports, stores, prints, exports, shares or deletes, and the API keys and AI connections it creates), and other written instructions the Customer sends to privacy@cloudlabels.io that we confirm in writing. We do not process Customer Personal Data for our own purposes. We do not use Customer Personal Data for product analytics, session recordings, marketing or to train AI models. Session recordings in the web app mask text shown on the screen, so they do not capture Customer Personal Data.
3.3 When the Customer or its users connect an AI assistant to the Service, the Customer instructs us to send the requested data to that assistant. The AI provider is chosen by the Customer, is not our sub-processor, and processes the data under its own terms with the Customer.
3.4 If a new instruction requires work that the Service does not support, we tell the Customer. Either party may then end the affected part of the Service under the Terms of Service.
3.5 We will tell the Customer immediately if, in our opinion, an instruction breaks the GDPR or other data protection law.
4. The Customer's responsibilities
4.1 The Customer is responsible for having a legal basis for the processing, for informing the data subjects, and for its instructions being lawful.
4.2 The Service is not designed for special categories of personal data (Article 9 GDPR) or data about criminal convictions and offences (Article 10 GDPR). The Customer must not store such data in the Service unless we have agreed in writing on specific safeguards.
4.3 The Customer must keep its sign-in details and API keys safe and give access only to people who need it.
5. Confidentiality
Only Furø Tech's owner and people we authorise may access Customer Personal Data, and only to the extent strictly necessary to provide, support, secure and maintain the Service. Everyone with access has committed to confidentiality in writing or is under a statutory duty of confidentiality. The duty continues after this DPA ends.
6. Security
6.1 We implement at least the technical and organisational measures described in Annex 2 to protect Customer Personal Data, in line with Article 32 of the GDPR. These measures take into account the state of the art, the cost, the nature, scope, context and purposes of the processing, and the risks for data subjects.
6.2 We may change the measures over time, but not in a way that lowers the overall level of security.
7. Sub-processors
7.1 The Customer gives us general written authorisation to engage the sub-processors listed in Annex 3.
7.2 We engage a sub-processor only through a written contract that imposes, in substance, the same data protection obligations as this DPA, in particular sufficient guarantees for appropriate technical and organisational measures.
7.3 We will tell the Customer of any intended addition or replacement of a sub-processor at least 30 days in advance, by email to the account owner and by updating Annex 3 on this page. The notice includes the provider's name, what it will do and where it processes data.
7.4 The Customer may object to the change in writing to privacy@cloudlabels.io before it takes effect, with reasons related to data protection. We will then try to find a reasonable solution. If we cannot, the Customer may end its paid plan before the change takes effect, and we refund the fees it has paid for the unused part of its billing period after the change takes effect. This does not limit the Customer's rights under the GDPR.
7.5 We remain fully responsible to the Customer for the performance of each sub-processor's obligations. We will tell the Customer if a sub-processor fails to meet its data protection obligations in a way that affects Customer Personal Data.
7.6 At the Customer's request, we provide a copy of the data protection terms we have with a sub-processor, or a link to them. We may remove confidential commercial terms.
8. Transfers outside the EEA
8.1 We and our sub-processors transfer Customer Personal Data to countries outside the EEA only as described in Annex 3 or on the Customer's further documented instructions, and only in compliance with Chapter V of the GDPR.
8.2 Each transfer is based on an adequacy decision of the European Commission, including the EU-US Data Privacy Framework for certified US companies, or on the European Commission's standard contractual clauses (Decision (EU) 2021/914) together with any supplementary measures needed. The Customer agrees that we may rely on those standard contractual clauses in our contracts with sub-processors.
8.3 If a transfer basis stops being valid, we will tell the Customer without undue delay and take reasonable steps to put another valid basis in place or stop the transfer.
9. Assistance
9.1 Taking into account the nature of the processing, we assist the Customer with appropriate technical and organisational measures, as far as possible, so it can respond to requests from data subjects who exercise their rights under Chapter III of the GDPR (access, rectification, erasure, restriction, data portability and objection).
9.2 If we receive such a request directly, we do not answer it ourselves unless the Customer has authorised us to. We forward it to the Customer without undue delay.
9.3 Taking into account the nature of the processing and the information available to us, we assist the Customer in ensuring compliance with its obligations on security of processing (Article 32), notification of personal data breaches (Articles 33 and 34), data protection impact assessments (Article 35) and prior consultation with the supervisory authority (Article 36).
9.4 Most assistance is provided through the Service's own functions and this documentation. If the Customer asks for assistance that takes significant work beyond this, we may charge a reasonable fee agreed in advance. We do not charge for assistance needed because we have breached this DPA.
10. Personal data breaches
10.1 We notify the Customer without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data. We send the notice by email to the account owner and other contacts the Customer has given us.
10.2 The notice includes, as far as we know at the time: the nature of the breach, including where possible the categories and approximate number of data subjects and records concerned; the name and contact details of a contact point; the likely consequences; and the measures taken or proposed to address the breach and reduce its possible adverse effects. Where we cannot provide all the information at once, we provide it in phases without undue further delay.
10.3 We take reasonable steps to contain and investigate the breach and to limit its consequences, and we document it.
10.4 Notifying the supervisory authority and the data subjects is the Customer's responsibility, and we assist as described in section 9.3.
11. Information and audits
11.1 We make available to the Customer all information necessary to demonstrate compliance with Article 28 of the GDPR and this DPA. This includes this DPA, our security description in Annex 2, the list of sub-processors in Annex 3, and written answers to reasonable security and privacy questions.
11.2 We allow for and contribute to audits, including inspections, by the Customer or an independent auditor it mandates. The Customer will first try to verify compliance through the information in section 11.1. An audit or inspection must be announced in writing at least 30 days in advance, be held during normal working hours, not take place more than once in any 12-month period unless a personal data breach or a supervisory authority requires it, and not give access to other customers' data or to our confidential information beyond what is necessary. The auditor must be bound by confidentiality. Each party bears its own costs, unless the audit shows that we have materially breached this DPA.
11.3 We cooperate with supervisory authorities as required by the GDPR.
12. Deletion and return
12.1 The Customer can export its data from the Service at any time while it has access, also while its workspace is locked after a trial or a failed payment.
12.2 When the Customer's organisation is deleted, or when this DPA ends, we delete Customer Personal Data, unless Norwegian or EEA law requires us to keep it. Data in the live database and files in storage (for example images, logos and PDFs) are deleted when the organisation is deleted. The database is backed up daily, and each daily backup is deleted after 7 days. Until a backup is deleted, it is protected as described in Annex 2 and is used only to restore the Service.
12.3 If the Customer wants its data returned instead, it must export it before deleting its organisation. If the Customer cannot export because of a fault on our side, we will help it get its data in a common machine-readable format.
12.4 We confirm deletion in writing at the Customer's request.
13. Liability
13.1 Each party's liability under this DPA is subject to the limitations and exclusions of liability in our Terms of Service (section 12). The limitations count towards the same total cap as the Terms of Service.
13.2 Nothing in this DPA limits either party's liability to data subjects under Article 82 of the GDPR, or liability that cannot be limited under applicable law.
14. Term
This DPA applies from when the Customer accepts the Terms of Service and as long as we process Customer Personal Data on the Customer's behalf, including until the data is deleted under section 12. Sections that by their nature should continue, including sections 5, 12, 13 and 16, continue after that.
15. Precedence
If this DPA conflicts with the Terms of Service or any other agreement between the parties about the processing of Customer Personal Data, this DPA prevails.
16. Changes, governing law and disputes
16.1 We may update this DPA, for example to reflect changes in law or in our sub-processors. We tell the Customer about material changes by email at least 30 days before they take effect. Changes required by law may take effect sooner. We will not change this DPA in a way that lowers the protection of Customer Personal Data. If a change is to the Customer's disadvantage and the Customer ends its paid plan for that reason before the change takes effect, we refund the fees it has paid for the unused part of its billing period after the change takes effect.
16.2 This DPA is governed by Norwegian law. Disputes are resolved by the Norwegian courts, with Hordaland District Court (Hordaland tingrett) as the agreed venue, unless mandatory law gives another venue.
17. Standard contractual clauses on request
If the Customer needs the European Commission's standard contractual clauses between controllers and processors (Decision (EU) 2021/915), it may ask us at privacy@cloudlabels.io. We will consider the request in good faith.
18. Contact
Questions about this DPA: privacy@cloudlabels.io. Furø Tech ENK, org. no. 911 872 900, Norway. Our business address is listed in Enhetsregisteret (look it up).
Annex 1: Description of the processing
Subject matter and nature. Hosting, storage, structuring, retrieval, printing, export, transmission and deletion of Customer Personal Data in Cloudlabels, a service for creating, managing and printing labels, and for connected integrations such as Shopify and AI assistants.
Purpose. To provide the Service to the Customer under the Terms of Service, including support, security, error correction and backups.
Duration. As long as the Customer uses the Service, and until deletion under section 12. A workspace that is locked after a trial is deleted 6 months after the trial ended, and a Free account is deleted after 24 months without sign-in, in both cases after a warning by email.
Categories of data subjects. The Customer's users (employees and other people the Customer invites), the Customer's own customers and recipients whose details are printed on labels or shipping marks, and contact persons at the Customer's suppliers or partners, as far as the Customer stores them.
Types of personal data.
- User data in the workspace: name, email address, role, and the actions a user takes in the Customer's workspace, including audit records with IP address and browser information.
- In audit records, the IP address and browser are deleted after 12 months, the email address is replaced by a pseudonymous code after 24 months, and the record is deleted after 3 years.
- Recipient and contact data the Customer adds: name, address, phone number and email address, for example on shipping marks.
- Data synchronised from Shopify when the Customer connects its store: product, variant, inventory and barcode data, and the customer data Shopify sends us in its mandatory privacy webhooks (for example the customer's ID, email address and phone number), which we use only to respond to data requests and erasure requests. We do not access the store's orders or customer records through the Shopify API.
- Content the Customer uploads: images, logos, text and files. These may include personal data if the Customer chooses to add it.
- Data in PDFs created through the AI connection (MCP), stored for about 48 hours.
- Logs of API and AI connection use linked to the Customer's organisation, deleted after 12 months.
Special categories. None intended. See section 4.2.
Frequency. Continuous while the Customer uses the Service.
Annex 2: Technical and organisational security measures
We have these measures in place:
- All traffic to and from the Service is encrypted in transit (HTTPS/TLS).
- The main database and file storage run at Supabase in the EU (Stockholm, Sweden).
- Each Customer's data is separated from other customers' data by access rules in the database (row-level security).
- Sign-in through Supabase Authentication (in the web app with Google, a passkey or an email link, in the iOS app with email address and password). Cloudflare Turnstile protects sign-in, sign-up, invitations and password changes against automated abuse.
- API keys and AI connection tokens are stored as hashes, not in readable form.
- PDFs created through the AI connection are stored in a private storage area, are only shared through signed links that expire after 48 hours, and are deleted after about 48 hours.
- Shopify data is deleted within 48 hours after the store uninstalls the app.
- The Customer controls user access through roles in its workspace.
- Session recordings (only with the user's consent) mask all text typed and shown on the screen. IP addresses are not stored in product analytics.
- Files in storage are deleted when the organisation is deleted.
- Server logs are kept for 1 day at Vercel, 30 days at Railway and 7 days at Supabase. Resend keeps email data and logs for 30 days.
- The database is backed up daily at Supabase, and daily backups are kept for 7 days. Uploaded files are not part of the backups.
- Our providers state that stored data is encrypted: Supabase (AES-256 at rest), Railway (AES-256 on volumes, encrypted private network between services) and Forward Email (encrypted mailbox per user and encrypted disks).
- Item photos, print profile images and email images are stored at web addresses that do not expire and do not require sign-in, because they are meant to be printed or shown. Anyone who has the address can open the image. The Customer should not upload images containing personal data to these areas. Profile pictures, organisation logos and generated PDFs are kept in private storage.
Annex 3: Sub-processors
Last updated: 12 November 2026
| Sub-processor | What it does | Where data is processed | Transfer basis |
|---|---|---|---|
| Supabase Pte. Ltd. (Singapore) | Database, file storage, sign-in | Data is stored in the EU (Stockholm, Sweden). Supabase in Singapore can access the data, for example for support | Standard contractual clauses (Decision (EU) 2021/914) in Supabase's data processing agreement |
| Railway Corporation | Application servers and cache (Redis) | USA (us-west2) | EU-US Data Privacy Framework and standard contractual clauses |
| Vercel Inc. | Hosting of the web app, server logs, usage and performance measurement in the web app (only with the end user's consent) | USA | EU-US Data Privacy Framework and standard contractual clauses |
| Plus Five Five, Inc. (Resend) | Sending emails from the Service (for example invitations) | Emails are sent from the EU (Ireland). Email data and logs are stored in the USA | EU-US Data Privacy Framework and standard contractual clauses |
| Cloudflare, Inc. | Bot protection (Turnstile) | Global network, company in the USA | EU-US Data Privacy Framework and standard contractual clauses |
| Forward Email LLC | Receiving and storing emails to support@ and privacy@ (our mailbox), which may contain Customer Personal Data | USA (mainly Denver, Colorado). Encrypted backups are stored with Cloudflare R2 | Standard contractual clauses (Decision (EU) 2021/914) in Forward Email's data processing agreement |
| PostHog, Inc. | Product analytics, only with the user's consent. Recordings mask screen text, so PostHog should not receive Customer Personal Data. Listed for transparency | USA (PostHog US Cloud) | EU-US Data Privacy Framework and standard contractual clauses |
| Shopify | Only when the Customer connects its Shopify store. Shopify is the Customer's own provider, not our sub-processor. | Not applicable | Not applicable |
Fiken, Stripe, Apple (App Store and TestFlight), Google (Analytics, Ads and sign-in) and X are not sub-processors under this DPA. We use them as a controller for our own purposes, as described in our Privacy Policy.