This agreement applies when you upload photos of other people to Luala for your business or profession. It is the contract that Article 28 of the EU General Data Protection Regulation (GDPR) and Article 9 of the Swiss Federal Act on Data Protection (FADP) ask you to have with us. "We" are Die Digitalen GmbH, Rautistrasse 60, 8048 Zürich, Switzerland. "You" are the person or company a space in Luala is used for, and its owners act for you. In a space shared with others, what its members upload for your business falls under this agreement too.
If you upload photos only for yourself, your family or your friends, in your personal space or a shared one, this agreement doesn't apply, and the privacy policy covers everything.
1. How it applies
This agreement is part of the terms. There is nothing to sign: the confirmation you give before every upload, or once when you connect an assistant, covers it. We store that confirmation with the version of the terms you agreed to.
A version of the terms brings with it the newest version of this agreement dated on or before it. When this agreement changes, a version of the terms with the same date is published with it.
A later version of this agreement applies from its date to everything this agreement covers, whichever version you confirmed.
2. Who is responsible for what
You are the controller, and we are your processor, for:
- the photos of other people you upload;
- the photos made from them;
- what you type for those photos.
You decide why these photos are used and you answer for doing so lawfully, including having a legal basis under data protection law. The written consent section 4 of the terms asks you to have from everyone in them comes on top of that. By uploading, you confirm that you have the authority to instruct us for the business the photos are uploaded for.
We are the controller for what we process for our own purposes and duties, as the privacy policy describes:
- account and billing data;
- the automatic checks for nudity, sexual content and age;
- reports, moderation, and the copy we keep of a banned account as evidence;
- upload confirmations and accounting records.
We process photos for these purposes only and don't reuse them for anything else. If we ban an account, we keep a copy of its photos, selfies and history for one year, longer only while a legal case needs it. Only our operators can reach that copy, and it is deleted when that time is up, even if you deleted the photos.
3. What is processed
- What for: making, editing, storing and showing the photos you ask for.
- What: photos and other images of identifiable people, which show their faces and bodies and can reveal more, such as health or religion; any metadata an upload carries; the instructions you give for them; and the personal data in the photos made from them.
- Whose: the people you upload photos of, such as models you hire, staff or clients, including a person an owner links to a character, who then sees its photos as a viewer. Section 4 of the terms sets the age limits.
- How long: until you delete them or the space is deleted (section 11).
4. Your instructions
We process these photos only on your instructions. Your instructions are the terms, this agreement and what you do in Luala. If the law makes us process them another way, we tell you first, unless that law forbids it. If we think an instruction breaks data protection law, we tell you.
5. Confidentiality
Everyone at Die Digitalen GmbH who can reach these photos is bound to keep them confidential.
6. Security
We keep to the measures in Annex 2. We may change them, but never to a lower level of protection.
7. Subprocessors
You approve the subprocessors in Annex 1. Each is bound by a contract to the same data protection duties as we are, and we answer to you for their work.
We email you 30 days before a new subprocessor starts processing these photos. You can object by writing to privacy@lua.la within those 30 days. If we can't resolve your objection, you may end this agreement by deleting the space, or your account if the photos are in your personal space. Write to the same address before you delete it: we refund the unused credits paid for in that space, pro rata, whatever section 11 of the terms says about a running plan.
Link (Stripe) is not a subprocessor. It sells credits and plans as reseller, as a controller in its own right, and it never receives these photos.
8. Transfers abroad
We are in Switzerland, which the European Commission recognises as protecting personal data adequately. Some subprocessors are in the USA or process data outside Switzerland and the EU. Those transfers rest on the European Commission's standard contractual clauses or on the companies' certification under the Data Privacy Framework. Tigris relies on those clauses without the adaptations the Swiss regulator asks for.
9. Data breaches
If a breach affects these photos, we email you without undue delay and within 48 hours of becoming aware of it. We say what happened, which data and how many people it concerns as far as we know, what it is likely to lead to and what we are doing about it. We add what we learn later.
10. Helping you
Requests from people in the photos. If someone contacts us to exercise their rights over photos uploaded for you, a viewer linked to a character included, (access, correction, deletion, restriction, portability or objection), we tell you without undue delay. You decide how to respond, and we help, given what we process and the information we have. We answer the person ourselves only if you instruct us to or the law requires it. You can act on most requests in Luala: delete a photo, delete a character's selfies, or download a copy under "Your data" in Settings. A report of illegal content is different: our moderation handles it, as section 10 of the terms says.
Your own duties. We help you meet your duties on security, breach notices, data protection impact assessments and prior consultation with an authority (GDPR Articles 32 to 36), given what we process and the information we have.
11. Deleting
You delete photos in Luala, and they go at once. Copies in backups are gone within 30 days. Google may keep what we send it for up to 55 days to detect abuse, and Anthropic the text we send it for up to 30 days, or up to two years if its safety systems flag it, each under its own terms. fal's handling is described in Annex 1.
When the space is deleted, or your account with your personal space, the same applies to everything in this agreement. What a member made in a shared space stays there when they leave it or delete their account, until the space is deleted. What we hold as controller (section 2) keeps the retention the privacy policy states.
When this agreement ends, you choose whether we return or delete these photos. To have them returned, each person in the space downloads what they made under "Your data" in Settings, or you write to privacy@lua.la and we provide the space's photos in a common format. To have them deleted, delete the space, or your account if they are in your personal space. After a return we delete the remaining copies, unless the law requires us to keep them.
12. Information and audits
On request to privacy@lua.la, we give you the information you need to show that this agreement and data protection law are kept.
We allow and contribute to audits, including inspections, by you or an independent auditor you mandate. You arrange them with reasonable notice, during normal business hours, and they must avoid unnecessary disruption and protect the confidentiality and security of other customers' data.
Where documents, independent audit reports or other evidence are enough, we may give you those instead of an inspection on site. An inspection on site may take place if they aren't enough, after a material data breach, or where otherwise reasonably necessary to check compliance.
13. Changes, liability and law
We announce changes to this agreement as section 12 of the terms says. Sections 13 and 14 of the terms cover liability and the law that applies. If this agreement and the terms disagree about these photos, this agreement decides. Nothing here limits what the law doesn't allow to be limited, including claims under Article 82 GDPR.
Annex 1: Subprocessors
| Who | What for, and where |
|---|---|
| Fly.io, Inc., 2261 Market Street #4990, San Francisco, CA 94114, USA. compliance@fly.io | Hosting and database, in Frankfurt, Germany |
| Tigris Data, Inc., 1250 Borregas Ave #87, Sunnyvale, CA 94089, USA. privacy@tigrisdata.com | Storage, in Frankfurt, Germany |
| Google Cloud EMEA Limited, 70 Sir John Rogerson's Quay, Dublin 2, Ireland. legal-notices@google.com | AI image processing and email delivery, in Ireland and other countries where Google has facilities |
| Features & Labels, Inc. (fal), 2261 Market St. Suite 10467, San Francisco, CA 94114, USA. support@fal.ai | AI image processing, in the USA and other countries |
| Anthropic Ireland, Limited, 6th Floor, South Bank House, Barrow Street, Dublin 4, D04 TR29, Ireland. privacy@anthropic.com | Text processing, of what you type only, never a photo, in the USA |
Third-party models. Some jobs run on models fal reaches through a third party's API: making a photo larger (upscaling, zooming in), cutting a person out of the background, and removing an object. When you use one of these, you acknowledge that the photo is transferred to that third party. fal identifies these models on its platform. These third parties may process photos in countries other than those listed for fal.
fal's own subprocessors are on its list.
Google, fal and Anthropic don't use these photos, or what you type for them, to train their models. We tell fal not to keep what we send it in its request history and to delete what it sends back within an hour. Until then, what it sends back sits at a public address that can't be guessed. What we tell fal applies to fal itself.
Annex 2: Technical and organisational measures
- In transit: luala.app and lua.la answer only over HTTPS, with HSTS, and storage is reached over HTTPS. The app reaches the database over Fly.io's encrypted private network.
- At rest: the database, its backups and stored files are encrypted by Fly.io and Tigris.
- Backups: the database is backed up automatically. Copies of deleted data are gone from backups within 30 days. Restores are tested.
- Storage access: the storage bucket is private. A photo is read through a signed link that expires within two hours, and uploaded through one that expires within 15 minutes. fal gets a signed link that lasts as long as the job can.
- What's kept: every uploaded photo is encoded anew before it is kept, so location data and other metadata don't stay. The original waits in a private staging area until you save or remove it, and expires there within about two days.
- Who can see them: a space's photos are shown only to the people in it, in Luala or through an assistant one of them connected: its owners and members see all of them, and a viewer only the photos of the characters linked to them. Passwords are stored as a bcrypt hash, and for a passkey we hold only its public key.
- Operators: the admin answers only to operators and shows no one else that it exists. An operator looks at a photo only for a report, an age check or a decision about an account. Operator accounts use multi-factor authentication.
- Keys: production's keys are held as secrets on Fly.io, outside the code.
- Updates: security updates are applied regularly.
- Incidents: we follow a documented process for detecting and responding to incidents.
- Deletion: deleting a space or an account removes its stored files, and the job retries until they are gone.