Ami Privacy Policy

Effective Date: October 12, 2026 Last Updated: October 12, 2026

This Privacy Policy applies to the Ami iOS application and its backend services (the “Service”). It explains how BFAI Technologies, Inc. (“BFAI Technologies”) collects, uses, stores, shares, and protects Personal Data in connection with the Ami iOS application and its backend services (the “Service”). This Privacy Policy is incorporated into, and should be read together with, our Terms of Service. Capitalized terms not otherwise defined in this Privacy Policy have the meaning given to them in our Terms of Service.

This Privacy Policy may be amended by us from time to time as described in Section 17 (Changes to This Policy) below. As amended, this Privacy Policy will be binding upon you.

1. DEFINITIONS

The following capitalized terms have the meanings given below wherever they are used in this Privacy Policy. Capitalized terms not otherwise defined here have the meaning given to them in our Terms of Service.

"Ami" means the Service, as branded and made available by us.

"BFAI Technologies,” “we,” “us,” and “our" mean BFAI Technologies, Inc., together with its Affiliates.

"Data Controller" means the entity that determines the purposes and means of Processing Personal Data. We act as the Data Controller for the Personal Data described in this Privacy Policy.

"Memory" means the durable facts Ami may save about you, when you turn Memory on, to personalize future conversations, as described in Section 4.4.

"Output" has the meaning given in our Terms of Service.

"Personal Data" means any information relating to an identified or identifiable individual, and includes what certain laws refer to as “personal information.”

"Pilot" means the current invite-only, pre-release phase of the Service.

"Processing" means any operation performed on Personal Data, including collection, storage, use, disclosure, and deletion, and “Process” has a corresponding meaning.

"Sale,” “Sell,” and “Share" have the meanings given to them under applicable U.S. state privacy laws, including the California Consumer Privacy Act, as amended by the California Privacy Rights Act (together, the “CCPA”). As described under “Sale and Sharing of Personal Data” below, we do not Sell or Share Personal Data.

"Sensitive Personal Data" means Personal Data that receives heightened protection under applicable law, including what the CCPA refers to as “sensitive personal information” and what the GDPR refers to as “special category data,” such as information revealing health or mental or emotional state.

"Service" means the Ami iOS application and its backend services, including its AI coaching and companion features, Memory, reminders, check-ins, and any related websites or services we operate.

"Subprocessor" means a third party that Processes Personal Data on our behalf and under our instructions, as described in Section 8 and Appendix A.

"User,” “you,” “your,” and “yours" refer to the individual who creates an account or otherwise accesses or uses the Service.

"Your Content" has the meaning given in our Terms of Service.

2. WHO WE ARE

Ami is a whole-life assistant and executive-functioning coach delivered as an iOS app, designed to work the way a trusted mentor or accountability partner would: keeping track of your schedule, preferences, and chosen metrics, and helping you meet your goals or recalibrate when you don’t. This Policy explains what Personal Data we collect, how it is used, who it is shared with, and the choices and rights you have.

The Data Controller is BFAI Technologies, Inc., 135 East 57th St, Floor 15, New York, NY 10022, United States. You can reach us about privacy at contact@bfaitechnologies.com.

Ami is currently offered as a closed Pilot to a small number of invited participants. Some practices described here, including optional Apple device integrations, may change as the product develops. We will update this Policy and, where required, ask for your consent again before enabling a new integration.

3. SUMMARY

(i) You sign in with Apple. We never see or store a password, and there is no email/password login.

(ii) Ami is a coaching and companion service, so much of what you tell it is personal: your goals, your routines, how you’re doing. We handle that as the core of the Service, not as a by-product to be monetized.

(iii) We use OpenAI to power the AI. Your messages and voice are processed by OpenAI to generate Ami’s responses. We disable provider-side response storage where supported and rely on OpenAI’s API policy that inputs and outputs are not used to train its models by default. Provider safety and operational processing may still apply. Realtime voice audio is never stored by us.

(iv) You are in control of Memory and voice history. Ami only keeps durable Memory about you when you turn Memory on, and you can inspect, correct, or delete it. Saving voice transcripts is off by default.

(v) Device access is opt-in. Notifications, calendar, reminders, microphone, Health, movement, location, and any future alarm integration are off until you enable them, and granting one never silently enables another.

