Security

Security and data handling at MemberTrace

Member organizations trust us with member records, dues, and event data. Here is how MemberTrace is hosted and how that data is protected.

Hosting on AWS

  • MemberTrace runs on Amazon Web Services. Our website is served through Amazon CloudFront, the platform API runs on Amazon API Gateway and AWS Lambda, and organization data is stored in an Amazon Aurora (MySQL) database.
  • Infrastructure is defined as code (AWS CloudFormation), so environments are built from reviewed templates rather than configured by hand.
  • [CONFIRM] AWS region(s) where customer data is stored.

Encryption

  • Traffic to MemberTrace is served over HTTPS; requests made over plain HTTP are redirected to HTTPS.
  • Member export files are stored in Amazon S3 with server-side encryption (AES-256) and with all public access blocked.
  • Access tokens for connected social accounts are stored encrypted, as described in our privacy policy.
  • [CONFIRM] Encryption at rest for the primary database.

Access control

  • Sign-in is handled by Amazon Cognito, with optional sign-in through Google or Microsoft accounts.
  • Every request to the platform API passes through an authorizer that validates the signed-in user before any data is returned.
  • [CONFIRM] How administrator roles and permissions are scoped within an organization.
  • [CONFIRM] Multi-factor authentication availability.
  • [CONFIRM] Internal MemberTrace staff access policy for customer data.

Payments through Stripe

  • Payments are processed by Stripe. Card details are entered into Stripe-hosted card fields (Stripe Elements) and sent directly to Stripe, so card numbers are not handled by MemberTrace forms.
  • Organizations collect dues and event fees through their own connected Stripe account.
  • [CONFIRM] Statement that MemberTrace never stores full card numbers, and any PCI wording approved by Stripe guidance.

Backups

  • The production database is backed up automatically every day, and backups are retained for 7 days.
  • A final snapshot is retained if the database is ever replaced or removed.
  • [CONFIRM] Restore testing cadence and recovery time objective.

Data handling

  • Each organization’s data belongs to that organization. Organizations can export their member data.
  • Connected third-party accounts can be disconnected at any time, and their stored data deleted, as described on our data deletion page.
  • [CONFIRM] Data retention period after an organization cancels.
  • [CONFIRM] List of subprocessors (e.g. AWS, Stripe, email providers).
  • [CONFIRM] Security contact address for reporting vulnerabilities.

Have a security questionnaire?

Send it our way and we'll work through it with you. You can also read our privacy policy and data deletion instructions.