Data Processing Addendum

Version of January 1, 2027 · takes effect January 1, 2027

A new version takes effect on January 1, 2027.

This Data Processing Addendum ("DPA") is part of the agreement between Venvy Works, LLC ("Venvy") and the venue or organization using Venvy ("you"), made up of our Terms of Service and any order. It applies whenever Venvy handles personal information on your behalf. You don't need to sign anything separately: it takes effect when you accept the Terms.

The short version

  • You're in charge of your data. You decide what to collect from your users and attendees and why. We handle it only to run Venvy for you, and only as you instruct.
  • We keep it safe and confidential. Only people who need access have it, and they're bound to keep it private.
  • We tell you about problems fast. If there's a breach affecting your data, you hear from us without undue delay, and within 72 hours where we can.
  • We tell you who else is involved. We publish the companies that help us run Venvy, and give you notice before adding one.
  • We help you answer people. When someone asks to see, correct or delete their information, we help you do it.
  • When you leave, your data goes. You get 60 days to export it, then we delete it on a published schedule.

1. Scope, definitions and roles

1.1 Definitions. "Personal Data" means information about an identified or identifiable person that Venvy processes on your behalf as part of your data under the Terms. "Data Protection Laws" means the privacy laws that apply to that processing. These include the California Consumer Privacy Act (as amended by the CPRA) and similar US state laws, and, where they apply, the EU General Data Protection Regulation ("GDPR") and the UK GDPR. "Subprocessor" means a third party Venvy engages to process Personal Data. "Security Incident" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, or unauthorized disclosure of or access to Personal Data. Other capitalized terms have the meaning given in the Terms or the Data Protection Laws.

1.2 Roles. You are the controller (or "business") of Personal Data. Venvy is your processor (or "service provider"). Where you act as a processor for someone else, Venvy is your subprocessor, and you are responsible for passing on that party's instructions.

1.3 What this DPA doesn't cover. Information Venvy controls itself, such as administrators' sign-in and billing details and visitors to our websites, is covered by Venvy's Privacy Policy, not this DPA.

1.4 Details. Annex 1 describes the processing: whose data it is, what kinds, for what purposes, and for how long.

2. Venvy's commitments

2.1 Your instructions. Venvy will process Personal Data only on your documented instructions. Those instructions are the Terms, this DPA, and your settings and actions in Venvy. The only exception is where law requires otherwise, and then we'll tell you first unless the law forbids it. If we believe an instruction breaks Data Protection Laws, we'll tell you.

2.2 No other use. Venvy will not:

  • sell Personal Data or share it for cross-context behavioral advertising;
  • keep, use or disclose it for any purpose other than providing Venvy to you, or outside our direct business relationship with you;
  • combine it with personal information from other venues or from our own sources, except as needed to run the service and as Data Protection Laws allow;
  • use it to train AI models.

Venvy certifies that it understands and will comply with these restrictions, and will tell you if it can no longer meet its obligations under the CCPA.

2.3 Confidentiality. Everyone Venvy authorizes to process Personal Data is bound by a duty of confidentiality, and gets access only as their job requires. Venvy staff reach a venue's workspace only through a logged path, and only for the reasons set out in the Terms ("Uptime, security and privacy").

2.4 Security. Venvy will maintain the technical and organizational measures in Annex 2, appropriate to the risk. We may update them, but never in a way that materially lowers the protection of Personal Data.

2.5 Security Incidents. If Venvy becomes aware of a Security Incident, we will:

  1. notify your administrators without undue delay, and within 72 hours where practical;
  2. tell you what we know: what happened, the kinds and rough number of people and records affected, the likely consequences, and what we're doing about it, adding details as we learn them;
  3. take reasonable steps to contain it and reduce harm;
  4. help you meet your own duties to notify regulators and affected people.

You decide whether to notify regulators or individuals about your data, unless the law requires Venvy to notify them directly. A notice from Venvy is not an admission of fault.

3. Subprocessors

3.1 Authorization. You authorize Venvy to use the Subprocessors listed in Annex 3 and at venvy.works/legal/subprocessors.

3.2 Our duties. Before a Subprocessor processes Personal Data, Venvy will check that it can protect the data, and will bind it by written contract to data protection obligations at least as protective as this DPA. Venvy stays responsible to you for its Subprocessors' work.

