photos.chat
Company Events →

GDPR & UK GDPR ARTICLE 28 · DATA PROCESSING ADDENDUM

Data Processing Agreement

Last updated: November 12, 2026 · Incorporated into and subject to the photos.chat Terms & Conditions.

1. Scope, Parties & Incorporation

This Data Processing Agreement ("DPA") forms part of the Terms & Conditions (the "Principal Agreement") between the organization or individual creating or administering an event on the Platform (the "Customer" or "Data Controller") and photos.chat (the "Data Processor"). This DPA applies automatically whenever Personal Data subject to Regulation (EU) 2016/679 ("EU GDPR"), the UK Data Protection Act 2018 / UK GDPR, the Swiss FADP, or substantially similar data-protection laws is processed on the Customer's behalf through an event hosted on photos.chat. All liability limitations, indemnities, and dispute-resolution terms in the Terms & Conditions (including Section 7's strict liability cap equal to the fee paid for the specific event) apply in full to this DPA.

2. Allocation of Roles (Controller vs. Processor)

  • Customer as Data Controller: The Customer determines why and how an event photo wall is operated, who is invited to scan the event QR code or enter the 6-digit Guest PIN, whether pre-approval moderation or OTP verification is enabled, and how Venue TV screens display content. The Customer is solely responsible for providing any required venue signage or attendee privacy notice and establishing a lawful basis (such as legitimate interest or attendee consent) under GDPR Articles 6 and 13.
  • photos.chat as Data Processor: photos.chat processes event media, display names, and guestbook wishes strictly on documented instructions from the Data Controller (configured via the Host Studio, Moderator Console, Editor Console, and Organization Workspace) for the sole purpose of delivering the live event wall and post-event archive export.
  • Zero Biometric / Facial-Recognition Processing: photos.chat does not extract facial geometry, run facial recognition, train generative AI models on Customer event uploads, or sell attendee data to advertisers or data brokers.

3. Article 28(3) Processing Details (Annex I)

Subject Matter & NatureReal-time browser upload, optional live cropping/framing, WebSocket broadcast to authorized event screens, moderation, and temporary ZIP/CSV export of event photographs, short video clips, and guestbook messages.
Duration & Automated ErasureStrictly transient: user-facing download access lasts 3 calendar days after event conclusion on Free events and 7 calendar days on Paid (Relax & Enjoy) events, followed by automated physical purge of encrypted R2 media objects and D1 rows after the 30-day internal operational safety buffer (or immediately upon Controller execution of Delete Event in Host Studio).
Categories of Data SubjectsEvent attendees/guests voluntarily scanning the event QR code, and Customer-designated Hosts, Moderators, and Photo Editors.
Categories of Personal DataGuest-chosen display name (e.g., first name), uploaded event photos and short videos, optional photo captions and guestbook wishes, emoji reactions, transient IP/rate-limit metadata, and—only if explicitly enabled by the Controller—OTP verification email/contact details.
Prohibited Special CategoriesSpecial-category data under GDPR Article 9, payment card images, government IDs, medical/HIPAA records, and confidential trade secrets are prohibited under Terms Section 6.4.

4. Technical & Organizational Security Measures (Article 32 — Annex II)

  • Encryption in Transit & at Rest: All guest, staff, WebSocket, and API traffic is encrypted via HTTPS/WSS (TLS 1.2/1.3). Media objects in Cloudflare R2 and relational records in Cloudflare D1 are encrypted at rest (AES-256).
  • Role-Separated Access & Hashed PINs: Separate capability-scoped tokens for Guest, Moderator, Photo Editor, and Host roles. All 6-digit numeric PINs and organizer passwords are stored strictly as salted PBKDF2-SHA256 digests; bumping token_version in Host Studio revokes active sessions immediately.
  • Pending Media Isolation: When Moderation Mode is enabled, unapproved uploads are gated behind staff bearer-token checks on media endpoints and withheld from public Guest/TV state payloads until explicitly approved.
  • Abuse & Rate-Limit Controls: Atomic Cloudflare Durable Object lockouts on PIN/login brute-force attempts, upload size/type validation, and strict Content-Security-Policy sandboxing on uploaded brand logos.

5. Authorized Sub-Processors & International Transfers (Annex III)

The Controller grants general written authorization for the following infrastructure sub-processors bound by data-protection and Standard Contractual Clauses (SCCs) / EU-U.S. Data Privacy Framework commitments where applicable:

Sub-ProcessorFunctionSafeguards / Location
Cloudflare, Inc.Edge Workers compute, D1 database, R2 object storage, Durable Objects real-time rooms & WAFGlobal Edge / EU-U.S. DPF & EU SCCs
Stripe, Inc.Organizer checkout, tax/receipt issuance & PCI-DSS Level 1 payment processingGlobal / EU-U.S. DPF & EU SCCs
UseSendTransactional organizer OTP codes, event link emails & retention remindersHTTPS encrypted relay

6. Data Subject Rights, Self-Service Erasure & Procurement Counter-Signature

Instant Self-Service Deletion: At any moment during or after an event, the Controller can hide or permanently delete individual guest photos/messages in 1 click from the Host Studio or Moderator Console, or execute Delete Event in Host Studio to purge the entire event room and its media immediately without waiting for the automated expiry cron.

Vendor Onboarding & Signed Copy: You may print or save this page directly as a timestamped PDF for your compliance records. Corporate procurement or legal teams requiring a countersigned PDF copy or vendor questionnaire response may email support@photos.chat.

← Terms & ConditionsCorporate Photo Walls
Privacy & DPA inquiries: support@photos.chat