Planning Pod, Inc. · Version 1.0 · Effective 17 November 2026
1.1 What it is. This Data Processing Agreement ("DPA") is part of the Customer Agreement between Planning Pod, Inc. ("Planning Pod", "we" or "us") and the customer named on the Order Form ("you"). It covers personal information that we handle for you through the Planning Pod platform (the "Service", as defined in the Customer Agreement). Words with capital letters, such as Customer Data and Guests, have the meaning given in the Customer Agreement.
1.2 Our roles. You decide why and how personal information about your Users and Guests is collected and used. We handle it on your behalf to provide the Service. Under US state privacy laws, you are the "business" or "controller" and we are your "service provider" or "processor". Under Canadian privacy laws, you remain responsible for the personal information, and we handle it for you as your service provider.
1.3 What this DPA does not cover. It does not cover personal information we collect for our own purposes, such as billing details for your account, our marketing, or visitors to our website. Our Privacy Policy covers that.
1.4 Details. Attachment A describes the personal information, the people it is about and what we do with it. Attachment B describes our security measures.
2.1 Only on your instructions. We handle personal information only to provide, support and secure the Service, as described in the Customer Agreement and Attachment A, and as you otherwise instruct us in writing. The Customer Agreement and your use of the Service's settings are your instructions. If we think an instruction breaks the law, we will tell you.
2.2 US state privacy law promises. For personal information covered by the California Consumer Privacy Act and similar state laws, we will not:
We will give it the same level of privacy protection those laws require of you. We will tell you if we can no longer meet our obligations under those laws. You may take reasonable steps to make sure we use the information in line with this DPA, and to stop and fix any use that is not allowed.
2.3 Improving the Service. As those laws allow, we may use personal information to maintain and improve the Service, including internal analysis to develop and test new features, but not using email or calendar data received from Google accounts. We will not use it to build profiles for, or provide services to, another business. We do not use Customer Data to train the AI models that run in the Service.
3.1 Our people. Our staff and vetted contractors may access personal information to provide, support and secure the Service, and are bound by confidentiality obligations. Only staff who need it for their work can view customer accounts in our staff tools, staff roles limit what each person can change, and staff must use two-step login. Engineers who run the Service can access the database directly. Staff do not read email or calendar data received from a User's Google account unless that User asks us to, it is needed for security, or the law requires it. Support staff can sign in as one of your Users to help you; each time they must give a reason, the session ends after 30 minutes, and it is logged. We do not notify you of each access.
3.2 Outside companies. We use outside companies ("subprocessors") to help provide the Service. The current list, with what each one does and where it handles data, is at planningpod.com/legal/subprocessors. We have written agreements with each that require them to protect personal information as the law requires, and we are responsible for their work.
3.3 New outside companies. We will give you at least 30 days' notice, by email and on the list page, before a new outside company starts handling personal information. If you have a reasonable objection based on data protection, tell us within that time. We will try to resolve it. If we cannot, you may end the Customer Agreement and we will refund prepaid fees for the rest of your term.
3.4 AI processing. PodPilot sends the information it needs to handle a request to AI models that we use through Amazon Bedrock, Amazon's managed AI service, in US regions. That information can include personal information. Anthropic, which makes the Claude models, does not receive it. Amazon handles it as our hosting provider, and neither Anthropic nor Amazon uses it to train AI models.
4.1 Security. We keep the technical, physical and organizational safeguards described in Attachment B. We may update them over time, but we will not make them materially weaker.
4.2 Breaches. If we become aware of a breach of security that has led, or that we reasonably believe has led, to personal information we handle for you being lost, changed, disclosed or accessed without permission, we will tell you without undue delay, and no later than 72 hours after we become aware of it, or sooner if the law requires. Our first notice may be short, and we will send updates as we learn more. Unsuccessful attempts, such as blocked sign-ins or scans, are not breaches. We will not notify affected people or regulators on your behalf unless you ask us to or the law requires it. We will tell you what we know, including what happened, what information was involved and what we are doing about it, and keep you updated.
4.3 Helping you respond. We will take reasonable steps to contain the breach and will help you with notices you must give to individuals or regulators. Telling you about a breach is not an admission of fault.
5.1 Requests from individuals. If someone asks to see, correct or delete their information, you can update their details, mark them inactive or remove them from an event in the Service. For requests the Service can't handle, tell us in writing which person and what you need us to do, and we will do it within 30 days, by hand if needed, except where the law requires us to keep the information. If someone contacts us directly about information we hold for you, we will pass the request to you and will not answer it ourselves unless you ask us to or the law requires it.
5.2 Where data is stored. We store Customer Data in the United States, in Amazon Web Services data centers in Oregon, Ohio and Virginia. We do not offer storage in other countries. Adyen, our payment partner, stores payment data in the European Union by default and may handle it in other regions. Some outside companies on our list may reach data from other countries, as the list shows.
5.3 Requests from authorities. If a government or court asks us for personal information we hold for you, we will tell you first, unless the law does not allow us to, and will give only what we are legally required to give.
5.4 When the Customer Agreement ends. For 30 days after the Customer Agreement ends, you can use the Service's export tools, which cover reports and records but not every type of data. We keep personal information after that until you ask us to delete it, and will confirm the deletion in writing if you ask. If you ask in writing, we will delete it from our live systems within 90 days of your request, and backup copies will expire within 35 days after that, and earlier versions of files within 90 days. Some security logs are kept for set periods, such as sign-in events for 400 days and firewall logs for 90 days. We may keep what the law requires, and a log of changes made in your account.
5.5 Reviews. We will give you the information you reasonably need to show you are meeting your own privacy obligations under the laws that apply to you. If you are on an Enterprise plan, we will also answer a reasonable written security questionnaire from you once a year, or after a breach. We do not currently hold a security certification such as SOC 2.
If you are in Canada, or handle personal information of people in Canada through the Service:
7.1 Liability. Each party's liability under this DPA is subject to the limits in the Customer Agreement.
7.2 If documents conflict. On how we handle personal information, this DPA controls over the rest of the Customer Agreement and over our Privacy Policy. A Public Sector Addendum, where one applies, controls over this DPA.
7.3 Student records. If you are a school, college or university subject to the US Family Educational Rights and Privacy Act (FERPA) and put student education records into the Service, you designate us as a "school official" with a legitimate educational interest, providing a service you would otherwise use your own staff for. We will be under your direct control in how we use and maintain those records; use them only to provide the Service; not disclose them to anyone except our outside providers, who are bound by the same limits, or as the law allows; refer any request for them, including a subpoena, to you (section 5.3); and not use them to train AI models. You are responsible for listing contractors as school officials in your annual FERPA notice.
7.4 How long it lasts. This DPA lasts as long as we hold personal information for you, including after the Customer Agreement ends.
7.5 Changes. We may update this DPA as described in section 17.3 of the Customer Agreement. We will not make changes that materially reduce the protection of personal information, unless the law requires it.
| Item | Details |
|---|---|
| People the information is about | Your Users; your Guests, including clients, event attendees, people who RSVP, sign documents or pay you; your contacts, vendors and leads |
| Types of information | Names, email addresses, phone numbers, postal addresses; event, booking, RSVP, seating, meal and dietary details; messages, notes, emails synced from connected mailboxes, calendar events and uploaded files; signatures with IP address, browser details and time; invoices, payment amounts and limited card details (brand, last four digits, expiry); PodPilot conversations and saved notes about Users; activity and session recordings in the Service |
| Sensitive information | Not required by the Service. Health details such as allergies or accessibility needs, and information about children, may be entered by you or your Guests in notes, forms or uploads |
| What we do with it | Host, store, display, search, export and back it up; send emails; create PDFs; process payments through Adyen; run PodPilot and other AI features; sync connected email and calendars; provide support; secure and monitor the Service |
| How long | For as long as the Customer Agreement lasts, and after that until you ask us to delete it (section 5.4) |
| Where | United States (Amazon Web Services in Oregon, Ohio and Virginia); payment data with Adyen in the European Union and other regions; see planningpod.com/legal/subprocessors |
Encryption
Access
Monitoring and logging
Backups and resilience
Payment data