Privacy notes for Futureproof Festival.
This page explains how the festival handles information from forms, analytics, ticketing partners, and support requests. This is a plain-language notice, not a formal legal policy, and it will be updated as the festival gets built.
- Revision
- Last updated: October 27, 2026
What we collect
We collect the information you choose to send us through Futureproof Festival forms: name, email address, organization, role, interests, accessibility notes, volunteer details, sponsor or speaker inquiries, and any message you include.
A media accreditation application also includes outlet and role information, public links to recent work, assignment status, an optional editor or producer contact or public assignment-letter link, coverage plans, requested dates, and working-access notes. Do not use that form for sensitive personal or accessibility information.
The private matchmaking intake, now closed, collected your name, email, ticket or Startup Exhibitor reference, connection intent, what you are building, what you offer and seek, up to five sectors or interests, location, commitment level, optional session access needs, and your contact-sharing choice.
The attendee portal uses the email on your named Luma registration for sign-in and eligibility checks. It stores the profile fields and photos you provide, your separate member and public visibility choices, private invitation kit, saved profiles, connection requests and messages, reports, and notification preferences. Registering or signing in does not publish your profile or list you for attendees. Your public page shows only the fields you selected for public use.
Ticket checkout is handled by Luma. When you buy or reserve a ticket, Luma may collect payment, registration, and attendee details under its own privacy and payment terms.
Private exhibitor onboarding collects organization and contact details, public copy, approved logo and rights-cleared artwork-reference links, two attendees, demo, logistics, accessibility and safety needs, an event-day contact, and asset-rights and public-use approval. It accepts no file uploads or payment details.
How we use it
We use festival information to reply to inquiries, send event updates, coordinate access and volunteer requests, manage sponsor or speaker conversations, and operate the attendee experience.
We use media accreditation information only to assess editorial purpose, verify evidence when needed, make an accreditation decision, issue and check in a named credential, coordinate approved working access, and understand published coverage.
We use exhibitor onboarding information to review proposed public materials, prepare attendees, and coordinate demo, accessibility, logistics, and safety needs. Submitted materials are not public by default.
We use matchmaking information only to confirm Festival eligibility, prepare a human-run session, support access needs, and make a follow-up introduction when both people request it and permit contact sharing. We do not create public profiles or use automated compatibility scoring.
We use your attendee profile and visibility choices to provide the page and private portal you asked for. Your registration email, invitation code, personal ticket link, private messages and graphics do not appear on your public profile. Member listing, public listing and graphic preparation are separate choices. Signing in does not subscribe you to marketing. Email alerts for new connection requests and replies are on by default. You can turn them off in your attendee notification settings; existing opt-outs are respected. These alerts do not include private message text.
The directory form and any photo are kept in our private workspace and deleted by December 31, 2026. That existing form/photo deletion promise still applies. Private networking access closes at the end of November 6, 2026, and private networking content has a retirement date of December 31, 2026, end of day, in America/Vancouver. Public-profile consent is separate from private-networking retention. You can withdraw your public visibility or ask us to remove your page.
Graphics in the portal are prepared only when you request them and permit use of your photo. When you choose an AI-painted portrait, we send that photo and the name you enter to OpenAI to generate the artwork. This is a separate choice from uploading a directory photo. You review the result before a private download and decide whether to share them. They are not published automatically or included in public page images.
We do not sell attendee, sponsor, speaker, volunteer, or newsletter contact lists.
Analytics and third parties
The website may use privacy-conscious analytics and event tracking to understand which public pages and calls to action are working. Outbound registration links may include campaign parameters so the crew can understand which of our own pages drove a Luma checkout visit.
Service providers may include website hosting, form handling, email delivery, analytics, and Luma ticketing. They should only receive the information needed to provide those services.
The private attendee portal uses Neon for its database, private Vercel Blob storage for photos and graphics, and Resend for sign-in codes and any separately enabled notification emails. Luma remains the source for registration eligibility and ticketing. These providers may process data outside Canada. Private portal pages load no analytics, and codes, registration emails, message bodies, photos and private kit links are not sent to analytics.
Account removal withdraws access and public visibility first. Private object deletion can need retries before the provider confirms absence. Provider-managed backup and recovery copies have separate retention practices; we do not report their erasure as complete without confirmation. Limited ticket/coupon identity and commercial records remain to prevent duplicate assignments and reconcile provider outcomes. Removing a portal account does not delete Luma tickets or finance records.
Media application analytics record only that a submission succeeded and which form provider handled it. Applicant, outlet, editor, coverage-plan, and submitted URL values are not sent to GA4 or Plausible.
Exhibitor onboarding is stored in a private operations workspace through the website host; the route loads no analytics and sends no answers to analytics. Luma receives attendee details only if the team later issues tickets through that separate service.
Matchmaking analytics likewise recorded only that the private intake succeeded and that the form went through. Names, emails, registration references, answers, intent, access needs, and contact-sharing choices are not sent to GA4 or Plausible.
FestivalChat and AI providers
When FestivalChat is enabled, it is an AI assistant powered through Anthropic's commercial API. The message you type and the recent conversation are sent to Anthropic to generate an answer. FestivalChat uses public-safe festival material and has no registration, payment, account, or private attendee lookup.
Futureproof Festival does not write FestivalChat transcripts to its own database. Anthropic publishes its own commercial API retention and model-training practices. Do not put payment, health, accessibility, confidential, or other sensitive information in the chat; email us instead when a question needs a person.
Read our AI Policy for the broader rules governing AI-assisted writing, code, graphics, operations, and decisions about people.
Media accreditation retention
Rejected applications and private verification details are deleted by January 31, 2027. Accepted records are minimized after the event to the accreditation decision, attendance and credential history, outlet, and published-coverage evidence needed for event operations and impact reporting.
Personal accommodation information is not collected in the media application; accessibility requests continue through a separate accessibility contact.
Matchmaking retention and withdrawal
Matchmaking is cancelled for 2026, and the intake is closed to new submissions.
Matchmaking intake exports, pairing sheets, interest cards, and unmatched requests are deleted within 30 days after the session. Paper records containing participant information are shredded. Futureproof Festival keeps only non-identifying aggregate counts.
You may withdraw before organizer-mediated contact details are sent. Once another participant has received an introduction you authorized, Futureproof Festival cannot retrieve it from their inbox. Sent introduction emails may remain under the normal retention settings of the participants' and organizer's mail systems.
Matchmaking data is not a newsletter opt-in and is not reused for marketing, a member directory, sponsor leads, research, automated matching, or another event.
Chat and FishMail in the festival app
Chat and FishMail in the festival app are optional and use your attendee portal sign-in. When you join, we keep the fish name you choose, what you post in Chat, and the FishMail you send and receive, linked to your portal account so the same fish works on more than one device. Your email and portal profile are not shown in the app.
Your fish name and Chat posts are visible to other attendees in the app and may appear on screens at the venue. FishMail only reaches people you are connected with in the attendee portal. Festival moderators can hide posts and fish.
This data is kept in a separate festival database on Neon, hosted through Vercel, which may process it outside Canada. The app loads no analytics. We delete all Chat and FishMail data by November 30, 2026. To have yours removed sooner, email hello@bc-ai.ca.
Your choices
Exhibitor links work once, and we store only enough to know a link has been used. We review exhibitor personal data at completion and delete or anonymize what is no longer needed, except for limited safety, finance, or event-operation obligations.
When your private account is open, you can change your visibility choices, export your own portal data or request account removal. You can also ask us to change or remove your attendee directory page at any time by emailing us.
You can ask us to update, remove, or stop using your contact information for festival communications. Some records may need to be retained for ticketing, safety, finance, or event operations.
For privacy or accessibility requests, email hello@bc-ai.ca or kk@bc-ai.ca.