(vi) We do not sell your Personal Data and do not use it for third-party advertising.

(vii) You can delete your account from within the app, which removes your Personal Data from our systems (subject to the limited, redacted operational records described in Section 9).

This summary is for convenience only; the sections below control.

4. INFORMATION WE COLLECT

Ami is designed to minimize collection: several categories exist only if you turn a feature on.

4.1 Account and identity

1. Sign in with Apple identifier: Apple gives us a unique identifier for your account. Depending on your choice at sign-in, Apple may also provide your name and an email address (which may be an Apple private-relay address that forwards to you). This is held by our authentication provider (Supabase Auth). We never receive your Apple password.

2. Profile details you provide: a display name (the short name Ami uses in conversation), your full name (if provided), time zone, and locale/language.

4.2 Consent records

A versioned, append-only record of the consents you give or withdraw, to the Terms of Service, this Privacy Policy, Memory, proactive notifications, calendar access, and voice, each with the policy version and a timestamp.

4.3 Your preferences and settings

Coaching style, quiet-hours window, Memory on/off, save-voice-transcripts on/off, action approval mode, and your chosen Ami voice.

4.4 What you tell Ami (service content)

1. Intake answers: a short conversational intake (about six questions) about your life, priorities, and how you’d like to be coached. We do not ask for your date of birth or age.

2. Life model, goals, and plans: the life areas, goals, plans, pursuits, commitments, and outcomes you create or that Ami drafts with you.

3. Chat history: the text of your conversations with Ami is stored so you have history and continuity. You can rename and delete individual conversations.

4. Voice conversations: your speech is streamed directly from your iPhone to OpenAI and processed live. Ami does not retain the raw audio. The text transcript of a voice session is saved only if you turn on “Save voice transcripts,” which is off by default. Text you type during a voice session is saved like ordinary chat.

5. Memories: when Memory is enabled, Ami may save durable facts about you to personalize future conversations. You can review, correct, and forget these in Settings → What Ami knows. Credential-like and high-risk identifier patterns are discarded rather than saved. We also generate a mathematical representation (“embedding”) used to organize Memory.

4.5 Device permissions

With your permission, Ami uses certain iPhone capabilities. Each is requested through the standard iOS permission prompt, is optional, and is revocable in iOS Settings. See Section 7 for the full detail of every Apple integration.

1. Microphone: during voice conversations you start (including, if you enable Background conversations, while in other apps or with the screen locked). Audio is not stored by Ami.

2. Notifications: to deliver the proactive check-ins you opt into.

3. Calendar and Reminders: to show your day and, for reminders, to create/edit/complete one when you ask (Section 4.6).

4. Camera: used only if you choose to share visual context during a conversation, on the same basis during the Pilot as it will be following general availability.

4.6 Calendar and reminders (on-device)

With permission, Ami can read selected calendar events and reminders to show your day and answer questions. Relevant titles, times, and reminder completion state can be shared with Ami and OpenAI when you ask about them. If you separately enable personal check-ins and sharing for a source, Ami also stores selected context on its servers to prepare those check-ins. Device permission alone does not enable this sharing. Shared context and AI responses can be part of conversation history.

Ami’s calendar access is read-only: it never creates or changes calendar events. For reminders, Ami may create, edit, or complete a reminder when you ask, following your approval setting.

4.7 Technical and operational data

Optional Google and Microsoft connections: if you connect an account, Ami stores the connection credentials needed to access the permissions you grant. Email and calendar access are separate from Apple sign-in. Relevant message or event content, saved task results, and action proposals may be processed by Ami and OpenAI for requests and the separately enabled background tasks you choose. Sending a reply or creating an event follows the app’s approval flow. You can disconnect in Settings.

1. AI usage ledger: for each AI request we record a redacted operational row, model used, token counts, estimated cost, and a short error class, to enforce usage limits and control cost. It does not contain the content of your messages.

2. Audit events: a server-written, redacted record of sensitive operations (for example, an account deletion) for security and integrity. Metadata is limited operational context, not message content.

3. Push registration: if you enable notifications, we store an Apple Push Notification service (APNs) device token, platform (iOS), and app version. Lock-screen copy is generic; the payload carries only internal routing identifiers. We also record whether a check-in was opened or acted on.

