Information Security

1. Our commitment

MinhaDoula handles data about doulas and pregnant clients, including potentially sensitive information about health and pregnancy. That's why security is not an optional feature: it is a central part of the product.

We adopt practices aligned with Brazil's LGPD, its security principle (art. 6, VII) and the need for technical and administrative measures able to protect personal data.

2. Infrastructure and hosting

• Hosting: servers at a cloud provider with managed data centers (Hostinger), with the provider's physical and logical controls.
• HTTPS: encrypted communication between browser/app and our servers (TLS). In production, HTTP is redirected to HTTPS, with transport security policies when applicable.
• Separate environments: local development and production are isolated; secrets and credentials are not versioned in the code repository.
• Updates: we follow security fixes for dependencies and the PHP runtime according to the project's maintenance cycle.

3. Authentication and access control

3.1. Credentials

• passwords stored with a secure hash function (not recoverable in plain text);
• email verification for accounts created with email and password;
• verification tokens with limited validity and controlled use;
• sessions authenticated by an HTTP-only cookie, with SameSite and Secure settings in production.

3.2. Social login (Google)

Authentication via Google OAuth uses the provider's official flows (GSI / authorization code). We validate tokens on the server and do not store the user's Google password.

3.3. Two-factor authentication (2FA)

Optional 2FA (code by email and TOTP in an authenticator app) is available for doulas and clients. We strongly recommend turning it on, especially on professional accounts.

3.4. Authorization

Access to client data, finance and attachments is restricted by role (doula, client, team member) and by account (ContaId). The API does not trust identifiers sent by the client without validation on the server.

4. Encryption and transmission

• In transit: TLS 1.2+ for the website, APIs and supported integrations.
• At rest: data stays on Hostinger's infrastructure, with the protections of the contracted plan. We do not keep our own backup routine in the code; the hosting provides weekly automatic website backups.
• Application secrets: API keys, SMTP tokens and OAuth credentials in environment variables (.env), outside the public source code.

5. Per-account isolation (multi-tenant)

Each doula operates in an isolated account. Business rules and database queries are filtered by account identifier, preventing one doula from accessing another account's clients or records.

In invited portal mode, the client sees only the data explicitly shared by the responsible doula.

6. Protection of sensitive health data

For intake forms, birth plans, notes and monitoring, we apply additional layers:

• sensitivity classification of files and records;
• data minimization in application logs;
• recording of LGPD consent when applicable;
• retention policy configurable per professional account;
• export and deletion at the data subject's request, within legal limits.

The platform does not replace a clinical record. Sensitive data must be handled with the same ethical and legal care as the doula's in-person practice.

7. Files and attachments

• storage in a private area, without permanent public URLs for sensitive documents;
• signed and expiring download links, when applicable;
• upload type and size validation;
• soft delete with the possibility of administrative recovery for a limited period, before permanent deletion.

8. Payments

Card and payment instrument data is processed by certified providers (Stripe, for cards, and, in Brazil, Asaas, for Pix and boleto). MinhaDoula does not store the full card number or the payer's bank details on its servers, nor the document number typed on the Pix or boleto payment screen.

Separate financial flows are kept apart by design:

9. Backup and continuity

The production website uses weekly automatic backups provided by Hostinger, copies of the site that allow restoration in case of an incident. Some files may be excluded from these backups by the provider (for example cache and database exports on disk), according to the hosting panel's policy.

• we do not keep, in the application repository, our own daily database snapshot job;
• we recommend periodic restore tests in a controlled environment;
• data at external providers (payment, email, OAuth) follows those services' policies.

In case of data loss caused by the user's voluntary deletion, recovery may not be possible after the provider's backup retention period.

10. Audit and monitoring

• logging of relevant events (login, critical changes, administrative access);
• log correlation for incident investigation;
• review of infrastructure permissions and credentials in regular cycles;
• rate limiting and abuse protection on sensitive endpoints (sign-up, login, token resend).

Logs are kept for as long as needed for security and compliance, with minimization of sensitive content.

11. Third parties and integrations

Integrations are evaluated for security, privacy and minimum data needs. Main categories:

• Google — OAuth and, when enabled, calendar;
• Stripe — card payments and webhooks;
• Asaas — Pix, boleto and billing webhooks (Brazil);
• Transactional email — SMTP or sending API;
• Public address and city data — ViaCEP and IBGE in Brazil, U.S. Census Bureau public data for the United States.

Contracts and settings seek to prevent processors from using data for purposes incompatible with the contracted service.

12. What you can do

Recommendations for doulas and clients:

• use a unique, strong password; don't share credentials;
• turn on 2FA;
• periodically review who has access to your professional account;
• correctly set “dashboard only” vs “invited portal” mode;
• avoid sending unnecessary documents or excessive data;
• keep your device and browser up to date;
• immediately report suspicious activity to suporte@minhadoula.com.br.

13. Security incidents

We keep an internal procedure for detecting, containing, eradicating and recovering from incidents. When an incident may cause relevant risk or harm to data subjects, we will notify:

• the affected data subjects, within an appropriate time;
• Brazil's National Data Protection Authority (ANPD), when required;
• the measures taken to mitigate new risks.

To report a security vulnerability responsibly, email suporte@minhadoula.com.br with the subject “Security — responsible disclosure”. We thank researchers who follow coordinated disclosure best practices.

14. Evolution of the security program

We are continuously evolving the security program, including on the roadmap:

• versioned REST API (/api/v1) with short-lived access tokens;
• optional 2FA (email and TOTP) in production;
• periodic reviews of dependencies and attack surface;
• penetration tests before critical launch milestones;
• formal incident response and business continuity policies.

This page will be updated as new measures are implemented.

15. Contact

Questions about security or privacy: suporte@minhadoula.com.br

See also the Privacy Policy to exercise data subject rights (LGPD).