Planning Pod, Inc. · Version 1.0 · Effective 17 November 2026
1.1 Who we are. Planning Pod, Inc. ("Planning Pod", "we" or "us") makes software that venues use to manage events, bookings and payments. Our address is 301 Remington St., Fort Collins, CO 80524, USA.
1.2 What this policy covers. This policy explains how we handle personal information on our website, planningpod.com, and on the Planning Pod platform (the "Service"), including the pages venues share with their clients and guests, such as proposals, payment pages, RSVP pages and client portals.
1.3 Information we handle for venues. Venues decide what information they collect about their clients and guests and how they use it. For that information, we act as the venue's service provider, and the venue's own privacy policy applies. If you are a venue's client or guest, please contact the venue with questions about your information. We will help the venue respond.
1.4 Information we handle for ourselves. We decide how to use the contact, account, billing and support details of our customers' account owners and users, and information about our website visitors and people who contact us or receive our marketing. This policy explains how.
2.1 From venues and their staff. Account and contact details (name, email, phone, business name and address), billing details, and everything users enter in the Service, such as events, bookings, contracts, messages, notes, files and PodPilot conversations. If a user connects a Gmail, Outlook or iCloud account, we also sync their email and calendar.
2.2 From clients and guests, on behalf of venues. Information people enter on venue pages, or that the venue enters for them, including:
2.3 From website visitors. Information you give us in forms, such as your name, email and company, and information collected by cookies and similar tools (section 4).
2.4 Collected automatically. When anyone uses the Service or our website, we collect technical information such as IP address, browser and device details, pages viewed, actions taken, errors, and sign-in events. On venue inquiry forms we also collect the marketing source and ad click identifiers, and store the IP address only in scrambled form.
2.5 Sensitive information. The Service doesn't ask for sensitive information. People can still enter it, for example allergies or accessibility needs in notes and forms. Please don't enter government ID numbers or passwords, and enter full card or bank numbers only in the secure payment form.
3.1 To provide the Service. To run accounts, store and show event information, send emails, create documents, process payments through Adyen, sync connected email and calendars, and provide support.
3.2 To keep it secure. To prevent fraud and abuse, protect accounts, and investigate problems.
3.3 To run PodPilot. PodPilot, our AI assistant, 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 can include names, emails, notes, messages and the contents of uploaded files. Anthropic, which makes the Claude models, does not receive it. Amazon handles it as our hosting provider, and it is not used to train AI models. We do not use customer data to train the AI models that run in the Service.
3.4 Analytics and session recordings. We use PostHog and Sentry to understand how the Service is used and to fix errors. Both record some sessions. Anything people type into fields is hidden in these recordings, but they can show other information displayed on the page, including on client portals.
3.5 To communicate. To send service messages, such as account and billing notices, and marketing about our products to customers and prospects, which anyone can opt out of.
3.6 To improve the Service. To analyze use internally and develop and test new features. This does not include email or calendar data from Google accounts (section 8.2).
3.7 For legal reasons. To meet legal obligations, enforce our agreements, and protect rights and safety.
4.1 In the Service. We use our own cookies to keep you signed in, protect sign-in and remember your preferences. Guest pages use short-lived access cookies, for example RSVP access for 14 days. PostHog sets an analytics cookie that lasts one year. Adyen's fraud-check script runs on payment pages and may set its own cookie. Font Awesome, Google Fonts and jsDelivr load on our pages and see visitors' IP addresses. The Service's own pages have no advertising trackers; the inquiry form script described in section 4.2 reads advertising cookies on venues' websites.
4.2 On venues' websites. If a venue adds our inquiry form to its own website, our script sets a 30-day cookie there to record how the visitor arrived, and reads Google and Meta advertising cookies so the venue can see which ads led to an inquiry. The script honors Global Privacy Control, a browser setting that signals you don't want to be tracked.
4.3 On our website. We use Google Analytics to understand how visitors use planningpod.com, and Google Ads and other advertising tools to measure and show our ads. These tools use cookies and similar technology. To opt out of ads based on your activity, use Google's ad settings and opt-out tools, or block cookies in your browser (section 4.4).
4.4 Your browser settings. Most browsers let you block or delete cookies. If you block the Service's own cookies, you won't be able to sign in.
5.1 Venues. Information clients and guests enter on a venue's pages goes to that venue.
5.2 Outside companies that work for us. Companies that help us run the Service, such as Amazon Web Services for hosting and AI, Nylas for email and calendar sync, and PostHog and Sentry for analytics and error reports. They may use the information only to provide their service to us. The full list is at planningpod.com/legal/subprocessors. For information we hold for our own purposes, we also use business tools such as our customer relationship, email, billing and support systems.
5.3 Adyen. Our payment partner receives payment details and venues' identity and bank details to process payments and meet its legal obligations. Adyen's own privacy notice also applies.
5.4 For legal reasons. When the law requires it, or to protect rights, safety and the Service.
5.5 If our business changes hands. As part of a merger, acquisition or sale of assets, with protections for your information. Information received from Google accounts is transferred only with users' consent where Google's rules require it.
5.6 We don't sell personal information. We don't sell personal information for money or rent it out. Our website uses Google advertising tools; section 4.3 explains how to opt out.
6.1 Where. We store information in the United States, with Amazon Web Services in Oregon, Ohio and Virginia. Adyen stores payment information in the European Union by default and may handle it in other regions. Some outside companies may access information from other countries. If you are outside the United States, your information will be handled in the United States, where it may be available to authorities under US law.
6.2 How long. We keep account and Service information while the customer's account is open, and after that until the customer asks us to delete it. Once asked, we delete it from our live systems within 90 days, and backups expire within 35 days after that. Some records last for set periods: application and AI request logs 30 days, firewall logs 90 days, sign-in security events 400 days. A log of changes to records, and records the law requires, such as tax and payment records, are kept longer. PodPilot conversations are kept with the rest of the customer's data; removing a conversation in the Service hides it rather than deleting it. Earlier versions of files are kept for 90 days. Marketing contacts are kept until you opt out; after that we keep only your email address on a do-not-contact list so you aren't added again.
6.3 Security. We encrypt information when it is stored and when it is sent over the internet, limit access to customer accounts to staff who need it for their work, require staff to use two-step login, log support access to customer accounts, and keep backups. No system is perfectly secure, but we work to protect your information and will notify our customers about a breach, and the people affected where we hold their information for our own purposes, as the law requires.
7.1 Marketing. You can unsubscribe from our marketing emails at any time using the link in each email. We will still send service messages about your account.
7.2 US state privacy rights. Depending on where you live, including California, Colorado, Connecticut, Virginia, Texas and other states with privacy laws, you may have the right to:
To make a request, email support@planningpod.com with "Privacy request" in the subject line. We will confirm your identity before acting. An authorized agent may make a request for you with your written permission. If we decline your request, you may appeal by replying to our decision, and we will answer within the time the law allows.
7.3 Canada. If you are in Canada, you may ask to see and correct your personal information, and you may withdraw your consent to our use of it, subject to legal and contract limits. If you are not satisfied with our answer, you may complain to the Office of the Privacy Commissioner of Canada or your provincial privacy commissioner, including Quebec's Commission d'accès à l'information.
7.4 Clients and guests of venues. If your information was collected by a venue using our Service, please send your request to the venue. If you contact us, we will pass your request on to the venue.
8.1 Children. Our website and Service are meant for businesses, and accounts are for people 18 and older. We don't knowingly collect personal information from children under 13 for our own purposes. Venues may enter information about children attending their events; the venue is responsible for having the right to do so.
8.2 Google user data. If a user connects a Google account, Planning Pod's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use that information only to show, send and organize the user's email and calendar in the Service and to answer the user's requests in PodPilot. We don't use it for advertising, don't sell it, and don't use it to develop, improve or train generalized AI or machine learning models. Our staff don't read it unless the user asks us to, it is needed for security, or the law requires it.
8.3 Changes to this policy. We will post any changes on this page with a new "last updated" date, and keep past versions at planningpod.com/legal/archive. For material changes, we will also notify customers by email and in the Service at least 30 days before they take effect.
8.4 Contact us. Email support@planningpod.com with "Privacy" in the subject line, or write to: Privacy Officer, Planning Pod, Inc., 301 Remington St., Fort Collins, CO 80524, USA. Our person responsible for privacy is our Head of Operations.