Data protection

Committees handle community money and personal details. This page explains how Mandali protects them.

Your data is isolated#

Every record in Mandali belongs to exactly one organization. Access is checked on the server for every page and every action, based on your signed-in account, never on information sent from your browser. The database also enforces that records can only be linked within the same organization, so even a software bug can't connect one committee's data to another's.

Access follows roles#

What a person can do depends on their role, checked on the server. Removing someone from the organization removes their access immediately.

Every change is recorded#

The audit log keeps a permanent record of who changed what, and when.

Payments#

Card payments run on Stripe. Card numbers are entered on Stripe's secure pages and never reach Mandali's servers. Money is paid into your committee's own Stripe account; Mandali never holds your funds.

Infrastructure#

• Mandali is hosted on Vercel, and data is stored in a managed Postgres database (Neon).
• All traffic is encrypted with HTTPS, and data is encrypted at rest by our providers.
• Sign-in, sessions and two-factor authentication are handled by Clerk.
• Browsers are instructed to only connect over HTTPS and to refuse to embed Mandali in other sites.

Children's information#

Mandali records children only as meal counts (for example 2 child meals). It doesn't ask for children's names or other personal details.

Your rights#

Your organization owns its data. Contact support to request an export or the deletion of your organization's data.