Beta Participation Agreement · version 2026-11-16
1. Incassia, LLC, a Utah limited liability company at 440 E 10425 S, Sandy, UT 84070, provides the Service (“Incassia” or “we”).
2. The planning business named in the enrollment record or signature block is the “Company” or “you.” Its representative confirms that they have authority to enter this agreement for the Company.
1. This agreement covers free access to Incassia’s private beta for wedding and event planners (the “Service”), optional migration of one active wedding and the benefits in section 10. The agreement governs enrollment and any authorized preparation from acceptance. Beta workspace access follows the dates in section 3.
2. The Service is under development. Features may change, fail or be discontinued during testing.
1. The Beta Period runs from Friday, November 20 through Friday, December 11, 2026. Public release is scheduled for Monday, December 14, 2026 (the “Release Date”). Sections 9 and 10 cover continued access, enrollment and export.
2. Ending early. Either party can end this agreement at any time by written notice (email is enough).
3. At general release the Company can choose a paid plan. Incassia will charge for a subscription only if the Company affirmatively accepts a plan and its billing terms. Section 9 governs export access for companies that do not subscribe.
1. The beta is free, including optional migration of one active wedding per participating Company.
2. The Company has no obligation to buy anything at the Release Date.
3. The Company remains responsible for any fees it incurs using its own outside payment services.
1. Workspace. Incassia provides a dedicated site on a Company subdomain of incassia.events and keeps the Company’s booking records and files separate from other planning businesses.
2. Users. The Company may invite up to five people from its team.
3. Kickoff call at a time chosen by the Company from the slots offered on Sun Nov 22, Mon Nov 23 and Tue Nov 24, 2026.
4. Optional White Glove Migration. The owner may submit files for one active wedding through the intake method Incassia supplies. Before import, Incassia identifies the destination workspace, the selected files, the data sent to each outside AI provider and the purpose of the job. The owner authorizes that job and may cancel future processing. The automated Migration Agent’s access ends when the job closes. Human access requires separate approval under section 8.4.
The Company must have permission to supply the files and must redact unnecessary personal details and the material listed in section 6.9, including where it appears in a contract or attachment. Floor plans and seating charts may be attached as reference files. Exact editable duplication is optional under a separate order at $25 per hour with a four-hour minimum ($100), billed for actual time worked subject to that minimum. Terms section 8.7 defines the scope and fees. After the import, the Company checks the imported records against its originals. Historical imports do not authorize sending invitations, requesting signatures or collecting payments. Declining migration does not affect eligibility for beta benefits.
For each booking, submit copies in a top-level folder named for that wedding client. Inside it, use the same subfolder names and hierarchy as the destination booking in Incassia. Incassia places a loose file or a file in an unrecognized folder into that booking’s Misc folder. If the booking itself is unclear, Incassia holds the file for the Company to identify the destination. Incassia reports imported, skipped, held and Misc items for review. The Company keeps its originals. Terms section 8.7 governs source defects, filing instructions and correction of Incassia’s filing errors.
5. AI document reading. When a user requests extraction from a contract, vendor agreement or invoice, the selected document goes to the disclosed AI provider. The Company must check the extracted names, dates, amounts and other fields against the original before accepting them. The Privacy Policy describes provider processing and retention.
6. Client payments. Incassia will not collect or move client funds during the beta or on public launch day. Planners can record a payment received elsewhere. Stripe or Square client payment processing may be enabled after public launch. No activation date is promised.
7. Support. By email, on a reasonable-efforts basis. Email hello@incassia.events, weekdays 9 AM to 5 PM Mountain Time.
1. Book and attend a kickoff call.
2. Use the Service in good faith for planning work. After onboarding, the Company may work on a real event it is authorized to manage or test the same steps using a fictional event.
3. Submit all three Friday feedback forms. The November 27 form is accepted through Monday, November 30 because of Thanksgiving. The remaining forms are due December 4 and December 11.
4. Attend a 20-minute wrap-up call between December 9 and December 11.
5. Report problems promptly. Use a fictional example or remove client and guest details from screenshots.
6. Keep independent copies of critical event records, especially the originals used for migration and any documents needed on the event day.
7. Keep sign-in details private, and add users only from its own team. Up to 5.
8. Hold the rights and permissions required for the materials supplied, including third-party contracts, photographs and floor plans, and provide the privacy notices or obtain the consents required for information about clients, guests, vendors and staff.
9. Exclude payment credentials, bank account numbers, government ID documents or numbers, medical records and passwords from uploads, forms, AI prompts and feedback submissions.
10. Not try to reach any other company's site or data, and not copy, scrape or resell the Service.
To earn the benefits in section 10.1, attend kickoff and wrap-up, submit all three forms by the dates above, and test the export of one complete booking. A fictional booking qualifies. Report the outcome in the feedback form. Providing the export itself is optional. If an Incassia outage or an Incassia cancellation prevents a required activity, Incassia and the Company will arrange an equivalent opportunity to complete it.
1. The Company will protect nonpublic features, designs, pricing, screenshots, recordings, bugs and security reports. The Company may share them with its team and professional advisers who need them to participate and are bound to protect them. Public launch releases only information Incassia has made public.
2. Incassia will protect nonpublic Company information, including client and vendor records, contracts and prices. Incassia may use it only as section 8 allows. Incassia may not use it to solicit the Company’s clients or vendors, or to promote another planning business. Neither party may use the other’s name, logo or testimonial publicly without written permission.
3. Each party will use reasonable care. These duties exclude information lawfully known without restriction, independently developed, lawfully received from another source or made public without a breach. A party may disclose the minimum legally required and will give prior notice when allowed. Either party may communicate lawfully with a regulator. Nothing here limits an honest review or report protected by law.
4. The duty for unreleased product information lasts two years after the Release Date. Trade secrets remain protected while they qualify as such. Incassia protects nonpublic Company content and personal data for as long as it retains them, including in backups.
1. Ownership. The Company and its clients, vendors and other rights holders retain their rights in the content supplied to the Service. As between Incassia and the Company, the Company controls its booking records and exports, subject to those third-party rights. Incassia retains its rights in the Service.
2. Incassia processes workspace data on the Company’s instructions under the Data Processing Agreement (“DPA”), including to provide, secure, back up and support the Service and as required by law. The Privacy Policy separately covers Incassia’s own use of business account and contact information.
3. The DPA provider schedule lists the services authorized to handle Company data. Cloudflare provides hosting and storage, Clerk supports sign-in, Resend delivers email and OpenAI processes selected AI requests. The Privacy Policy explains what information each receives.
4. Staff access. For support, Incassia staff may open workspace records or files only after the account owner expressly approves access in writing, including by email or an authenticated support request. Approval must identify the issue, the records or files staff may open, and when access ends. The owner may withdraw approval at any time. Incassia records the approval and staff access and ends access when the issue is closed, approval expires or the owner withdraws it, whichever comes first. Separately, designated personnel may access only the information reasonably necessary to contain an active security incident or comply with a binding legal obligation. Incassia records the reason and notifies the owner promptly when lawful and safe.
For a separately ordered floor plan or seating chart copy, the 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.
5. Incassia may use product suggestions to improve the Service. This permission does not include the Company’s private content or anyone’s personal information. The owner may voluntarily supply a fictional or redacted export for a specific test. Remove identifying details, signatures and attachments containing personal information. Incassia may review only that copy for the authorized test. Incassia deletes the active copy within 30 days of receipt or earlier on the owner’s request. Backup copies expire under the schedule in section 8.8.
6. Incassia does not use Company data to train its own models. The Privacy Policy describes the AI features, the provider’s handling of submitted material and the controls available to users.
7. The Company may use the workspace export tools or email hello@incassia.events during the applicable access or export window. Incassia will securely provide the verified owner with an export in common formats, including CSV and PDF as applicable, within 10 business days after receiving a verified request. A request received by the deadline remains eligible while Incassia verifies the owner and completes delivery. Incassia will identify which records and attachments the export includes so the Company can check its copy.
8. The verified owner may request earlier deletion in writing. Incassia deletes the active site and data within 30 days and confirms completion in writing. Information that Incassia must retain by law may remain for the required period. Deleted data may remain in restricted backups for up to about 13 months under the schedule in the Privacy Policy and DPA. A shorter legally required deletion deadline controls, including for archived copies. If a backup is restored, Incassia will reapply outstanding deletion instructions before ordinary use resumes.
9. Incassia will notify the account owner without unreasonable delay after discovering unauthorized access to, disclosure of or loss of Company data, and immediately when applicable law requires. Incassia will describe the facts then known, cooperate with the Company and send updates as material facts become available. The DPA governs incident response for personal data.
10. Incassia deletes migration staging copies within 30 days after sign-off or cancellation, or within 30 days after the beta ends if there is no sign-off or cancellation. Files selected for attachment to the booking remain subject to the workspace deletion schedule. Section 8.8 governs backup copies. 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.
1. The Company’s workspace stays open between the end of the beta on December 11 and the scheduled public release on December 14, 2026.
2. If the Company enrolls in a subscription, its existing workspace and booking records continue under the plan it selects.
3. A Company that declines a subscription may still download its data.
4. Unless the Company subscribes or requests earlier deletion, its workspace remains available for export through January 15, 2027, Mountain Time. Incassia then deletes the active workspace, subject to any timely export request under section 8.7. Section 8.8 governs backups and legally required records.
5. Before scheduled deletion under section 9.4, Incassia sends the owner at least two email notices. The last notice will be at least seven days before deletion.
The Company may retain the version of this agreement it accepts.
1. A Company that completes section 6 and enrolls in a base subscription plan between public launch and January 15, 2027, inclusive, earns six full months of base service, free White Glove Migration of its remaining bookings, and the price lock in section 10.4. The parties will confirm the list of bookings, source files and intended imports before the migration begins. Exact duplication of editable floor plans or seating charts is a separately priced service under Terms section 8.7.
The free period starts on enrollment and ends the day before the six-month anniversary. For December 14 enrollment, base service is free through June 13, 2027 and the first possible base charge is June 14. For January 15 enrollment, it is free through July 14 and the first possible base charge is July 15. Incassia will show the plan, price, billing frequency, first charge date and cancellation method and obtain affirmative billing authorization before charging. If the Company does not authorize ongoing billing, the free service ends and the Company receives the 30-day export period in the Terms. Separately ordered add-ons and applicable taxes are outside the base-service benefit.
2. Each participating company can request migration of one active wedding during the beta. The separate post-beta benefit in item 1 applies only after the Company meets the conditions stated there.
3. Under a separate launch offer, the first ten companies to pay for an annual plan receive free White Glove Migration. Completion of the beta does not require the Company to buy an annual plan.
4. Qualifying beta graduates who enroll by January 15, 2027 and the first 50 paying companies each qualify for the launch price lock. While the account stays open, the Company may switch among the three launch plans at their base monthly or annual rates identified in the launch price schedule in Terms sections 8.1 and 8.2. Extra users, projects, AI and other add-ons carry their then-current prices, subject to the stated 2027 prices in the Terms. Applicable taxes remain payable. A payment freeze preserves the lock if the Company pays before closure. The lock ends at closure.
5. Benefits are personal to the Company and cannot be transferred or redeemed for cash or credit, including when the Company cancels or declines the free period.
1. The Service is provided "as is" and "as available".
2. Incassia offers no service-level agreement during beta testing. It does not guarantee uptime, a response or recovery time, uninterrupted backups or recovery of every record or file. Its express data protection, export and deletion obligations still apply.
3. The Privacy Policy and DPA describe backup retention. Keep independent copies and check that exports contain the material needed to run each event.
4. AI results are suggestions. Nothing the Service reads or suggests is legal, tax or financial advice. The Company is responsible for its contracts, invoices, taxes and what it tells its clients.
5. An import or AI suggestion does not initiate a payment, message or signature. Check the original source and the delivery or signature status for important communications. A message marked sent is not proof of receipt.
1. The common aggregate liability cap and damages exclusions in Terms section 12 apply to the Beta Agreement, Terms and DPA together. Incassia’s aggregate liability is capped at the greater of $100 or the fees the Company paid Incassia for the Service in the 12 months before the first event giving rise to the claim. Related claims and multiple agreements do not increase the cap.
2. To the extent permitted by law, the exclusions in Terms section 12 include indirect, incidental, special and consequential damages, including lost profits from a lost event.
3. Neither the cap nor the damages exclusions apply to Incassia’s fraud, gross negligence or willful misconduct, or to liability that applicable law prohibits limiting. An expressly promised refund remains payable.
4. Neither party owes the other a contractual duty to defend or indemnify for claims arising from the free beta. This rule controls any conflicting indemnity in the Terms.
1. By either party at any time, by written notice.
2. Incassia may immediately restrict access when reasonably necessary to contain an active security threat or prevent unlawful use. It may end beta access for a material breach of the upload, use or confidentiality duties in sections 6 and 7. Incassia will notify the owner of the reason and a way to request review as soon as lawful and safe.
3. Sections 7, 8, 9, 10, 12 and 14 survive to the extent needed to carry out their terms, including earned benefits.
4. When participation ends, ordinary use stops on the stated date. Export remains available through the deadline in section 9. If direct access is unsafe or suspended, a verified owner may request secure delivery under section 8.7, subject to applicable law and protection of other people’s data.
1. The Beta Agreement, Terms of Service and incorporated Data Processing Agreement govern beta use. The Data Processing Agreement controls conflicts about processing personal data on the Company’s behalf. This Beta Agreement controls other conflicts about the beta and its surviving benefits.
2. Changes to this agreement or its earned benefits require written agreement by both parties. Incassia may change beta features without notice, subject to its express commitments in this agreement and the DPA.
3. Business disputes are subject to the binding arbitration provision in Terms section 14.2. It provides for one AAA commercial arbitrator seated in Salt Lake County, Utah, and permits eligible small claims and urgent temporary court relief. That section survives the beta.
4. Send notices to Incassia at hello@incassia.events. Incassia sends notices to the current verified owner email in the Company’s enrollment or workspace record.
5. Assignment. The Company cannot transfer this agreement. Incassia can transfer it with the Service, with notice.
6. An authorized representative may accept electronically through enrollment or the parties may sign below. Electronic enrollment takes effect when the representative affirmatively accepts the identified versions of the Beta Agreement, Terms and DPA. Incassia will retain the Company name, representative’s name, title and email, time of acceptance and versions accepted, and provide a copy the Company can retain.
For the Company, if signing on paper or by electronic signature
Company legal name and address ____________________________________
Authorized representative and title ___________________________________
Email _____________________ Signature _____________________ Date __________
For Incassia, LLC, if signed as a separate agreement
Authorized representative and title ___________________________________
Signature __________________________________________ Date __________