CRM Giving Pricing Security Try it today

Trust & security

Security at Meridian Voyager

Your organization trusts Voyager with donor records, beneficiary details, and the day to day work of your mission. Here is how we protect that data, in plain language, with no overclaiming. Where something is on our roadmap rather than done, we say so.

Tenant isolation

Your data is walled off

Every customer lives in its own workspace. One organization can never see or reach another organization's data.

Enforced in the database itself

Separation between workspaces is enforced by PostgreSQL, not just by our application code. Every table that holds workspace data is protected by row-level security policies, and the application connects using a restricted database role that those policies scope to the current workspace.

That means isolation does not depend on a developer remembering to add a filter to a query. The database refuses to return another workspace's rows. It is the strongest place to put this boundary, so we put it there.

Encryption

Encryption everywhere

Your data is encrypted while it travels and while it sits at rest.

In transit

All traffic to Voyager, and between Voyager and its data stores, runs over TLS. Strict Transport Security is enforced, so browsers only ever connect over a secure channel.

At rest

Our managed database and file storage encrypt data at rest. The most sensitive stored secrets, such as a workspace's outbound email password, get a second layer: they are encrypted in the application with AES-256-GCM before they are written, so the plaintext never lands in the database.

Payments

Card numbers never touch our servers

Payments are handled by Stripe, a PCI DSS Level 1 certified provider and one of the most trusted names in online payments.

Fully outsourced to Stripe

When a card is entered, it goes directly into Stripe's own hosted, secure fields and on to Stripe. Full card numbers are never stored, processed, or transmitted by Voyager's servers. We keep only Stripe's tokens, which cannot be turned back into a card number.

Because all card handling is outsourced this way, Voyager falls under the lightest PCI scope (SAQ A). See our compliance posture below.

Access

Access and audit trails

People see only what their role allows, and important actions are recorded.

Least-privilege roles

Inside your workspace, you decide who can do what. Roles such as owner, admin, member, and limited portal access gate every part of the product, and sensitive areas can be restricted further to users who meet your requirements.

Behind the scenes, access to production infrastructure is limited to the two founders using strong, unique credentials. There are no shared infrastructure logins, and secrets are never stored in code.

Audit trails

Voyager keeps audit trails of important actions across the workspace, so you can see what happened and who did it. This protects the donor and beneficiary data your supporters trust you with, and it helps your team hold itself accountable.

Resilience

Backups and recovery

Your data is backed up every night to a separate provider, and we have tested that we can restore it.

Nightly, off to a second provider

  • The whole database is backed up every night to independent storage at a second provider (Cloudflare R2), encrypted at rest, kept for 30 days.
  • Each workspace is also exported on its own every night, so a single customer can be recovered or handed their data without touching anyone else.
  • Uploaded files are mirrored to the same secondary store so they can be recovered alongside the database.
  • We keep a written restore runbook and have run a restore drill to confirm the backups actually come back correctly, with workspace isolation intact.

Responsible AI

AI that works for you, on your data only

Voyager's AI features help with tasks like grant writing and intake. They are careful with your data.

Your workspace, your request

When you use an AI feature, it processes only the data from your own workspace, and only the specific information needed for the action you asked for. AI does not roam across your data or across other customers.

Your data is not used to train AI models. We do not sell your data, and our AI provider's business terms do not use the content we send to train their models.

Where we stand

Compliance posture, honestly

We would rather tell you exactly where we are than claim a badge we have not earned.

The plain truth

Payments (PCI): because all card handling is outsourced to Stripe, we operate under the lightest PCI scope (SAQ A). Card data never touches our servers.

SOC 2: a SOC 2 audit is on our roadmap. We run the underlying controls today (database-enforced isolation, reviewed changes, encrypted and tested backups, incident response), and we will pursue the formal audit when a customer needs it. We do not claim to be SOC 2 certified.

Health data (PHI): Voyager is not sold as a HIPAA system, and our posture is no PHI. Please do not upload protected health information unless we have a specific written agreement in place first.

If your organization has a security questionnaire or a specific requirement, we are happy to work through it with you.

Get in touch

Questions about security?

Reach us directly. We respond to security reports and questions promptly, and acknowledge coordinated disclosures within 3 business days.

soo@meridian-group.ai