Privacy Policy
A.M.I.E. is a private beta assistant operated by Joel Chiprut. This policy explains what the service handles and why.
Information handled
- Beta signup and account details, including name, email, company, job title, username, and owner-assigned access settings.
- Content you deliberately send to A.M.I.E., such as messages, files, preferences, and work requests.
- Security and reliability records such as sign-in time, audit events, and request status.
- Data from an external account only after its account holder authorizes the requested OAuth permissions.
How information is used
Information is used to provide the service, preserve requested continuity, authenticate users, complete authorized work, prevent abuse, and improve reliability. A.M.I.E. does not sell personal information or use it for third-party advertising.
Age verification
A.M.I.E. asks for a brief age check to distinguish adult accounts from protected minor accounts, apply age-appropriate capabilities, and enable parent-managed Family controls where required.
What A.M.I.E. keeps: the date of birth entered during signup, the verification provider and session reference, whether verification succeeded, the resulting age tier (adult, age 13–17, or under 13), and the verification time.
What A.M.I.E. does not keep: the ID image, selfie image, document number, date of birth returned separately by the verification provider, or biometric template. Stripe processes the verification materials under Stripe’s own privacy and retention terms.
Service providers and connected accounts
Authorized content may be processed by the configured AI model provider and hosting infrastructure. Salesforce, Slack, Microsoft, and connected Google services use provider authorization and encrypted tokens; their account passwords are never stored by A.M.I.E. iCloud accepts only an Apple-generated app-specific password for supported Mail, Calendar, and Contacts access, never the main Apple Account password. Connected-system credentials are excluded from chat, memory, model prompts, source, audit details, and browser responses.
Live voice and call audio
When you start live voice, microphone audio is transmitted to the configured AI model provider in real time to produce the conversation. If you explicitly choose Hear a Call, the audio track from the screen, window, or tab you share is mixed with the microphone and transmitted too. The required shared video track is never read, analyzed, or transmitted by A.M.I.E. A.M.I.E. retains the resulting text turn for continuity when a live turn is recorded, but does not deliberately retain the raw live-audio stream in its application database. Do not use live voice or call audio unless every participant has given permission.
Retention and deletion
Account information, messages, uploaded files, A.M.I.E.-created files, and user-authorized connection grants are retained to operate the private beta and maintain requested continuity. You can disconnect an individual system from Connected Systems. You can initiate deletion from the signed-in account page or the public deletion page; completing it removes the beta account, private conversation, file library, encrypted connection grants, and signup record and anonymizes the deletion log.
Security and choices
A.M.I.E. uses signed HttpOnly sessions, one-way password hashing, encrypted connector credentials, access controls, and audit records. No system can guarantee absolute security. You may revoke a connected service through that provider and sign out of A.M.I.E. at any time.
Children and family accounts
An adult parent or guardian may create a Family account and add supervised child profiles. Child profiles receive age-appropriate restrictions; for children under 13, the parent account can review search and chat history.
Contact
Privacy and account questions: Amie@getmeamie.com.