Privacy Policy · version 2026-11-16
This version takes effect when first posted. It covers waitlist and enrollment information collected before the beta opens on November 20, 2026.
Incassia, LLC, a Utah limited liability company, operates the Incassia websites and event-planning workspaces.
Privacy contact • hello@incassia.events
This notice covers incassia.events, its waitlist and beta enrollment, company workspaces, and the forms, invitations and shared pages that planning companies provide through Incassia.
Incassia decides how to use website inquiries, waitlist and marketing preferences, account administration, subscription billing and records needed for its own support, security and legal obligations. You can contact us directly about these records.
Your planning company decides which event records to collect, who receives them and how they are used for the event. We process those records for the company under its instructions and our Data Processing Agreement. This applies when a planner enters data about you and when you submit a form, comment or signature yourself. The same person may appear in both an Incassia account record and the planner’s event records.
The planner chooses which teammates, clients and vendors receive access. For example, the planner may send a seating chart to the venue or share meal requirements with a caterer. Information a planner or recipient downloads, prints or forwards may also remain with that person.
Incassia’s providers receive the information needed for their functions in section 5. Staff access to workspace content is limited as described in section 4.
We will not sell planner-controlled event records, share them for cross-context behavioral or other targeted advertising, or use them to market to the planner’s clients, vendors or guests.
Account and sign-in. The company and its users supply names, emails, roles and settings such as the workspace address, time zone, company logo and support email. Our sign-in provider handles authentication.
Enrollment and waitlist. We use the contact and company details you provide, your mailing preference, and signup source and time. Beta enrollment can include team invitations, event volume, current planning tools and a record of the terms accepted.
Subscription billing. If a company orders a paid plan, Stripe processes payment. Incassia uses the billing contact, plan, amounts due or paid, transaction status and identifiers it receives to manage the subscription, refunds and accounting.
Support and feedback. We receive the correspondence, page information and screenshots you choose to send. Please remove identifying details that are unnecessary to explain the issue.
Activity and technical records. These can include changes made in a workspace, company AI usage counts, error records, browser and network information, and the time of a request. We use them to operate the service, investigate failures and protect accounts.
What we receive depends on the information the planner enters, imports or requests.
Clients and inquiries. Names, contact details, event dates and venues, preferences, form responses, contracts, budgets, prices, invoices and payment records.
Guests. Names, seating assignments, meal choices and requested accommodations. A named guest’s food allergy, religious meal requirement or accessibility request can reveal sensitive information. Planners should ask for the practical accommodation, limit access to those arranging it, and provide notices and obtain permissions required for that use.
Vendors and staff. Business and contact details, shifts, roles, rates, agreements and invoices.
Documents and designs. Uploaded contracts, signatures, timelines, budgets, floor plans, images and templates, including originals selected for optional White Glove Migration.
Planning work. Guest placement, notes, tasks, messages and comments.
Keep medical records, government IDs, full payment card or bank numbers, passwords and other account credentials out of the workspace. Check unredacted attachments as well as form fields.
The planner receives the information you submit, including form answers, requests, comments and signatures. A shared page or signature request may use your email to verify access. Signature records may include the signer’s name, time, IP address and a document fingerprint used to verify the signed version. Access and security records can be associated with the relevant page or request.
When a planner uses an Incassia inquiry form, that planner receives the contact information, event details, message and other answers you enter. For questions about an inquiry or RSVP, contact the planning company named on the form or in the invitation.
We provide the selected workspace features, including organizing bookings, sharing the materials a planner selects, recording signatures, exporting records and recovering data.
We administer accounts, authenticate users, manage subscriptions and respond to support and security reports.
We send invitations, forms, signature requests and other planner-directed messages. We use the contact details supplied for an Incassia inquiry, waitlist or mailing list to answer it or send the updates requested.
We process files or prompts for AI features as described in section 6.
For support, Incassia staff may open workspace files or records only after the account owner expressly approves access in writing, including by email or an authenticated support request. The approval must identify the issue, permitted records and expiry. The owner can withdraw it at any time. We record the approval and access, and end access 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 obligation. We record why and notify the owner promptly when lawful and safe.
When a planning company orders manual copying of a floor plan or seating chart, its account owner must give express written authorization naming the people who may open the specified files and booking, the authorized task and the expiry. We log access and end it at withdrawal, expiry or completion, whichever comes first. Approving an automated migration gives no one permission to open a workspace.
Testing an export does not require sending us a copy. If the owner volunteers a fictional or redacted sample, designated staff review that copy only for the specified test. Follow section 8 for deletion.
We use information to meet binding legal duties and to protect accounts. The limits on access to workspace content also apply to those activities.
These providers have different roles. The planner gives instructions about workspace content. Incassia selects providers for its own subscription, account and business operations.
Cloudflare hosts workspaces and processes the database records, uploaded files and recovery copies needed to provide the service.
Clerk handles sign-in and identity information, such as a user’s or invited recipient’s email and the authentication data needed for their sign-in method.
Resend delivers planner-directed and system emails. It receives the recipient address and the subject and contents needed to deliver a message.
OpenAI processes the files, instructions and booking context sent for AI features. Section 6 explains when this happens.
Stripe and Square connections for client payments are disabled during the beta and at public launch. Planners may manually record a payment made elsewhere. This is separate from Incassia subscription billing.
Google and Microsoft calendar integrations are disabled. Before enabling an integration that changes how personal information is handled, we will update the notice and explain the permissions requested when a planner connects it.
Stripe processes Incassia subscription payments when an owner orders a paid plan. Any email delivery provider used for Incassia marketing may receive subscriber contact details, mailing preferences and message-delivery information for that purpose.
We may disclose the minimum information required by a binding legal demand and give the planner notice when permitted. In a merger or transfer of the business, we may transfer records subject to continuing privacy and contractual protections and provide notice. A change of ownership does not by itself authorize a new use of planner data.
Document reading sends the selected document for analysis. Posy sends the user’s question and relevant workspace context. For an optional migration, we identify any outside AI provider and what files it would receive before the account owner authorizes the import.
An original file or free-text question can include everything typed or attached, including confidential pricing, contact details and guest notes. Remove information that is unnecessary for the task before submitting it. Do not assume that limits on the structured booking context also remove information from your attachments.
We will not use planner data to train general-purpose AI models or authorize providers to do so. Our processing instructions call for requesting that OpenAI not store the generated response where that setting is supported. That setting does not remove the provider’s separate abuse-monitoring logs. OpenAI describes a default of up to 30 days for those logs, subject to legal and safety exceptions. Files sent through a separate file endpoint may be kept until deletion or expiration. The applicable endpoint and account controls affect retention. OpenAI describes its practices at developers.openai.com/api/docs/guides/your-data.
AI-generated entries are drafts. Review extracted terms, amounts and dates against the original before accepting a change to the booking. Rejecting a suggested entry does not erase the submitted prompt or an existing chat record.
The workspace keeps Posy conversations, AI-use acceptance records and usage counts. The workspace owner can review a conversation escalated for harassment, including the relevant prompts and responses. Incassia staff access remains subject to section 4.
There is no company-wide AI off switch. To avoid sending content through those features, use the manual workflow, skip AI reading and Posy, and decline AI-assisted migration.
Cookies and similar storage support sign-in, security and user settings. Some saved drafts and preferences may remain on your device. Browser settings let you remove site data or block cookies. Blocking authentication cookies can prevent sign-in.
We honor opt-out preference signals, including Global Privacy Control, when applicable law requires it. A browser setting does not remove information a planner already collected through an event form. Use section 9 to request help with an existing record.
Workspace records and saved chats remain available while the workspace is active, subject to authorized deletions and applicable law.
Beta-only workspaces have export access through January 15, 2027 unless the verified owner requests earlier deletion. We send two notices before scheduled deletion, the last at least seven days in advance. For subscribed workspaces, the export window lasts 30 days after actual closure. A missed payment freezes workspace use after seven full days and closes the account after 30 unpaid days from the original missed payment. A freeze does not start the export clock. A verified owner may request a secure export by email while the account is frozen or during the post-closure export period.
Beta migration staging copies are deleted within 30 days after sign-off or cancellation, or within 30 days after the beta ends if sign-off never occurs. Files the planner attaches to a booking remain with that booking. We delete an optional fictional or redacted sample export from active systems within 30 days of receipt or earlier on the owner’s request. 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.
We delete the active workspace at the end of its export period, after completing any export requested by the deadline. A timely request remains eligible while we verify the owner and deliver it. We complete earlier verified company deletion requests within 30 days, subject to required legal retention. A shorter legal deadline controls.
Our ordinary recovery schedule keeps every backup from the last 30 days and then one monthly backup for 12 months. Deleted records may ordinarily persist in recovery copies for up to about 13 months. Where the law requires earlier removal, that deadline applies to backup and archived copies too. Outstanding deletion instructions must be reapplied before restored data returns to ordinary use.
The activity-log retention period is 12 months, subject to a shorter applicable deadline or necessary legal retention. Use of device storage, downloaded copies and copies distributed by a planner may continue outside Incassia’s systems.
We remove waitlist entries on request or 12 months after launch, whichever comes first. If you separately subscribed to marketing, you can unsubscribe at any time. We may keep a minimal suppression record so the address stays off future marketing lists.
We keep account and billing records as necessary to manage the subscription, document payments, handle disputes and meet tax or recordkeeping obligations. We keep support and security records for the issue and any necessary follow-up, and acceptance and consent records for as long as needed to document the agreement or permission. Records retained for a legal duty are limited to that purpose.
Workspace owners can view, correct or export workspace records and request deletion through hello@incassia.events. For Incassia’s own account, billing or mailing records, contact us directly at the same address.
For a client, guest, vendor or staff event record, contact the planner named in your invitation or form. If you contact Incassia, tell us which planner or event is involved and the action requested. We will forward the request to the appropriate planner and help it respond. Please do not send IDs, guest lists or an entire booking in your initial email.
Use the unsubscribe link in an Incassia marketing email or contact us to stop marketing messages. We may still send account, security, billing or service messages related to your use of the service.
Depending on the law applicable to the record, rights can include access, correction, deletion, receipt of a portable copy, withdrawal of consent and opting out of certain uses or disclosures. We may request only the information reasonably needed to verify you or an authorized agent and locate the record. We will respond within the applicable deadline and will not penalize you for exercising an applicable privacy right.
If we deny a request about our own records, we will explain the decision to the extent permitted. If a right of appeal applies, reply to that decision or email hello@incassia.events with “Privacy appeal” and the reason for reconsideration. We will explain the outcome and provide regulator contact information where required.
We require safeguards appropriate to the information handled, including restricting workspace access to authorized people. Recipients should protect shared links. Planners should review access, revoke links when appropriate and remove users who leave.
Our recovery policy requires company-specific encrypted backups. The retention and deletion schedule appears in section 8.
No online system can guarantee complete security or recovery. Contact us promptly if you receive a link or record intended for someone else.
If we discover unauthorized access to, disclosure of, or loss of planner data, we will notify the account owner without unreasonable delay and immediately when applicable law requires. We will share available facts, mitigation steps and material updates, and help the planner meet its notification obligations.
Incassia is intended for event-planning professionals and the adults they invite. An adult may enter the minimum information needed for a child’s participation, such as a seat or meal. Adults should respond on behalf of children under 13. We do not knowingly collect personal information directly from children under 13. If you believe a child submitted information directly, email hello@incassia.events so we can investigate and arrange appropriate deletion or other action required by law.
Processing locations depend on the provider and feature and may be outside your state or country. The planner can request information about provider locations and applicable safeguards at hello@incassia.events. We will use a lawful transfer mechanism where one is required. We provide relevant location information to the planning company before processing its workspace data.
We will post a revised notice with its effective date and email the workspace owner about material changes. During the beta, we will notify companies before a change affecting how their data is used. If a new use requires additional notice, consent or an instruction from the planner, we will obtain it before that use begins.
hello@incassia.events
Incassia, LLC, 440 E 10425 S, Sandy, UT 84070