App Encryption Documentation

The Apostolic Pulse — Security & Data Protection Overview

Last updated: April 2026

The Apostolic Pulse takes the security and privacy of its users seriously. This document describes the encryption methods and security measures employed to protect user data at every layer of the application. Our infrastructure is built on the Base44 platform and adheres to industry-standard security practices.

Data in Transit

All data transmitted between the app and our servers is encrypted using HTTPS/TLS 1.2 or higher.
This applies to all API calls, file uploads, media streaming, and authentication flows.
Certificate pinning is enforced to prevent man-in-the-middle attacks.

Data at Rest

All user data stored in our database is encrypted at rest using AES-256 encryption.
File uploads (profile pictures, media attachments, voice notes) are stored in encrypted cloud object storage.
Database backups are also fully encrypted.

Authentication & Sessions

User passwords are never stored in plaintext — they are hashed using bcrypt with a unique per-user salt.
Session tokens are cryptographically signed JWTs with short expiration windows.
All authentication flows are handled via the Base44 platform, which enforces secure credential management.

Access Control

Row-Level Security (RLS) is enforced at the database level — users can only access data they are authorized to see.
Admin-only operations require server-side role verification before execution.
All sensitive backend functions validate the authenticated user before processing any request.

Third-Party Services

The app uses Base44 as its backend-as-a-service provider, which complies with industry-standard security practices.
Media and file storage is handled via encrypted cloud infrastructure.
No encryption keys are stored client-side or exposed to the frontend.

© 2026 The Apostolic Pulse. All rights reserved.

Privacy Policy·Terms of Use·Home