Security
A shul's records — its members, its finances, its yahrzeits — deserve the same care as any financial system. Here's how ShamashHub protects them.
Tenant isolation
Every shul's data is scoped to its organization at the database level. Every query on every request is filtered by organization — one shul can never see another's records.
Encryption
All traffic runs over TLS. Data is encrypted at rest, and sensitive credentials such as payment-processor keys are additionally encrypted at the application layer.
Per-user permissions
Access inside a shul is granular: each staff member sees only the modules and sections they were granted. Fundraisers, gabbaim, and office staff each get exactly their slice.
Payments
Platform billing runs through Stripe; donor card payments run through your own processor. Full card numbers never touch our servers.
Authentication
Passwords are stored with strong one-way hashing. Sessions are short-lived signed tokens, and staff access can be revoked instantly by an administrator.
Backups
Databases are backed up continuously with point-in-time recovery, so an accidental deletion in the office is recoverable.
Found a vulnerability, or have a security question before signing up? Contact us — security reports go straight to the engineering team.