Privacy Policy

1. Who this policy covers, and our role

This policy applies to information we handle in two different capacities:

• As a controller — for information we collect about our Customers and their authorized users (for example, account registration, billing, and support), and for operating and securing the Service. This is the information we decide how to use.

• As a service provider / processor — for the personal information that a Customer uploads to or generates in the Service about its own clients, event contacts, venue partners, and vendors (we call these individuals “End Users”). We process this information on the Customer’s behalf and under its instructions, to provide the Service. The Customer — not Panko — decides what End-User information to collect and why.

If you are an End User (for example, someone who submitted an event or catering inquiry, is named on an event, or signs a contract through Panko), the venue, caterer, or event business you are dealing with is responsible for that information. Please direct privacy questions and requests to that business. We will refer you to them and support their handling of your request. Sections 2–4 below describe the categories of information involved either way; Sections 8–10 describe your choices.

We serve customers in the United States, and the Service is intended for use in the United States only.

2. Information we collect

2.1 Information Customers and their users provide

• Account and profile information — name, business name, email address, phone number, mailing address, job role, and login credentials for the individuals who administer or use a Customer account (owners, staff, team members).
• Business and legal-entity details — information a Customer provides about the legal entity(ies) it invoices from, such as legal name and taxpayer identification number (EIN).
• Billing information — the contact and billing details we need to invoice a Customer for the Service, and records of the plan and payments. (See Section 6 for payment processing.)
• Support and communications — information you provide when you contact us, respond to a survey, or otherwise communicate with us.

2.2 Information about End Users, provided or generated through the Service

When a Customer uses the Service, the following categories of information about its clients, event contacts, venue partners, and vendors may be stored and processed in Panko:

• Contact details — first and last name, email address(es), phone number(s), and mailing or billing addresses.
• Event, booking, and inquiry details — event type and dates, guest counts, venue names and addresses, spaces/resources booked, service preferences, budget-related notes, preferred contact method, and free-text notes.
• Dietary information — dietary restrictions and allergen information associated with an event or its guests, which a Customer may collect to plan and safely serve food.
• Messages and files — email and in-app messages exchanged through the Service, message threads, attachments, and files uploaded to an event or account (for example, floor plans, menus, or reference documents).
• Orders, quotes, and invoices — menu selections, order and quote details, pricing, and invoice records (such as invoice number, amount due, and due date).
• Payment records — for payments an End User makes to a Customer through the Service: amount, date, status, payment method type (for example, card vs. bank transfer, and whether a card is a credit or debit card, which determines whether any Customer-configured card surcharge applies), and any surcharge or discount amount. Full card numbers and bank credentials are handled by Stripe, not Panko — see Section 6.
• Contracts and e-signatures — catering, venue, and event agreements sent for signature, signer identity and contact details, signature/audit records (including a certificate of evidence), and any preferences captured during signing (such as an optional marketing opt-in choice).
• Scheduling and consultations — consultation and appointment bookings, calendar entries, and video-call links.
• Venue- and vendor-partner submissions — information a venue or vendor partner submits when referring or handing off an inquiry to a Customer.

The specific fields are determined by each Customer through the forms and features it chooses to use.

2.3 Information we collect automatically

When anyone uses the Service, we and our infrastructure providers automatically collect limited technical information needed to operate, secure, and troubleshoot it:

• Log and device data — IP address, browser and device type, pages or screens accessed, and timestamps.
• Security data — signals used to detect and prevent fraud, spam, and abuse, including data (such as your IP address) processed by our bot-protection provider (Cloudflare Turnstile) on public forms.
• Address autocomplete — when you type an address into an address field, the text you type is sent to Google Maps Platform (Places) to suggest and format U.S. addresses. Google’s privacy policy applies to its processing of that input.
• Essential cookies and similar technologies — used to keep you signed in, remember your preferences, and maintain the security and integrity of the Service. We do not use advertising cookies or sell information collected through cookies, and we do not use the Service to track you across other websites for advertising.

