Security and data
How Huddla handles your data
Postgres on Render, separated per workspace (every query filtered by workspace). Calendar tokens and video links are encrypted with AES-256-GCM; participant links are stored only as hashes.
What Huddla holds
- Organizer team accounts
- Participants' names, email addresses (optional for link joiners), time zones and working hours
- Participants' answers to candidate times and their comments
- Meeting details, agendas, notes, action items and follow-ups
- Organizers' calendar tokens (encrypted) and free/busy reads; participants' free/busy read once and not stored
- Meeting descriptions and notes sent to the AI provider when AI is switched on
How long it’s kept, and how to export or delete it
Finished polls are deleted with their participants and answers after the organizer's setting (3 months to 2 years; 1 year by default); /try samples are deleted after 24 hours. Organizers can export everything or delete a person or the whole workspace at any time.
The full detail is in Huddla’s data export and deletion policy.
Who processes it
Service providers (subprocessors), each on our instructions and only for the purpose shown:
- Render: hosting, databases and backups, in the United States.
- Stripe: subscription and license payments (card details go to Stripe, never to us).
- Resend: sending email.
- Anthropic: reading meeting descriptions, drafting agendas and follow-ups, and wording recommendations.
- Google: calendar free/busy and adding confirmed meetings, only for calendars people choose to connect.
- Microsoft: calendar free/busy and adding confirmed meetings, only for calendars people choose to connect.
- Cloudflare: bot checks on public poll links and the try page (Turnstile), when switched on.
Questions and security reports
Huddla is run by New Odyssey. To ask what we hold about you, to have it exported or deleted, or to report a security problem, email clio@new-odyssey.com. The privacy policy covers the rest.