Placeholder — not reviewed by counsel
Privacy Notice
This describes what Aboardable actually does with data today, for a private pilot’s benefit. It is not a finished legal document — data residency, retention periods and cross-border transfer terms all need a real legal and jurisdictional review before this is relied on. See ARCHITECTURE.md § On hosting and data residency for the open questions that review needs to answer.
What Aboardable stores
Board and meeting records: agendas, uploaded papers, packs, meeting recordings and transcripts, minutes, actions and the audit trail of who did what. Account information: your name, email and timezone.
Meeting recording and transcription
When a meeting is recorded through Aboardable’s meeting-bot integration, attendees are asked for consent before recording begins, and that consent is recorded. The resulting recording is transcribed and stored as part of the meeting’s record. A board administrator can request deletion of the recording from the transcription provider’s systems; Aboardable’s own copy of the transcript remains as part of the governance record unless separately deleted.
Who can see what
Access follows board membership, not organisation ownership — see ARCHITECTURE.md § The authorisation layer. A departed board member retains read access only to the packs and minutes of meetings they attended. This is a governance requirement of the product itself, not a privacy add-on.
Third parties involved in processing
Supabase (database, authentication, file storage), Vercel (hosting), Resend (transactional email), Anthropic (AI-assisted agenda and minutes drafting), OpenAI (audio transcription), and Attendee (meeting-bot recording), where each feature is actually in use.