How FolioMatch protects event documents.

1. Organization and role-based access

Every review belongs to a workspace — a planner organization or a venue. Access controls are enforced at the data layer, not only in the user interface, based on a person's active membership of that workspace and their role.

Owners, admins and members can work on reviews; viewers have read-only access. Billing is managed by the workspace owner. Someone removed from a workspace loses access when their membership ends.

We maintain automated authorization tests designed to verify that one organization cannot access another organization's reviews, documents or reports.

2. Private document storage

Documents are kept in private storage. Nothing is published, and files are not served through permanent addresses — files are reached through signed links that expire. Uploads are limited to PDF documents and CSV invoice exports, up to 50 MB each.

Before a document is read by any part of the system, it is checked: the extension, the declared type and the actual contents of the file. A file that is not genuinely a PDF or a CSV is rejected before analysis. File names are cleaned when stored.

3. Secure sign-in and MFA

Sign-in credentials are handled by our authentication service; FolioMatch does not hold passwords in readable form. Password resets go through a single-use, expiring email link, and responses do not reveal whether an address already has an account.

Two-factor authentication with an authenticator app is available to every account and is set up from My profile. Administrative access requires a session verified with a second factor.

4. AI document processing

FolioMatch uses OpenAI models to process uploaded event documents as part of its reconciliation analysis. For each review, the text of the uploaded pages and the document file names are sent; where a page has no text layer, an image of that page is sent instead.

The model identifies agreement terms and bill lines. Amounts are then calculated in FolioMatch's own code from the stored term, the stored line and a stated formula, and each result is shown with its evidence. A finding is a suggestion for a person to review, not a decision.

Analysis currently covers documents in English.

5. Evidence and audit history

Each finding is shown with the terms, bill lines and calculation behind it, so it can be checked against the original documents. Changes to a finding's status, the closing and reopening of a review, and team changes are recorded with the person and the time, and kept as a history. The assessment a review produced is preserved; the human resolution is what changes.

6. Subprocessors and service providers

• Supabase — hosting, database, file storage and sign-in.
• OpenAI — provides the model that processes document text, file names and images of scanned pages during a review.
• Stripe — payments, checkout and billing records.
• Google — optional sign-in with a Google account.

7. Privacy and payment data

Card details are entered in Stripe's own checkout form; FolioMatch does not store card numbers. The application does not run advertising or analytics tracking. How information is collected, used, retained and shared is described in the Privacy Policy; the rules for using FolioMatch are in the Terms of Service.

Deletion is not currently self-service. Account and data deletion requests can be submitted to hello@foliomatch.io.

8. Security is an ongoing process

We continue to strengthen FolioMatch's security controls as the product and the organizations using it grow. We do not currently claim SOC 2 or ISO 27001 certification. If your organization has specific security or procurement requirements, contact us at hello@foliomatch.io.

9. Report a security issue

If you believe you have found a security problem in FolioMatch, please tell us at hello@foliomatch.io before posting it publicly, so we can look first. We'll keep the conversation private while we investigate. The same address handles account, data and deletion requests.