What we do not collect: we do not use third-party analytics or advertising SDKs, and the app does not collect a device advertising identifier. This is accurate during the Pilot and will remain accurate following general availability, including at App Store launch.

5. HOW WE USE YOUR INFORMATION

We do not use your Personal Data to train our own models, we do not sell it, and we do not use it for cross-context behavioral advertising. See Section 11.1 for a fuller explanation of these legal bases for individuals in the EEA, UK, or similar jurisdictions.

6. HOW AMI WORKS WITH AI PROVIDERS

Ami’s intelligence is provided by OpenAI. Understanding this data flow is important:

1. Text coaching and intake: your relevant context and messages are sent to OpenAI’s API to generate Ami’s replies. We send these requests with the provider-side storage opt-out (store: false) and a one-way safety identifier, and rely on OpenAI’s API data policy under which API inputs and outputs are not used to train OpenAI’s models.

2. Memories: when Memory is enabled, memory text may be sent to OpenAI to generate the embedding described in Section 4.4, but only while your current consent is in force.

3. Realtime voice: your iPhone connects directly to OpenAI over an encrypted WebRTC connection. Audio is processed in real time to hold the conversation. We never retain the raw audio.

4. Device context: when you ask about a supported source, a bounded result can be included in the AI turn as untrusted data. Separate personal-check-in consent permits selected context to be stored and used for relevant check-ins. Raw Health samples and raw visit-history coordinates are not uploaded.

We send OpenAI only what is needed for the immediate request. OpenAI acts as our Subprocessor for this purpose (Appendix A).

7. APPLE SERVICES AND DEVICE INTEGRATIONS

Ami is an iOS app and relies on a number of Apple services. This section lists every Apple integration active in the Pilot today, and, for completeness, the Apple integrations that are planned but not yet enabled. Where an Apple feature involves your Personal Data, Apple acts as an independent controller under Apple’s own Privacy Policy for its part of the processing.

7.1 Apple integrations active in the Pilot

There is no separate Apple Watch app in this Pilot. With your permission, Ami can read supported information that Apple Watch has written to Health on your iPhone.

7.2 Planned Apple integrations (not active in the Pilot)

The following are on our roadmap and are described here for transparency. They are not enabled in the current Pilot. Each will be opt-in, gated by both an explicit iOS permission and an in-app consent, and we will update this Policy before enabling it.

Guardrails we apply to device integrations: on-device-first processing; explicit per-feature consent, separate from account sign-up; we do not persist raw audio or raw HealthKit samples in our backend; we do not collect date of birth or age during onboarding; and granting one permission never silently enables another.

8. WHEN WE SHARE INFORMATION

We share Personal Data only with the Subprocessors that operate the Service on our behalf, and only as needed to run the Service. We do not sell it or share it for advertising.

(i) Supabase, our backend platform: database, authentication, and serverless functions. Processing region: United States (us-east-1).

(ii) OpenAI, AI processing for text, voice, and embeddings, as described in Section 6.

(iii) Apple, Sign in with Apple, push notifications, TestFlight, and the on-device integrations in Section 7.

We may also disclose information if required by law or to protect the rights, safety, and security of our users, the public, or BFAI Technologies. If BFAI Technologies is involved in a merger, acquisition, or asset sale, information may transfer as part of that transaction, subject to this Policy. This applies during the Pilot on the same basis as it will following general availability of the Service.

Google and Microsoft act under their own terms for the optional connected accounts you authorize. Ami sends them the account requests and approved actions needed for your selected features; it does not receive your Google or Microsoft password.

A current Subprocessor list is in Appendix A.

9. HOW LONG WE KEEP YOUR INFORMATION

We keep Personal Data for as long as your Account is active or as needed to provide the Service, then delete or de-identify it. Automated retention jobs enforce the following:

Account deletion. When you delete your account in the app, we remove your authentication record, which cascades to delete your profile, Memory, embeddings, goals, commitments, proposals, pursuits, consent records, devices, and notification data. Two categories are intentionally retained in redacted, de-identified form (no longer linked to you) as operational and security records, namely the usage ledger and audit events, plus a deletion tombstone that records that the deletion occurred. These follow the retention windows above.

10. YOUR CHOICES AND CONTROLS (IN THE APP)

(i) Memory on/off, plus inspect, correct, and forget any Memory (Settings → What Ami knows). Turning Memory off stops new saves without deleting what’s already there.

