Privacy Policy

This policy explains how Bail ("we", "us") handles your personal data. Bail is a product of aimdev, a product studio. The data controller is aimdev. For any privacy question, or to exercise your rights, contact [email protected] (this address routes directly to the studio owner).

Bail places a pre-scheduled phone call or SMS to your own phone number so you have a way to step out of a situation that has stopped feeling right. This policy is not legal advice; it is a plain-language description of our actual practices, written to meet GDPR Articles 13 and 14 and the equivalent requirements of CCPA/CPRA, LGPD, APPI, POPIA, PDPA, PIPEDA/Law 25, and the Australian Privacy Principles.

Who we are

aimdev decides why and how your personal data is processed when you use Bail. We operate the Bail app and API on aimdev.site infrastructure.

• Controller: aimdev
• Privacy contact / data-subject requests: [email protected]

What we collect

When you use Bail we process:

• Your account — created on first phone verification and keyed to your platform sign-in identity (the auth user ID from our shared sign-in, which we host ourselves). We store your credit balance and subscription status.
• Your verified phone number — the number you verify is the only number Bail will ever call or text (the "own-number" guardrail). We store it in E.164 format together with its country code and the time it was verified.
• One-time verification codes — during phone verification we store a salted SHA-256 hash of the code (never the code itself) and the phone number it was sent to, until it expires. When verification runs through Twilio's Verify service, Twilio holds this state instead.
• Scheduled calls / escapes — the persona you chose (e.g. "boss", "mom"), the scheduled time, the escape type (call, SMS, or combo), and any custom SMS body or spoken-message script you write. We store the call status and the identifier Twilio assigns to each call.
• Call and SMS events — append-only telemetry about each escape (placed, answered, completed, no-answer, etc.).
• Purchase records — credits and subscriptions are bought in the Bail app through Google Play or the Apple App Store. We store the purchase reference the store issues, the product, and its status and expiry, so we can add it to your account. We never receive your card details: they stay with Google or Apple. If you paid on the web before purchases moved into the app, we also hold the Stripe reference, amount, currency, and status of that payment; those card details were handled by Stripe and never touched our servers.
• Logs — operational logs that reference your account by ID only; we do not put raw personal data (numbers, message text) into log messages.

We do not collect your contacts, your location, or the phone numbers of any third party. Bail only ever contacts you.

Lawful basis (why we process)

• Providing the service (verifying your number, scheduling and placing your call/SMS, taking payment): performance of our contract with you (GDPR Art 6(1)(b)).
• Product analytics (see below): our legitimate interest in operating and improving Bail (Art 6(1)(f)). You can object at any time ([email protected]).
• Security, fraud prevention, and abuse limits: legitimate interest.

Sub-processors and international transfers

We share the minimum data needed with service providers who process it on our behalf under contract:

Purchases made in the app are sold to you by Google Play or the Apple App Store. They process your payment as independent controllers under their own privacy policies, not on our behalf; all we exchange with them is the purchase reference, to confirm what you bought.

We do not sell or rent your personal data, and we do not share it with advertisers or data brokers. Data-processing agreements with these providers are being finalised before our EU launch.

Analytics

Bail uses self-hosted product analytics — there is no third-party analytics service or ad-tech SDK. Events are keyed to your pseudonymous account ID and carry only counts, enums, booleans, and durations — never your phone number, message text, or any content. This telemetry is first-party and is not sold or shared.

Retention

• Account, verified phone, scheduled calls, call events, payments: kept while your account is active. When you delete your account (or leave Bail), this data is soft-deleted immediately and hard-deleted after a 30-day grace period by our automated purge.
• One-time codes: expire within minutes and are cleared on account deletion.
• Analytics events: automatically deleted after 425 days (~14 months).
• Logs: retained up to 365 days.
• Twilio-held call/SMS logs: subject to Twilio's own retention; we are adding automated deletion of these on erasure.

Your rights

Under GDPR (and equivalents in the regions listed above) you have the right to access your data, request erasure, obtain a portable copy (portability), request rectification, restrict processing, and object to processing based on legitimate interest.

• Erasure is available in two ways: in the app (Profile → Delete my account), and by emailing [email protected]. Deleting your account removes your Bail data (account, verified number, scheduled calls, call history, and payment records) after the 30-day grace period.
• To exercise access, portability, rectification, restriction, or objection, use Profile → Download my data or email [email protected]. We respond within 30 days (15 days for Brazil under LGPD, 45 days for California under CCPA where applicable).
• If you are in the EEA or UK you may also lodge a complaint with your local data protection supervisory authority.

Children

Bail is not directed at children and is intended for users of the age of digital consent in their jurisdiction.

Changes

We will update this page and its "last updated" date when our practices change.