What actually protects your information.

• Every table holding personal data is protected by row-level access rules enforced by the database, so one account cannot read another account's records.
• Server-side code is the only authority on what you are allowed to see or pay for. The browser never decides your access level.
• Circle content is scoped to the Circle you belong to; losing membership ends access for both sides of a conversation.
• Administrative capabilities are restricted to a small number of explicitly assigned accounts and are recorded in an audit trail.

• Authentication is handled by a managed provider. We never see or store your password.
• Sessions use signed tokens, and requests to protected features are verified on the server on every call.
• All traffic is served over HTTPS.

• Checkout runs on Stripe's hosted pages. Card numbers never reach The Forge's servers.
• Membership status changes only through Stripe events whose signatures we verify; unsigned or forged requests are rejected.
• Each Stripe event is processed once, so a replayed message cannot alter your access.

• Bank connections are made through Plaid and are read-only.
• The Forge never receives your banking password.
• The Forge cannot move money, pay bills, or send transfers — the capability does not exist in the product.
• You can disconnect an institution at any time from Settings.

• API keys and service credentials are stored server-side only and are never shipped to the browser.
• Privileged database functions run with a fixed search path and check the calling user internally; public and anonymous execution is revoked where it is not needed.
• Database and hosting are managed infrastructure with encryption in transit and at rest, and routine backups.

• Voice notes in one-to-one conversations have no transcript and are excluded from search, AI and automation.
• Audio is reached only through short-lived links issued after a participation check.
• Deletion, membership loss and account deletion erase the audio itself through a durable deletion queue.

We do not claim SOC 2, ISO 27001, HIPAA, PCI or GDPR certification, and we do not claim end-to-end encryption: content is encrypted in transit and at rest, but the service can read it in order to work. If a security claim is not on this page, assume we have not made it.

If you find a security problem, write to info@realdadlife.ca with enough detail to reproduce it. Please do not access other people's data or degrade the service while testing. Reports are read by a person and answered.