2.4 Information from third parties and integrations

If a Customer chooses to connect a third-party service, we receive information from that service to provide the requested feature. For example, if a Customer connects QuickBooks Online we receive accounting-related data from Intuit; if a Customer connects Stripe to accept payments we receive payment and payout status; if a Customer connects a scheduling provider we receive booking details; if a Customer connects Google Calendar we receive the connected Google account’s email address and the list of calendars it can write to; and if a Customer uses e-signature features we receive signer and signature records. We also receive email delivery status (such as bounces) from our email provider and, where an email address is checked, an assessment of whether its mailbox appears to exist (Section 5.7). See Section 5 for details on each integration.

3. How we use information

We use information to:

• Provide, maintain, and improve the Service — including managing accounts, storing and displaying Customer content, sending and receiving messages, generating quotes, invoices, and contracts, managing bookings and events, and enabling integrations the Customer turns on.
• Communicate — send transactional and service messages (for example, inquiry notifications, invoice reminders, appointment confirmations, and account or security notices). Some of these messages are sent by Customers to their End Users through the Service.
• Secure the Service — authenticate users, enforce permissions, detect and prevent fraud, abuse, and unauthorized access, and maintain backups and audit records.
• Support — respond to questions and troubleshoot problems.
• Billing — invoice Customers and keep records of payments for the Service.
• Comply with law — meet our legal, tax, and regulatory obligations, and enforce our agreements.
• Improve and develop — understand how the Service is used and develop new features. When we use information for product improvement, we use aggregated or de-identified data where practicable.

We do not sell personal information, and we do not share personal information for cross-context behavioral advertising. We do not use End-User information for our own marketing.

4. How and when we share information

We share information only as described below:

• With your organization — information in a Customer account is accessible to that Customer’s authorized users according to the permissions the Customer configures.
• At the Customer’s direction — for example, when a Customer sends a message, quote, invoice, or contract to an End User, or connects an integration.
• Service providers (subprocessors) — third parties that host and support the Service under contracts that require them to protect the information and use it only to provide services to us. See the current list in the Appendix.
• Integrations you enable — such as QuickBooks Online, scheduling, and e-signature providers, as described in Sections 5.1–5.3 and 5.6. Information flows to these services only when a Customer connects them.
• Legal and safety — when we believe disclosure is reasonably necessary to comply with a law, regulation, legal process, or governmental request; to enforce our terms; or to protect the rights, property, or safety of Panko, our Customers, or others.
• Business transfers — in connection with a merger, acquisition, financing, reorganization, or sale of assets, subject to the surviving entity honoring this policy.

5. Integrations you connect

Customers can connect optional third-party services. Information flows to these services only when a Customer connects and configures them, and each service’s own terms and privacy policy also apply to the Customer’s use of it. Sections 5.4, 5.5 and 5.7 instead describe providers that Panko itself uses to run parts of the Service; they process information on our behalf as subprocessors (Appendix).

5.1 QuickBooks Online (Intuit)

