Trust Center
Everything you need to evaluate Kindora, in one place: how we protect customer data, which vendors handle it, where our information comes from, and how to use your privacy rights.
Last updated November 17, 2026
Kindora is a fundraising platform for nonprofits and social enterprises. The organizations that use it trust us with donor and constituent records, so we treat that data as theirs, not ours.
This page describes controls that are in place today. Where something is still being built, we leave it off this page rather than describe it in the present tense.
At a glance
- Our Gmail integration was independently assessed under Google's CASA program in October 2026, and Google approved it on that basis.
- No SOC 2 report or ISO 27001 certification.
- Database and application servers in the United States.
- No Customer Data is used to train AI providers' underlying models when we use their business APIs.
Documents
Everything we publish about security, privacy and our data, in one list.
- Sub-processors
Every vendor that handles Customer Data: what it does, what data it gets, its region and its data processing agreement.
- Privacy Policy
What we collect, how we use it, and how long we keep it.
- Where our information comes from
The public sources behind our funder data, with counts recomputed every night.
- Data use terms
What Kindora's data may and may not be used for.
- Terms of Service
The agreement that governs use of Kindora.
- Privacy rights portal
Request an opt-out, deletion, access or correction, with or without a Kindora account.
- Report misuse
Tell us if someone is using Kindora in a way we do not allow.
- System status
Live uptime and incident history.
- security.txt
Machine-readable security contact (RFC 9116).
Independent assessment
- In October 2026, TAC Security, an authorized lab for Google's Cloud Application Security Assessment (CASA), assessed Kindora's Gmail integration: sign-in, the Gmail connection and draft-saving flow, and the web application, API and database they run on, including a lab-run scan of the live application. It passed every applicable test case (46 passed; 2 did not apply).
- The assessment did not cover every Kindora feature. For example, file uploads and the fetching of funder websites were outside its scope.
- On that basis, Google approved Kindora's Gmail integration on October 27, 2026. The assessment is repeated every year.
- This is an application security assessment, not a certification. Kindora does not hold a SOC 2 report or ISO 27001 certification, and we have not yet commissioned a full penetration test.
Encryption
- All connections to Kindora, and between Kindora and its sub-processors, are encrypted in transit using TLS.
- Customer Data is encrypted at rest by our infrastructure providers.
- Third-party integration tokens, such as Blackbaud, Salesforce and Google OAuth credentials, are additionally encrypted at the application layer with a dedicated key.
Access control and tenant isolation
- Row-level security enforces per-tenant isolation by organization across customer donor and CRM data, with role-based access control in the application.
- Person-enrichment tables are gated per organization for the browser role; the frontend does not read them directly.
- Multi-factor authentication is required on every account that can reach production systems or source code.
- Signed-in sessions end after 30 days, or after 14 days without use, and the user signs in again.
- Least-privilege secrets management. Production credentials are restricted to required personnel, access is removed the day an engagement ends, and the production access list is reviewed on every personnel change and at least once a year.
- Authentication uses Supabase Auth (JWT) for user sessions and service-to-service API tokens for internal calls.
- Support access to customer accounts is read-only and logged.
Secure development
- Dependabot alerts and automated security-update pull requests.
- Security alerts are fixed on deadlines counted from when the alert opens: critical within 3 days, high within 7, medium within 30.
- CodeQL static analysis on pull requests, plus a full scan of the production codebase twice a day.
- Code review on changes, with AI-assisted security review available.
Logging, monitoring, and resilience
- Error monitoring configured to exclude default personally identifiable information, and product-usage analytics with process-type tagging.
- Infrastructure-level access logging.
- Managed Postgres with provider redundancy and daily backups kept for 7 days.
- Our database and application servers are in the United States. A few sub-processors operate in the EU; the sub-processor list shows each one's region.
Incident response
- A documented personal-data-breach process covering detection, assessment, containment, controller notification without undue delay, and documentation.
Data minimization and sub-processors
- Analytics use hashed identifiers where feasible. Product-usage telemetry does not ingest constituent, donor, or prospect records.
- Our infrastructure, AI model, payment, email, analytics and monitoring providers are engaged under each provider's data processing agreement. Some research and enrichment vendors are engaged under their standard published terms; we are putting negotiated agreements in place and will state the position for any vendor on request.
- We give at least 14 days' notice before adding or replacing a sub-processor.
- No Customer Data is used to train AI providers' underlying models when we use their business APIs.
Privacy rights and suppression
- Anyone can submit an opt-out, deletion, access, or correction request through our privacy rights portal, whether or not they are a Kindora user. Requests are email-verified, routed to the right organization, and tracked against statutory deadlines that start when we receive the request.
- The rights portal honors Global Privacy Control signals.
- A suppression registry records opt-outs using salted hashes, so a request to stop being enriched persists without us storing the underlying identifiers in the clear.
- Contacts marked do-not-enrich are excluded at the data layer, so no enrichment service re-enriches them.
- We removed federal campaign-contribution data from scoring and the product, and ingestion is disabled behind a permanent fail-closed block.
Deletion and return
- Self-service export and deletion tools.
- A 30-day export window after termination.
- A deletion request through the rights portal clears enrichment data held about that person in Kindora.
Security reviews and questionnaires
If your organization is reviewing Kindora, email security@kindora.co. We complete security questionnaires in writing and can share more detail about the CASA assessment on request.
Reporting a security issue
If you believe you have found a vulnerability in Kindora, email security@kindora.co. We acknowledge reports within 48 hours. Please give us a reasonable window to investigate and fix before public disclosure. For privacy questions, email privacy@kindora.co.
Changes to this page
- November 17, 2026. Added the independent CASA assessment, multi-factor authentication, session limits, access reviews, remediation deadlines, backups and hosting regions. Corrected the code-scanning schedule (pull requests plus two full scans a day; there is no scan on each push) and narrowed the sub-processor agreement statement to match the sub-processor list. This page now links every public security, privacy and data document.
- October 5, 2026. First published.