VenueWSSub-processors
Last updated 28 October 2026. Provided in English; the English version governs.
These are the vendors that may process personal information on behalf of VenueWS customers. Each is bound by a written contract with obligations no less protective than our Data Processing Addendum, and we remain responsible for their performance.
We notify customers by email at least 30 days before a new sub-processor begins processing their data, and a customer may object on reasonable data-protection grounds. To receive those notices, or to ask a question about a vendor, write to hello@dmsworkspace.com.
1. Always in use
| Vendor | What it does | Data it sees | Where |
|---|---|---|---|
| Microsoft Azure | Hosting, compute, managed Postgres and backups — the service itself runs here. | All customer data at rest and in transit. | United States |
| Resend | Delivery of invitation emails, reminders, digests and account email. | Recipient name and email address, message content including the invitation QR image. | United States |
| PayPal | Subscription payments and invoices. | Billing contact and payment details. Card numbers go to PayPal directly and never reach us. | United States and globally |
2. Only when a customer turns it on
| Vendor | What it does | Data it sees | Where |
|---|---|---|---|
| Meta Platforms (WhatsApp Business Platform) | Delivery of invitation and reminder messages, for venues that enable WhatsApp. | Guest phone number, guest name, event and venue name, invitation link. | United States and globally |
| Eventbrite | Importing a guest list from a connected Eventbrite event. | Attendee names, emails and order references, pulled at the customer's direction. | United States |
| Google (Sheets API) | Importing a guest list from a connected spreadsheet. | Whatever the customer's sheet contains for the rows imported. | United States |
| Google (Wallet) | Issuing a wallet pass when a guest chooses to add one. | Guest name, event and venue name, pass identifier. | United States and globally |
| Apple (Wallet) | Issuing a wallet pass when a guest chooses to add one. | Guest name, event and venue name, pass identifier. | United States and globally |
| Anthropic (Claude API) | Reading imported guest and vendor lists (photos, PDFs, pasted text), and looking vendors' public business details up on the web, with the customer's own API key. | The file, photo or text the customer uploads — guest or vendor names and contact details as written there — and vendor business names. Guest data is never searched on the web. | United States |
| Zapier, Make | Sending event data to a customer's own automation, at their direction. | Only the fields the customer's own automation subscribes to. | United States and globally |
3. Our public pages only
| Vendor | What it does | Data it sees | Where |
|---|---|---|---|
| Google (Analytics) | Counts visits to our marketing pages and sign-up page. Advertising features and Google Signals are off; a browser sending Global Privacy Control is not tagged at all. | Page views, approximate region, referrer, analytics cookie id. Never loaded on a guest page, the scanner, or inside the signed-in app. | United States and globally |
See also our Privacy Policy, Terms of Service and Data Processing Addendum.