Data Processing Agreement · version 2026-11-16
Counsel review draft • November 14, 2026
This Data Processing Agreement (DPA) is between Incassia, LLC and the planning business identified in its accepted order or beta enrollment (Planner). It takes effect when the Planner’s authorized representative accepts the identified version with the Terms of Service or Beta Participation Agreement, or when both parties sign it. Incassia and the Planner must each keep a copy. This DPA controls any conflict about the processing of personal data on the Planner’s behalf.
Planner Data means personal data that Incassia processes on the Planner’s behalf, including workspace content, data received through planner-directed links and forms, and approved migration or support copies. The Planner acts as controller or business when it determines the purposes and means of processing. Incassia acts as its processor or service provider. When the Planner acts for another controller, it must have authority to appoint Incassia as a subprocessor and convey the controller’s lawful instructions. Each party will meet the obligations applicable to its actual role. Incassia separately determines how it uses account administration, its own subscription billing, business inquiry and site marketing records, as described in the Privacy Policy. Workspace contact lists and booking records remain subject to this DPA.
Documented instructions include the accepted agreements, the Planner’s selections within features, and lawful written directions from the Planner. If Incassia reasonably believes an instruction violates applicable law, it will promptly tell the Planner and may pause that instruction pending clarification. For a binding legal demand, Incassia will give advance notice if permitted, disclose only what the law requires and document the disclosure.
Data subjects include planner users, couples, guests, vendors and staff, including children identified by an adult in event records. Data includes names and contact information, RSVPs, seating, meal and accessibility requests, contracts, signatures and related signing records, invoices, budgets, timelines, forms, correspondence, prompts and uploaded files. The Planner determines what is necessary. It will provide required notices, obtain permissions and any consent the law requires, and tell recipients how to exercise their rights. An allergy, accommodation or dietary request can reveal health or religious information. Collect only the accommodation needed, limit access to people who need it for the event, and omit unnecessary diagnoses. Do not upload payment credentials, bank account numbers, passwords, government identification numbers, identity documents or medical records.
Incassia may receive, organize, store, retrieve, display, deliver, export, back up and delete Planner Data, send planner-directed links or emails, support authorized imports, and process selected files or prompts using enabled AI features. These instructions apply during service and until return or deletion is complete. Incassia will process sensitive accommodation details only as instructed to arrange the event or carry out an authorized operation on that booking.
For migration, the owner selects files and authorizes the automated job after receiving the identity of any outside AI provider and a description of the files it will receive. Job access ends when the job closes. The agent’s permission is limited to the authorized workspace, destination bookings, selected files, permitted actions and duration. The owner may revoke it at any time. Reference floor plans and seating charts may be attached. A separately ordered manual copy requires the limited human access approval in section 4. An automated job does not authorize staff to open the workspace.
Incassia may retain, use or disclose Planner Data only to perform the limited services in section 2, secure them or meet a legal duty. Incassia will not sell Planner Data, share it for cross-context behavioral advertising, use it for targeted advertising or its own marketing, or train general-purpose AI models with it. It will impose corresponding restrictions on its subprocessors.
Where the California Consumer Privacy Act (CCPA) applies, the Planner discloses personal information only for the business purposes in section 2. Incassia will act as the Planner’s service provider or contractor and comply with applicable CCPA requirements and regulations. It will not sell or share personal information as those terms are defined by the CCPA, retain, use or disclose it outside the direct business relationship, or combine it with information obtained from another source or its own interactions with individuals, except as expressly permitted by the CCPA and its regulations. Incassia certifies it understands and will comply with these restrictions. It will provide the level of privacy protection required of the Planner under applicable law and promptly notify the Planner if it determines it can no longer meet these obligations.
Incassia will maintain technical and organizational measures appropriate to the nature and risk of the processing. They include role-based access, workspace separation, protected transmission, recovery backups, access logging and timely revocation. It will limit access to authorized persons bound by confidentiality. The Planner will manage its users, recipients and permissions, keep sign-in credentials secure, revoke unnecessary access and report suspected misuse.
For support, staff may open workspace content only after the account owner gives express written approval, including by email or authenticated support request, identifying the issue, the records staff may open and the expiry. Incassia records the approval and access. Access ends at withdrawal, expiry or ticket closure, whichever comes first. Designated personnel may separately access the minimum necessary to contain an active security incident or meet a binding legal duty. Incassia will log the reason and notify the owner promptly when lawful and safe. A voluntarily supplied fictional or redacted sample authorizes designated staff to review that copy for the specified test only.
For a separately ordered floor plan or seating chart copy, the Planner’s account owner must expressly authorize in writing the people who may open the specified source files and destination booking, the work they may do and when access expires. Incassia logs that access and ends it on withdrawal, expiry or job closure, whichever comes first. Permission for the automated import does not grant a person access.
The Planner authorizes the active subprocessors in the schedule below for the listed services. Incassia will impose written duties at least as protective as this DPA, including confidentiality, use limits, safeguards and applicable deletion instructions. Incassia remains responsible to the Planner for their performance. Incassia will email the owner at least 30 calendar days before a new or replacement subprocessor will first receive Planner Data, identifying the provider, purpose, affected data and relevant processing locations. The Planner may object on reasonable data-protection grounds within 15 calendar days after notice. Incassia will work with the Planner to resolve a timely objection and will not send its data to the proposed provider while the objection is unresolved. If no reasonable alternative is available, the Planner may terminate the affected service and receive a refund of any unused prepaid portion.
Incassia will make the relevant processing locations available to the Planner before processing begins and notify it of material changes. Before a transfer that requires safeguards by law, the parties will document the applicable legal mechanism and complete any necessary terms and annexes. If that cannot be done, Incassia will not make that transfer.
Incassia will promptly forward privacy requests about Planner Data to the Planner and act on its instructions, unless the law requires a direct response. Taking account of the processing and the information available to it, Incassia will assist with timely access, correction, deletion, portability, restrictions, objections, appeals and other applicable rights, including passing required requests to affected subprocessors. It will provide reasonable assistance with impact assessments, security reviews, prior consultations, regulatory inquiries and incident notices.
A security incident means unauthorized access to, acquisition, alteration or disclosure of, or accidental or unlawful loss or destruction of, Planner Data handled by Incassia or its subprocessors. Incassia will notify the verified account owner without unreasonable delay upon discovering an incident and sooner whenever required by law. Where Utah Code § 13-44-202(3) applies, Incassia will notify and cooperate with the data owner or licensee immediately upon discovering a qualifying breach if misuse of the personal information occurs or is reasonably likely. Incassia will not wait to establish every fact before the first notice. It will share the available timing, data and people affected, likely consequences, protective steps and a contact, supplement the notice as facts develop, and cooperate with containment and legally required notices. The Planner coordinates notices concerning data it controls. Each party may make a notice it is independently required to make.
Incassia will supply information reasonably necessary to demonstrate compliance and cooperate with assessments by the Planner or its confidential independent auditor, including inspections where applicable law requires. Existing reports can satisfy a request if they address it. Upon notice, the Planner may take reasonable and appropriate steps to verify use, stop unauthorized processing and require remediation. Assessments will protect other customers’ data. Incassia will document corrective action and, on request, confirm completion where appropriate.
At the Planner’s choice, Incassia will return or delete Planner Data at termination, subject to any retention required by law. A beta-only workspace may export through January 15, 2027. A subscribed workspace may export for 30 days after actual closure, including closure for nonpayment. A payment freeze after seven full unpaid days does not start that window. For nonpayment, closure follows 30 unpaid days measured from the missed payment. The verified owner may email for a secure export throughout a freeze or export window. Incassia will deliver a requested export in common formats within 10 business days after verification and preserve the data needed to fulfill a timely request if delivery crosses the deadline. Receipt by the deadline preserves the request while we verify the owner. It will delete the active workspace at the end of the applicable window, subject to completing a timely export. It will honor an earlier verified company deletion request within 30 days, subject to legally required records, and confirm completion in writing. It will tell the owner if that request will end a pending export.
For beta migration, Incassia deletes staging copies from active storage within 30 days of sign-off or cancellation, or within 30 days after the beta ends if sign-off never occurs. For a post-beta migration, the order or approved job inventory must set a job expiry date. Incassia deletes active staging copies within 30 days of the first of sign-off, cancellation or job expiry, subject to any earlier legal deadline. Files the Planner selects for attachment remain with the booking. A voluntary fictional or redacted sample export is deleted from active storage within 30 days of receipt or earlier on request.
Incassia will keep each company’s recovery copies in separate storage in the same Cloudflare account and encrypt them with a key unique to that company. Under the ordinary recovery schedule, it retains every backup from the most recent 30 days and then one per month for 12 months. Deleted data may remain there for up to about 13 months, subject to any shorter deadline required by applicable law. Incassia will restrict retained copies to recovery, security or legally required use, relay required deletion instructions to affected subprocessors and reapply outstanding deletions before restored records return to ordinary use. Where Washington’s My Health My Data Act applies to an authenticated deletion request for consumer health data, Incassia will delete affected backup or archived data within six months of authentication, or earlier where required. The Planner will promptly provide the authentication date and information needed to identify the records. These duties continue for as long as Incassia or its subprocessors retain Planner Data.
Send instructions, objections or requests to hello@incassia.events. Incassia sends notices to the verified account owner at the email address on file. The Planner will keep that address current. The underlying business agreement governs disputes and liability, subject to mandatory law. Electronic acceptance and signature are alternatives. Each party should retain the dated version accepted with its order or enrollment record.
Planner legal name __________________________________________
Authorized representative and title ______________________________
Signature and date __________________________________________
For Incassia, LLC (name, title, signature and date) _____________________
Cloudflare — Active. Hosts workspace databases, uploads and recovery storage. It receives workspace records, documents and files needed to host and recover the service. Section 7 sets the recovery-copy schedule.
Clerk — Active. Authenticates team members and sign-in recipients. It handles relevant user names, email addresses, authentication information and session data.
Resend — Active. Delivers planner-directed and service emails. It handles recipient addresses, message subjects and content, which may include event details and access links.
OpenAI — Active for selected AI operations. For document reading it receives selected files and instructions. For Posy it receives the prompt and authorized booking context. Migration uses an outside provider only as disclosed for that job. The service has no company-wide AI switch. A request-level storage setting does not govern default abuse monitoring or the lifecycle of files uploaded separately. Section 6 of the Privacy Policy describes provider retention.
Google and Microsoft calendar connections and Stripe and Square client payment connections — Disabled as of this schedule date. They receive no Planner Data through those disabled features. Before enabling one, Incassia will disclose relevant recipients, permissions, data and roles and obtain the Planner’s connection authorization. Section 5 governs any new subprocessor.
Stripe subscription billing — Separate from client payment connections. When a Planner buys an Incassia plan, Stripe handles Incassia’s subscription checkout and related billing information. The Privacy Policy covers that processing.