• Authorization. We access QuickBooks data only after the Customer authorizes the connection through Intuit’s standard OAuth 2.0 flow. We request a single authorization scope — com.intuit.quickbooks.accounting (accounting data). We do not request access to Intuit payroll, payments, or user-profile data. We never ask for or store QuickBooks (Intuit) login credentials; Intuit provides us with time-limited access tokens, which we store encrypted at rest.
• What we access. Solely the accounting objects needed to keep the Customer’s books in sync with Panko: we create or update customers, items/products-and-services, accounts, invoices, and payments in the Customer’s QuickBooks company, and we read company preferences (such as tax and class-tracking settings), tax codes, classes, the company name, and invoice status. Data we send to QuickBooks is limited to what an invoice needs — for example a customer display name, invoice number, dates, line amounts and descriptions, and the invoice recipient’s email address for QuickBooks’ billing-email field.
• Change notifications. If Intuit sends us webhook notifications about invoice or payment changes in the connected company, we verify and use them only to keep already-synced records current; changes to records we did not create are ignored.
• Why we access it. We use QuickBooks data solely to provide the features the Customer requests — keeping invoices, customers, and payment status in sync between Panko and the Customer’s QuickBooks Online company. We do not use QuickBooks data for advertising, we do not sell it, and we do not share it except with the subprocessors that host our Service (Appendix) or as required by law.
• Storage and retention. We store the minimum QuickBooks data necessary to provide the integration — encrypted tokens, record-mapping identifiers, sync status, and change notifications — and retain it in line with Section 7 and Intuit’s developer requirements.
• Disconnecting. A Customer can disconnect QuickBooks at any time from within Panko, or from Intuit (Settings → Apps / Connected apps in QuickBooks Online). Disconnecting revokes and deletes our access tokens and stops all syncing. We retain the non-sensitive record-mapping identifiers so that if the Customer later reconnects the same QuickBooks company, existing records pair back up instead of being duplicated; a Customer can request full deletion.
• Intuit’s terms. Use of the QuickBooks integration is also subject to Intuit’s terms and privacy notices. Our use of Intuit APIs and data complies with the Intuit Developer terms.

5.2 Scheduling (calendar and video calls)

If a Customer connects a scheduling provider (currently cal.com), the Customer connects its own cal.com account by providing its cal.com API key, which we store encrypted at rest. Booking itself happens on the provider’s scheduling pages; the provider then notifies Panko of bookings, reschedules, and cancellations, and those notifications include attendee details (name, email address, time zone, and responses to booking questions) and any video-call link the provider generates, which we store to show appointments in the Service. Any calendar the Customer connects inside its scheduling account — such as Google Calendar or Microsoft Outlook — is connected there, under the Customer’s own account and those providers’ terms; Panko does not access calendars connected that way. Panko’s own, separate Google Calendar integration is described in Section 5.6.

5.3 Electronic signatures

If a Customer uses e-signature features (currently via BlueInk), we send the e-signature provider each signer’s name and email address and the document to be signed, and receive back signing status, the completed document, a certificate of evidence, and the values of fields completed during signing. Signing is embedded in the Service — the e-signature provider does not email or contact signers directly. Signed documents and evidence records are stored in the Service’s file storage as part of the Customer’s records. See Section 8 of the Terms of Service for how electronic signatures work and each party’s responsibilities.

5.4 Email

We use Resend to send and receive email on behalf of Customers. Email addresses, message content and attachments, and delivery status (such as bounces) are processed to deliver and manage those messages, including inbound replies routed back into the Service.

5.5 Address autocomplete

Address fields in the Service use Google Maps Platform (Places) to suggest and standardize U.S. addresses as you type; the text entered in those fields is sent to Google for that purpose (see Section 2.3).

5.6 Google Calendar

A Customer’s administrator can connect a Google account so that Panko keeps the Customer’s events on Google calendars the administrator chooses. Information flows one way, from Panko to Google: Panko publishes its own events to those calendars and does not import or read the rest of the Customer’s calendar.