3.3 Changes. Venvy will post a new or replacement Subprocessor at least 30 days before it starts processing Personal Data, and email administrators who subscribe to updates. In an emergency, such as replacing a provider that suddenly fails, we may give shorter notice and will explain why.

3.4 Objections. You may object to a new Subprocessor on reasonable data protection grounds within the notice period. We'll work with you in good faith to find a solution, such as a change in how your data is handled. If we can't, you may end the affected part of the service and get a refund of fees you prepaid for the unused time.

3.5 Services you connect. Services you or your users choose to connect, such as your own Square account, Canva, or your own Anthropic API key, are not Venvy's Subprocessors. You choose them, and their terms with you govern the data they receive.

4. Helping you meet your obligations

4.1 Requests from individuals. If a person asks to access, correct, delete, export or restrict their Personal Data, or to opt out, you can handle most of this yourself in Venvy. Where you can't, Venvy will help within a reasonable time, taking into account the nature of the processing. If a request reaches Venvy directly, we'll pass it to you without undue delay and won't answer it ourselves unless you ask us to or the law requires it. Your administrators can find a person by email, download that person's data, erase them, and export your whole venue, all from Privacy requests in Venvy.

4.2 Assessments and consultations. Venvy will give reasonable help with data protection impact assessments and any consultation with a regulator that you're required to carry out, to the extent it concerns Venvy's processing and you don't already have the information.

4.3 Showing compliance. On request, no more than once a year unless a regulator requires it or after a Security Incident, Venvy will:

  • answer a reasonable written security questionnaire;
  • share a summary of our security measures and any third-party assessments we hold, under confidentiality.

If that isn't enough to show compliance, or a regulator requires it, you may arrange an audit by an independent auditor bound by confidentiality, with at least 30 days' notice, during business hours, without disrupting the service or other venues' data. You'll cover your own costs, and Venvy's reasonable costs for audits beyond the first one each year.

4.4 Your responsibilities. You confirm that you have a lawful basis for the Personal Data you collect through Venvy, have given people the notices the law requires, including your own privacy policy and the purpose statement on each form, and will not instruct Venvy to process Personal Data in breach of Data Protection Laws. You'll follow the Terms' limits on sensitive information and children's information.

5. When the agreement ends

5.1 Export. For 60 days after your account ends, your administrators have read-only access to export Personal Data, as set out in the Terms ("Canceling").

5.2 Deletion. After that window, Venvy will promptly delete Personal Data from active systems, and it will age out of backups within 7 more days. While data sits in backups, it stays protected under this DPA and isn't used for anything else. Venvy may keep Personal Data only where the law requires it, and then only for as long and for the purposes required.

5.3 Confirmation. On request, Venvy will confirm in writing that deletion is complete.

5.4 Erasure records. When Venvy erases a person's Personal Data, whether on your instruction under Section 4.1 or at the end of the agreement under Section 5.2, it may keep a minimal record of the erasure: the date, a reference number, and a one-way hash of the person's email address. Venvy uses this record only to show that the erasure happened, and to repeat it if a backup is ever restored. It holds no other Personal Data, and Venvy protects it under this DPA.

6. US state privacy laws

For Personal Data covered by the CCPA and similar US state laws, Venvy is a "service provider" or "processor." Section 2.2 states its restrictions. You may take reasonable and appropriate steps to stop and remedy any unauthorized use of Personal Data, after notifying Venvy. Venvy will notify you if it determines it can no longer meet its obligations under those laws.

7. International transfers

7.1 Where data lives. Venvy and its Subprocessors process Personal Data in the United States.

8. General

8.1 Precedence. If this DPA conflicts with the Terms on the processing of Personal Data, this DPA wins. If the Standard Contractual Clauses apply and conflict with either, the Clauses win.

8.2 Liability. Each party's liability under this DPA is subject to the limits and exclusions in the Terms ("Warranties, liability and indemnities"), except where Data Protection Laws or the Standard Contractual Clauses do not allow that.

8.3 Changes. Venvy may update this DPA to reflect changes in law or in our Subprocessors, with notice as described in the Terms. No update will reduce the overall protection of Personal Data during your current subscription term.

8.4 Duration. This DPA lasts as long as Venvy processes Personal Data for you, including during the export and deletion periods in Section 5.

Annex 1: Details of processing