(ii) Save voice transcripts: off by default.

(iii) Approval mode: choose whether Ami acts on a proposal automatically or pauses for your review.

(iv) Proactive notifications: off until you opt in (and grant iOS permission); durable pause, resume, and stop controls; quiet hours.

(v) Calendar, Reminders, Health, Location, Motion, Microphone, Camera: granted through the iOS permission prompt and revocable in iOS Settings at any time.

(vi) Delete individual conversations, or delete your entire Account.

11. YOUR PRIVACY RIGHTS

Depending on where you live, you may have some or all of the rights described below. These rights, and the sections below describing them, apply during the Pilot on the same basis as they will following general availability of the Service.

11.1 European Economic Area, United Kingdom, and similar jurisdictions (GDPR / UK GDPR)

If you are located in the EEA, the UK, or a jurisdiction with similar data protection law, the General Data Protection Regulation (GDPR) or the UK GDPR gives you the following rights over your Personal Data, in each case subject to the exemptions available under applicable law:

1. Right of Access: you may request confirmation of, and access to, the Personal Data we hold about you, together with certain related information (such as the purposes of Processing and who we share it with).

2. Right to Rectification: you may request correction of inaccurate or incomplete Personal Data.

3. Right to Erasure: you may request deletion of your Personal Data in certain circumstances, for example where it is no longer necessary for the purposes it was collected.

4. Right to Restriction of Processing: you may request that we limit how we use your Personal Data in certain circumstances, for example while a correction or objection request is being assessed.

5. Right to Data Portability: you may request a copy of the Personal Data you provided to us in a structured, commonly used, machine-readable format, and, where technically feasible, ask us to transmit it to another controller.

6. Right to Object: you may object to Processing based on our legitimate interests, including profiling, on grounds relating to your particular situation.

7. Right to Withdraw Consent: where Processing is based on consent (such as Memory, proactive notifications, or a device permission), you may withdraw that consent at any time, without affecting the lawfulness of Processing before the withdrawal.

8. Right to Lodge a Complaint: you may lodge a complaint with your local data protection supervisory authority, or the supervisory authority of the EU or UK member state where you live, work, or where the alleged infringement occurred.

We aim to respond to a verified GDPR/UK GDPR request within one (1) month of receipt; if a request is complex or we have received a number of requests, we may extend this by a further two (2) months and will explain why.

If Pilot participants are located in the EEA or UK, we will appoint an Article 27 GDPR representative and, where applicable, a UK representative, on the same basis as we would following general availability of the Service.

11.2 California Residents (CCPA/CPRA)

This section supplements the rest of this Privacy Policy and applies specifically to individuals who reside in California, consistent with the California Consumer Privacy Act, as amended by the California Privacy Rights Act (together, the “CCPA”).

In the preceding twelve (12) months, we have collected the categories of Personal Data described in Section 4, which correspond to the following CCPA categories: identifiers; internet or other electronic network activity information; audio and voice information (only transiently, as described in Section 4.4); and, if you choose to share it, sensitive personal information revealing health or mental or emotional state (for example, through coaching conversations or an optional Apple Health summary). We collect these categories from the sources, and use and disclose them for the purposes, described in Sections 4, 5, and 8 above. We retain each category for the periods described in Section 9.

Your CCPA Rights

1. Right to Know or Access: you may request confirmation of, and access to, the specific pieces and categories of Personal Data we hold about you.

2. Right to Correct: you may request correction of inaccurate Personal Data we hold about you.

3. Right to Delete: you may request deletion of your Personal Data, subject to exceptions such as our need to complete a transaction, comply with a legal obligation, or exercise legal claims.

4. Right to Data Portability: you may request a copy of your Personal Data in a portable format.

5. Right to Opt Out of Sale or Sharing: as noted in Section 8, we do not Sell or Share Personal Data, so no opt-out is currently necessary; if this changes, we will provide a means to opt out, including honoring the Global Privacy Control where technically required.

6. Right to Limit Use of Sensitive Personal Information: you may request that we limit our use of sensitive personal information (such as information revealing health or mental or emotional state) to purposes necessary to provide the Service you requested; we do not use sensitive personal information to infer characteristics about you.

7. Right to Non-Discrimination: we will not deny goods or services to you, charge different prices, or provide a different level of service because you exercised a CCPA right.