• Authorization. We access Google only after an administrator authorizes the connection through Google’s standard OAuth 2.0 consent screen. We request these scopes: openid and email (to identify which Google account was connected); calendar.calendarlist.readonly (to list the calendars the account can write to, so the administrator can pick destinations); and calendar.events (to create, update, and delete the events Panko publishes). We never ask for or store Google passwords. Google provides us with access and refresh tokens, which we store encrypted at rest.
• What we read. The connected account’s Google account ID and email address; each writable calendar’s ID and name; and, for events Panko itself created, the event’s title, location, times, and status, which we read back only to detect and repair changes made to those events in Google. We do not list, read, or store any other events on the Customer’s calendars.
• What we write. For each Panko event matching a chosen destination, we create one Google event containing a title (for example, the client’s name and the event type), the location (such as the venue name), the date and time, private internal identifiers, and a plain-text description. The description names the Customer’s brand and, for client events, the estimated guest and kid counts, the date the client’s contract was signed, and each account holder’s name, phone number, and email address. An administrator chooses, per calendar, whether it receives approved events, approved events and drafts, or drafts only. We do not add attendees or send invitations. We update or remove that Google event when the Panko event changes or is cancelled.
• What we store. Encrypted tokens and their expiry, the Google account ID and email address, the chosen calendars’ IDs and names, the IDs of the Google events we created, and sync and health status. We do not store copies of Google calendar content.
• Who sees it. The connected Google email address and calendar names are shown only to the Customer’s administrators, in the Service’s calendar settings. The events we write, including client contact details in their descriptions, are visible to whoever the Customer shares those Google calendars with; the Customer controls that sharing in Google. We do not sell Google user data, use it for advertising, use it to train or improve generalized AI or machine-learning models, or allow humans to read it, except with the Customer’s consent, for security purposes, to comply with law, or when it is aggregated and anonymized for internal operations. We do not share it with anyone except the subprocessors that host our Service (Appendix) or as required by law.
• Disconnecting. An administrator can disconnect Google at any time from the Service. Disconnecting stops syncing, deletes the events Panko created from the chosen calendars, and then deletes our access and refresh tokens. You can also remove Panko’s access from your Google Account at myaccount.google.com/permissions. After a Google account is disconnected or a calendar is removed, we keep the account’s email address and the calendars’ IDs and names for 30 days, so that an accidental disconnect can be undone by reconnecting, and then delete them automatically.
• Google API Services User Data Policy. Panko’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.

5.7 Email address checks

Panko checks whether an email address looks able to receive mail. Panko’s own checks look only at the address’s format and its domain, and can refuse some addresses (for example, a malformed address, one on a known disposable-email domain, or one at a domain that cannot receive mail). To check further whether the mailbox exists, Panko’s servers send the email address to Bouncer (Bouncer Sp. z o.o.) when a Customer’s staff enter or change an email address in the Service (for example on a contact, an invitation, or a team member), and after a public or partner inquiry has been submitted and accepted. We do this to provide the Service on the Customer’s behalf, so that its staff can catch a mistyped address before relying on it.

• What is sent. The email address only, from Panko’s servers. No name, message, or other record is sent with it, and your browser never contacts Bouncer.
• What comes back. Bouncer’s assessment of whether the mailbox appears to exist. Panko keeps that result only briefly, except that for an accepted inquiry it may be kept as a note for the Customer’s staff to review. Bouncer’s result is advice: it never stops staff from saving an address or an inquiry from being submitted, and it does not show who owns or controls a mailbox.
• What is not checked. Signing in never sends your address to Bouncer.
• Where. Bouncer processes these checks in the European Union (see Section 9).

6. Payments (Stripe Connect)

Panko integrates with Stripe to let Customers accept payments from their own clients (for example, event deposits and invoices), using Stripe Connect with Standard connected accounts. This means:

• The Customer has its own Stripe account. To accept payments, a Customer creates or connects a Stripe account and agrees to Stripe’s terms directly; the Customer manages payments, payouts, and refunds primarily through the Stripe Dashboard.
• Stripe collects and stores payment details. Card, bank, and other payment credentials are collected and processed by Stripe on its own PCI-compliant systems and are governed by Stripe’s privacy policy. Panko does not collect or store full payment card numbers or bank account credentials.
• What Panko receives. Panko receives limited payment information from Stripe — payment status, amounts, dates, non-sensitive identifiers, account onboarding/verification status, and the payment method’s type (for example, whether a card is credit or debit, which determines whether a Customer-configured card surcharge applies) — to display payment status in the Service, apply the Customer’s payment pricing settings, and reconcile invoices. Panko also receives and retains Stripe’s event notifications (webhooks) about these payments and accounts.
• Surcharges and discounts. If a Customer enables a card surcharge or bank-payment discount, the adjusted total and a disclosure (for example, “Includes a N% card surcharge”) are shown to the payer before they confirm payment.
• Separate from Service fees. This is separate from any fees a Customer pays Panko for the Service, which are described in the Terms of Service. Panko does not add a platform fee to payments processed through a Customer’s Stripe account.