Parties. Data exporter (controller): the venue named in its Venvy account, contact: its administrators. Data importer (processor): Venvy Works, LLC, 4128 South Blvd, Suite A4, Charlotte, NC 28209, privacy@venvy.works.

Subject matter and nature. Hosting, storing, organizing, displaying, emailing and deleting Personal Data so the venue can schedule rooms and events, manage its people, publish pages and forms, and sell tickets.

Purpose. Providing Venvy to the venue under the Terms, including support, security, and fixing problems.

Duration. For the term of the agreement, plus the export and deletion periods in Section 5.

Frequency. Continuous.

People whose data is processedKinds of Personal Data
Venue users (staff, managers, team members, renters)Name, email, profile photo, role and permissions, team memberships, bookings and availability, sign-in sessions (IP address, browser), notification settings, actions recorded in the change history
Ticket buyersName, email, orders, tickets, check-ins, emails sent to them, refund history. Card details are collected by Square, not Venvy.
Form respondents and volunteersName, email, and whatever answers the venue's forms ask for
Waitlist membersName, email, quantity requested; for automatic purchase, a reference to a card saved at Square and the maximum amount authorized
Venue contacts shown publiclySeller name, support email and phone, postal address

Sensitive data. Venvy is not designed for sensitive data, and the Terms prohibit collecting government ID numbers, full card or bank numbers, passwords and detailed health information. Venues may collect limited sensitive answers, such as accessibility or dietary needs, through their forms. Venvy protects these with the same measures as all Personal Data (Annex 2).

Retention. As the venue configures and as Section 5 describes. Change history is kept for 365 days by default.

Annex 2: Security measures

These describe Venvy as built today. Bracketed items need confirming before publication; promise only what is true.

AreaMeasures
EncryptionTLS for all traffic between browsers and Venvy, and between Venvy and its providers. Data encrypted at rest by the database and storage providers (AES-256). API keys for connected services encrypted before storage.
Sign-inPasswords hashed with argon2. Sign-in, reset and verification tokens stored only as hashes. Sessions expire after 7 days of inactivity and 30 days at most. Repeated sign-in attempts rate-limited.
Access controlRole-based permissions inside each workspace. Every record carries its venue's identifier, and the database enforces row-level security, so each request can read and write only the rows of the venue it is for. Venvy staff reach a venue's data only through the Venvy staff console; viewing a venue's workspace as one of its users ("Shadow") is time-limited and logged. Production access limited to named Venvy staff, with multi-factor authentication required for the Venvy staff console and used on our hosting, database and source-code accounts. Staff access to a workspace logged.
LoggingAdministrative changes recorded in a change history, kept 365 days by default. Security-relevant events logged by the hosting provider.
EnvironmentsTest and preview deployments use their own database branches, copied from production, and never connect to the production database itself; that copied data stays under the same protections described here. Test environments share file storage with production; file deletions run only in production, so testing can't remove production files.
DevelopmentCode review and an automated security review before each release; dependency vulnerability checks; automated tests in continuous integration.
ResilienceManaged database with point-in-time recovery of up to 7 days; hosting across a provider's redundant infrastructure.
Incident responseBreach notice within 72 hours where practical (Section 2.5).
PaymentsCard data is collected on Square's hosted pages and never reaches Venvy's servers.

Annex 3: Subprocessors

The current list lives at venvy.works/legal/subprocessors; changes are announced as in Section 3.3.

SubprocessorWhat it doesPersonal Data involvedLocation
Vercel, Inc.Application hosting, scheduled jobs, image storage, page analyticsAll Personal Data in transit; uploaded images; page-view dataUS
Databricks, Inc. (Neon)Database hosting and backupsAll stored Personal DataUS (AWS US East 1, N. Virginia)
Plus Five Five, Inc. (Resend)Sending emailNames, email addresses, message content, kept under Resend's own retentionUS
Upstash, Inc.Rate limitingIP addresses and request countsUS (us-east-1, N. Virginia)
Block, Inc. (Square)Payment processing for Venvy subscriptionsVenue billing contact, card brand and last four digitsUS

Not Subprocessors, because the venue or its users choose and connect them: the venue's own Square account, Canva, Anthropic (with the venue's own API key), and Booked (for imports).

Section 3.3's notice process, and this DPA's plain-language summary, are adapted from the Basecamp open-source policies / CC BY 4.0.