8. Right to Appeal: if we decline to act on your request, you may appeal by contacting us using the information in Section 15.

California’s “Shine the Light” law (California Civil Code Section 1798.83) permits California residents to request information about our disclosure of Personal Data to third parties for their own direct marketing purposes in the preceding calendar year. We do not disclose Personal Data to third parties for their own direct marketing purposes.

To exercise any of the rights above, please contact us using the information in Section 15. We will take reasonable steps to verify your identity before responding, which may require you to provide additional information. You may designate an authorized agent to make a request on your behalf, subject to our ability to verify the agent’s authority and your identity. We will respond within forty-five (45) days of a verifiable request; if we need more time, we will notify you of an extension of up to an additional forty-five (45) days.

11.3 Other U.S. State Privacy Laws

If you reside in Virginia, Colorado, Connecticut, Utah, or another U.S. state with a comprehensive privacy law, you generally have similar rights to those described in Section 11.2 above: to confirm processing, access, correct, delete, and receive a portable copy of your Personal Data, and to opt out of the sale of Personal Data, targeted advertising, or certain profiling. As noted throughout this Policy, we do not sell Personal Data or use it for targeted advertising. Where these laws provide a right to appeal a decision on your request, you may do so by contacting us using the information in Section 15.

11.4 Exercising Your Rights

Many of the choices above you can exercise yourself in the app (Section 10). For anything else, including access to or a copy of your data, contact us using the information in Section 15. We verify requests against your authenticated Account and respond within the time required by applicable law.

12. AUTOMATED DECISION-MAKING AND PROFILING

Ami uses AI to personalize coaching, for example, tailoring check-ins, suggestions, and nudges to your stated goals, routines, and (if Memory is enabled) saved preferences. This involves a degree of profiling, but we do not use Personal Data to make decisions that produce legal effects concerning you or that similarly significantly affect you based solely on automated processing, without the opportunity for human review. You may object to profiling based on our legitimate interests as described in Section 11.1, and you can always disable Memory or adjust your preferences in the app as described in Section 10.

13. HOW WE PROTECT YOUR INFORMATION

(i) Access control by default. Every data table enforces row-level security with a default-deny posture, so you can only ever reach your own data. The most sensitive tables are reachable only by our trusted server functions, never directly by the app.

(ii) Encryption. Encryption in transit for all connections (to our backend and to OpenAI); encryption at rest is provided by our hosting platform; your session is held in the iOS Keychain.

(iii) Secret isolation. The app itself holds no service credentials; AI and push keys live only in server-side secret storage.

(iv) Integrity by design. Consent, Memory history, and audit records are append-only; AI spending is admitted through the database so limits can’t be raced; prompt versions are pinned and verified.

No method of storage or transmission is 100% secure, and we cannot guarantee absolute security. In the event of a Personal Data breach, we will notify affected individuals and, where required, regulators, without undue delay and in accordance with applicable law.

14. INTERNATIONAL DATA TRANSFERS

Ami’s backend and AI processing currently take place in the United States. If you use Ami from outside the United States, your information will be transferred to and processed there. Where such a transfer is subject to the GDPR or UK GDPR, we will rely on an appropriate transfer mechanism, such as the European Commission’s Standard Contractual Clauses or the UK International Data Transfer Addendum, as applicable. This applies during the Pilot on the same basis as it will following general availability of the Service.

15. CONTACT US

Questions, requests, or concerns about your privacy:

BFAI Technologies, Inc.

contact@bfaitechnologies.com

135 East 57th St, Floor 15, New York, NY 10022, United States

16. CHILDREN'S PRIVACY

Ami is not directed to children and is intended for users 18 and older. We do not knowingly collect Personal Data from children, and we do not ask for date of birth or age during onboarding. If you believe a child has provided us information, contact us using the information in Section 15 and we will delete it.

17. CHANGES TO THIS POLICY

We may update this Policy as Ami evolves (for example, when we move from Pilot to general availability, or when we enable a planned Apple integration). We record the version you agreed to, and for a material change we will notify you in the app and, where required, ask for your consent again. The “Last Updated” date reflects the current version. As amended from time to time, this Policy is binding upon you.

APPENDIX A: SUBPROCESSORS (CURRENT PILOT)