Trust and safety
A nonprofit is being asked to let a stranger near its systems. That decision deserves specifics rather than reassurance, including the places where missionStack cannot give you a guarantee.
missionStack is served only over HTTPS, and browsers are instructed to refuse an unencrypted connection for a year at a time. The application loads no third-party scripts, fonts, or trackers: the content security policy restricts scripts, styles, and network calls to missionStack itself. The site cannot be framed by another page, and camera, microphone, location, payment, and USB access are blocked outright.
Passwords must be at least ten characters. Sign-in attempts are limited to five per minute, and password-reset requests to three per five minutes, so guessing attacks are throttled rather than merely logged. Reset links expire one hour after they are issued, and completing a password reset revokes every existing session on the account.
The database is backed up daily and encrypted with AES-256 before the backup leaves the server, with a copy kept off the server. A backup is not treated as valid until it has been restored into a disposable, isolated database and verified. An untested backup is not a backup, and missionStack does not count one until the restore has actually run.
Representatives hold organization-scoped permissions for posting requests, handling contact, approving completion, and managing the organization, granted individually rather than by default. Administrative decisions, verification outcomes, safety actions, and account changes are recorded in audit history, and access can be paused, suspended, or revoked.
Account, profile, organization, request, interview, matching, engagement, safety, completion, review, notification, and audit records. Private records stay behind authentication. Volunteer profiles, organization pages, testimonials, and impact summaries become public only when you turn on the applicable visibility control.
The guided interview and the matching engine send your submitted profile and request text to OpenAI to structure your intake, generate embeddings, and produce explainable recommendations. This is why missionStack asks you not to enter passwords, credentials, protected health information, or confidential client data. Every recommendation shows the reasoning behind it, and a person can always override it.
Transactional email — invitations, password resets, and notifications — is delivered by Brevo. The application runs on a DigitalOcean server, and Cloudflare provides the encrypted entry point to it. missionStack does not sell your information, and does not share it with anyone beyond the providers required to operate the service.
Records and audit history are retained for platform operations, safety review, evaluation, and restoration. To ask what is held about you, to correct it, or to request deletion, write to [email protected].
Every organization submits identity and authority evidence, and a missionStack administrator reviews it and records an approval or rejection with reasons. This review is human judgment on submitted evidence. missionStack does not yet perform automated charity-registry lookups or duplicate-registration detection, and it does not independently confirm that a representative is authorized by the organization's board.
This is the most important sentence on this page. Volunteers reach missionStack only by invitation, and every access request is reviewed and approved by an administrator before an account can be created. That is the entire extent of the screening. missionStack does not run criminal background checks. It does not verify identity documents. Skills, certifications, employment history, and professional links are self-reported and are not independently confirmed. Do not treat a missionStack profile as a credential check.
Begin with bounded, low-risk work: advisory conversations, assessments, planning, documentation, training, or work in a sandbox. Grant the least access that lets the work happen, make it time-limited, and remove it when the engagement closes. Never share passwords or permanent credentials — missionStack never needs credentials to your systems, and asking for them through the platform is prohibited. You grant access in your own systems, which means you can revoke it at any moment without our involvement.
Any participant can report conduct, safety, or scope concerns from the Safety page or through the help button on any signed-in page. missionStack can pause an engagement, suspend an account, and block contact between participants while a concern is reviewed, and good-faith reporting must not result in retaliation. For an immediate threat to someone's safety, contact emergency services first.
missionStack is new, and it is run by one person. The security practices above are implemented and tested, but they have not yet been through an independent penetration test, a qualified legal and privacy review, or a formal accessibility audit with assistive technology. Those are underway rather than finished, and you should weigh that before entrusting anything sensitive to this platform. For now, please do not put confidential client, donor, or regulated information into missionStack at all.
Privacy Policy · Terms of Use · Code of Conduct and Safety · About missionStack
Questions about any of this: [email protected]