Stripe is listed in the Appendix.

7. Data retention

We retain information for as long as a Customer’s account is active and as needed to provide the Service. When a Customer closes its account, we delete or de-identify Customer content within a commercially reasonable period, except where we must retain it to comply with legal, tax, or accounting obligations, resolve disputes, enforce our agreements, or maintain security (for example, backups from which data is purged on a rolling basis). Customers control the retention of individual records within their account and may delete them through the Service. End Users seeking deletion should contact the relevant Customer (see Section 1).

8. Security

We use administrative, technical, and physical safeguards designed to protect information, including:

• Encryption of data in transit (TLS) and encryption of data and access tokens at rest;
• Role- and relationship-based access controls that limit who within a Customer account can see each record, and that separate one Customer’s data from another’s (multi-tenant isolation);
• Least-privilege access for our personnel and audit logging of sensitive actions;
• Reputable infrastructure providers with recognized security programs (see Appendix); and
• Ongoing monitoring for vulnerabilities and abuse.

No method of transmission or storage is completely secure, and we cannot guarantee absolute security. Customers are responsible for maintaining the confidentiality of their login credentials and for configuring user permissions appropriately.

9. Where information is stored

We store and process information in the United States. Our infrastructure providers may maintain redundant facilities within the United States for reliability and backup. The one exception is the email address checks described in Section 5.7: the email addresses sent for those checks are processed by Bouncer in the European Union.

10. Your choices and rights

Account users. You can access and update your account and profile information within the Service or by contacting us. You can opt out of non-essential emails using the unsubscribe link; we will still send transactional and account/security messages you need to use the Service.

U.S. state privacy rights. Depending on your state of residence, you may have rights to request access to, correction of, or deletion of personal information about you, to obtain a copy of it, and to not be discriminated against for exercising these rights. Because personal information about End Users is controlled by our Customers, we will forward your request to the relevant Customer and assist them, or act on their instructions. For information we control (Section 1), you may submit a request using the contact details below; we will verify your request before acting on it. We do not sell personal information or share it for cross-context behavioral advertising, and we do not use it to make decisions that produce legal or similarly significant effects about you.

You may designate an authorized agent to make a request on your behalf; we may require verification of the agent’s authority.

11. Children’s privacy

The Service is intended for business use by adults. It is not directed to children, and we do not knowingly collect personal information directly from children under 18. If you believe a child has provided information to us directly, please contact us and we will take appropriate steps to delete it. Customers are responsible for any information about event guests they choose to enter.

12. Third-party links and services

The Service may link to or interoperate with third-party websites and services that we do not control. Their privacy practices are governed by their own policies, and we are not responsible for them.

13. Changes to this policy

We may update this policy from time to time. If we make material changes, we will update the “Last updated” date above and, where appropriate, provide additional notice (for example, by email or an in-app notice). Your continued use of the Service after an update means you accept the revised policy.

14. Contact us

Questions, concerns, or privacy requests:

Megamind Management LLC
Attn: Privacy
Email: privacy@panko.events

If you are an End User with a question about information a venue, caterer, or event business holds about you, please contact that business directly.

Appendix — Subprocessors

We use the following service providers to operate the Service. Each processes information only to provide services to us and under confidentiality and data-protection obligations. This list may change; we will update it when it does.

We do not use third-party analytics, advertising, or session-recording services in the Service.

Where a Customer connects its own Google or Microsoft calendar inside a scheduling provider, that connection is between the Customer and those providers under their terms; Panko does not access calendars connected that way (Section 5.2). Panko’s own Google Calendar integration is described in Section 5.6. Similarly, under Stripe Connect, the Customer contracts with Stripe directly and Stripe acts as an independent payment processor for the Customer’s transactions.