SponsorLink Security Overview
Our commitment to protecting user details, club transactions, partner listings, and cryptographic digital passes.
Encryption in Transit
All client-server communications are encrypted using secure TLS 1.3/1.2 protocols. Session authentication cookies are signed with high-entropy keys to prevent hijacking.
Encryption at Rest (AES-256)
100% of database records, emails, member profiles, logs, and cloud storage backups are automatically encrypted at rest using AES-256 encryption. Passwords, PINs, and portal tokens are additionally protected with cryptographic hashing.
Stripe Connection Tokenization
No credit card or raw banking credentials for merchants touch our servers. Financial data is tokenized directly via Stripe Connect to guarantee complete PCI-DSS compliance.
Cryptographic Signatures
Digital wallet cards are dynamically signed. Apple Wallet passes use SHA-256 manifests with PKCS#7 signatures, and Google Wallet passes use secure SHA-256 JWT tokens.
Frequently Asked Questions
Yes. 100% of data stored in our Google Cloud SQL database (including all emails, user profiles, transaction logs, database backups, and cloud storage buckets) is automatically encrypted at rest using AES-256 server-side encryption.
No. We do not process, transmit, or store credit card numbers or raw bank account details. All billing and card authorizations are delegated directly to Stripe.
Passwords and admin credentials are hashed using PBKDF2/Bcrypt cryptographic hashes before verification, ensuring secure portal authentication.
100% of the raw database files, transaction logs, and backups are encrypted at rest using AES-256. An attacker with access to raw disk snapshot files cannot read any stored emails, member records, or system data without authorization keys.