Security
Last updated October 19, 2026
This page describes how AltruNova protects the payment details and personal information that pass through it, what we ask of the people who use it, and how to tell us about a security problem.
1. Payment details
Card and bank details are entered into fields provided by Stripe, our payment processor, and go straight to Stripe. Apple Pay and Google Pay payments are also handled by Stripe. AltruNova never receives or stores full card numbers; for a saved payment method we keep only a reference to it with its brand or bank name, last four digits and expiry date.
Nonprofit payout accounts are set up in onboarding forms provided by Stripe.
2. Encryption
All traffic to the service is encrypted in transit with TLS.
Social Security numbers and brokerage account numbers given for a stock donation, and the password a nonprofit staff member signs in with, are encrypted in the browser before they leave your device. A donor's Social Security number is never shown to the nonprofit.
3. Identity verification
- Nonprofit staff: confirm their work email address with a one-time code, and complete identity verification through Plaid before they can use the portal.
- Donors: confirm their phone number with a one-time code sent by text message before donating. Codes are limited to a few requests in a short period, to stop them being used to flood a number.
- Stock donors: complete identity verification through Plaid before a brokerage account is opened in their name.
4. Access control
Each nonprofit's data is kept separate from every other nonprofit's. Within a nonprofit, every staff member has a role — Owner, Finance, Manager or Viewer — that decides what they can see and do; for example, only some roles can see donation amounts or issue refunds. A nonprofit's administrators decide who is invited and which role each person has.
Inside AltruNova, access to personal information is limited to the people and systems that need it to run the service.
5. Donation widgets
A nonprofit's donation widget runs in a separate, isolated frame on the nonprofit's website. The widget only loads on websites the nonprofit has listed in its settings, which must use HTTPS. The website hosting the widget is told that a donation was made, but not who made it or how they paid.
6. Infrastructure
AltruNova runs on Amazon Web Services. Sign-in sessions use short-lived access tokens; a signed-in session is renewed with a refresh token that is replaced each time it is used.
7. What we ask of you
- Use a strong password that you do not use anywhere else, and do not share your sign-in details.
- Invite only the people who need access to your organization, give each the narrowest role that lets them do their work, and remove people who leave.
- Expect emails from AltruNova only for the reasons listed in our Email policy. We will never ask you for your password or a verification code by email or phone.
- Tell us at info@altrunova.com straight away if you think your account has been used without your permission.
8. Reporting a vulnerability
If you believe you have found a security vulnerability in AltruNova, email security@altrunova.com with a description of the problem and the steps to reproduce it. Please give us a reasonable time to fix it before telling anyone else, do not access or change data that is not yours, and do not disrupt the service or degrade it for others. We will acknowledge your report and keep you informed as we work on it.
9. If something goes wrong
If a security incident affects your personal information, we will tell you, and the nonprofits and authorities concerned, as the law requires. See also our Privacy Policy.