Privacy Policy

1. Who is responsible

AItteo is operated by IE Konstantin Khalyushev, Individual Entrepreneur registered in Georgia (the ‘operator’, ‘we’, ‘us’). We determine the purposes and means of processing personal data described here and act as the data controller. Our business address is N91, Floor 1, Apartment N2 b, Iv. Javakhishvili Str, Chugureti district, Tbilisi 0162, Georgia and our registry identifier is 302253059.

For privacy questions and requests, email support@aitteo.com. This policy covers AItteo’s own processing. Apple, Google and other services you use independently also have their own privacy notices.

2. Adults only and your choices

AItteo is intended only for people aged 18 or older. Do not create an account or submit personal information if you are under 18. If you believe a child has provided information, contact us so we can investigate and arrange appropriate deletion.

Account sign-in and the information necessary to process a decision are required for the corresponding service. Voice, photos, additional context and durable preference confirmation are optional. You can use text instead of a microphone or photo. Without optional information, recommendations may be less personalized. We do not need identity documents, precise location, contact lists or payment-card details to provide the current beta.

3. Accounts and authentication

When you sign in with Apple or Google through Firebase Authentication, the authentication services process your provider identifier, credentials or tokens and profile details made available by that provider, which may include your name and email address. Apple may supply a private relay email. Our backend uses verified sign-in identifiers, an internal account identifier, access status and invitation/redemption records to authenticate you and administer beta access.

Sign-in credentials and recovery state can be stored on your device using platform storage and Keychain. We do not receive your Apple or Google password. Signing in with different providers can result in separate accounts; it does not automatically merge your information.

4. Decisions, onboarding and personalization

We process the text you submit, alternatives, context, language, clarification answers, decision results and feedback to understand the choice and generate a response. AI processing may produce interpretations, option labels, safety classifications and preference candidates. These can be inaccurate; review them before relying on them.

Free-form onboarding and adaptive questions collect what you choose to tell Teo about your preferences, habits, goals and the help you want. Before sign-in, this is associated with a pseudonymous onboarding subject and session credential. ‘Anonymous onboarding’ does not mean irreversibly anonymous data: the session can be linked to your account when you complete the linking flow.

Only preferences you confirm for durable personalization enter the confirmed preference profile. They remain available until you explicitly remove them or delete your account. Temporary answers and decision-specific clarification are separate from this durable profile. The service also maintains contextual evidence, derived personalization state and references used to explain and reproduce decisions.

Please avoid submitting sensitive information, information about other people without authority, or secrets such as passwords. Free text can reveal health, beliefs or other sensitive matters even though we do not require them. AItteo is not designed to build sensitive personal profiles or identify you from your voice. If you have submitted sensitive information, you can request its removal.

5. Voice and photo input

With your microphone permission, the app records audio after you start a recording. A temporary audio file is stored on your device for submission and recovery. Cancelled recordings are removed; submitted drafts are cleaned up by the app’s completion or discard flow. Older incomplete capture files are cleaned up when the recording directory is next opened. Uninstalling the app removes its local application storage, subject to platform behavior.

Audio is transmitted to our backend and the Microsoft Azure AI Speech service for transcription. The backend processes the recording in memory and does not persist the raw audio in its application database. This is not a promise that Microsoft never processes or retains audio under its service policies. We store the transcript and technical submission metadata, such as duration, size, audio hash, provider, status and language. A transcript used in a decision or onboarding follows the retention rules for that context.

If you choose photo input, we process the selected image and accompanying text using Azure AI to understand the alternatives. The backend stores extracted text, structured interpretation and submission metadata rather than the original photo bytes. Images can contain people, location or other private information; submit only what is necessary.

6. AI processing and safety

Microsoft Azure OpenAI processes relevant text, selected preference context, photos and transcribed voice input for interpretation and response generation; Microsoft Azure AI Speech transcribes voice input. TypeSafe’s Jev decision service receives the structured decision context needed to compare alternatives, including relevant preferences and clarification information. We send context through server-side integrations rather than embedding provider credentials in the app.

We process requests and responses to identify harmful or unsupported requests, apply limits and help prevent misuse. A refusal or safety check is not a guarantee that every unsafe or inaccurate answer will be detected. Relevant inputs, outputs, model metadata and results may be retained as described below for operation, debugging and accountability.

Personalization uses your information to tailor your experience; it is distinct from training a general-purpose model. The app does not train a general-purpose model on your content. Microsoft’s published Azure terms state that prompts and responses are not used to train foundation models or improve its or third-party products without your permission or instruction. TypeSafe’s published standard customer terms prohibit training model weights on customer data without prior consent, while allowing service telemetry, fraud/abuse monitoring and legally required processing. These commitments do not mean zero retention. Provider storage, security review and diagnostic processing are separate from model training.

AItteo offers suggestions about alternatives you supply. It does not itself execute purchases or other real-world actions, or make binding employment, credit, insurance or similar determinations. We do not intend this service to make solely automated decisions producing legal or similarly significant effects about you. You retain responsibility and independent judgment, particularly for consequential decisions. Contact us if a result or personalization seems incorrect.

7. Technical information and the website

We process account/session and request identifiers, timestamps, service events, error codes, latency, model and token/cost usage, rate-limit information and other operational metadata. These help secure accounts, enforce access and spending limits, investigate failures and understand service performance. Some are linked to your account even when the event contains no message text.

Application logs are designed to exclude raw message content and credentials, but model-call records and diagnostic records in the database can contain inputs and outputs. Hosting and network providers also receive connection information, including IP addresses and request/device information necessary to deliver and protect the service.

Our public website is hosted on Vercel. It sets no cookies and loads no advertising pixels or third-party scripts. Website usage analytics is not enabled. Hosting security and delivery processing still occur, and Vercel forwards early-access sign-ups from the website to our backend. Apple’s TestFlight separately provides beta feedback, session and crash information; what you send through TestFlight is also governed by Apple’s terms.

Early access. If you join the early-access list on our website, we store your email address (in lower case); when you first and most recently submitted it and how many times; whether you ticked the optional product-news box, and when; the version of the notice shown to you; and how you reached the form: the part of our website (such as the home page), the page address on our site, the button you used and any campaign tags (utm parameters) in the link. We do not store your name, IP address or device details with your entry, and joining the list does not create an AItteo account. To block abuse, our backend counts requests per network address in temporary memory; those counts are not stored.

We use your email address to tell you when early access opens, and to send occasional product news only if you ticked that box. Submitting the form again does not create a second entry and does not withdraw an earlier product-news choice. We have not sent any emails to the list yet; any email we send will explain how to stop receiving them.

The app and our backend send product-usage events to Amplitude, our analytics provider. Events record actions such as completing onboarding steps or requesting and finishing a decision. They exclude decision and answer text, transcripts, photos, email addresses and prompts, and use a random analytics identifier instead of your sign-in identifiers. Amplitude derives approximate country, region and city from the app’s connection IP address; we do not collect GPS location. If you enter a preferred name in the app, it is also stored in Amplitude as a profile property. We did not identify an active Firebase Analytics, Sentry or Crashlytics integration in the inspected app.

Our business email is routed through Cloudflare. If you contact us, we and our email service providers process your email address, correspondence and any attachments to respond and manage your request. Please do not include passwords or unrelated sensitive information. If the app asks for notification permission, the operating system controls that permission; the inspected app does not implement a remote push-token registration service.

8. Purposes and legal grounds

Where GDPR or comparable requirements apply, we rely on performance of our contract with you for account access, requested decision processing and the personalization you request. We rely on legitimate interests for proportionate security, fraud/abuse prevention, reliability, troubleshooting, operational usage measurement and defending legal claims. These interests are balanced against your rights and reasonable expectations.

For the early-access list, we use your email address to send the notice you asked for when early access opens, at your request. We send product news only with your consent, given by ticking the separate box; you can withdraw it at any time without leaving the list. We rely on legitimate interests to understand which pages and campaigns lead people to the list and to protect the form from abuse.

Where consent is legally required, we obtain it for the specific processing before it begins, and you may withdraw it. Device permissions are controlled in device settings. Acceptance of Terms or acknowledgment of this policy is not blanket consent to unrelated uses or a substitute for any explicit consent required for sensitive data. We rely on legal obligations when a law requires disclosure or retention. We do not use your information for targeted advertising.

9. Who receives information

Our service providers include Google/Firebase for authentication; Apple and Google for the sign-in methods you choose; Microsoft Azure for application hosting, AI/transcription, security and diagnostic infrastructure; Supabase for the hosted PostgreSQL database, including the early-access list; TypeSafe for Jev decision inference; Amplitude for product-usage analytics; Vercel for public website delivery and for forwarding early-access sign-ups to our backend; and Cloudflare for business email routing. Providers receive the information relevant to their role, not necessarily every category listed in this policy. Apple and Google also process distribution and beta information under their own policies.

Authorized operator access may be needed to maintain the service, investigate an issue or respond to your request. We may disclose information when legally required, to protect rights and safety, or in connection with a genuine transfer of the service subject to appropriate protections and legally required notices. There is no advertising-data sale or data-broker integration in the current service.

10. International processing

AItteo is operated from Georgia. The backend, database (including the early-access list) and Azure AI Speech transcription resources include United States infrastructure, and our Amplitude project uses its United States data region. The configured Azure GPT-4.1 deployment is GlobalStandard, so inference can occur in any geography where Microsoft deploys that model. TypeSafe describes US hosting; authentication, email and website providers may also process information in other locations. Your data is not guaranteed to remain in your country.

Where applicable law restricts international transfers, transfers require an appropriate legal mechanism, such as an adequacy decision or contractual safeguards with any necessary supplementary measures. Contact us for information about the safeguards applicable to your data. A provider’s availability alone does not establish that a particular transfer is lawful.

11. How long information is kept

Confirmed durable preferences do not expire with decision history. They persist until explicit preference removal or account deletion. Removal stops their use and clears the active preference content; revision/retry records and temporary source evidence can remain separately under their applicable lifecycle.

Temporary onboarding sessions normally expire after the configured 90-day history window. Session expiry makes them unavailable and the retention sweep removes temporary sources and answers. Confirmed durable preferences are preserved separately. Linking a session to an account does not mean all onboarding content is retained forever.

Decision/session history content and voice transcripts or photo interpretations associated with those decisions normally use a 90-day expiry. Raw model-call request/response payloads have a separate default 7-day retention period. The code provides retention sweeps to erase expired content; expiry is not a guarantee of physical erasure at the exact instant the window ends. Automated sweep execution has not been verified for the currently hosted beta, so expired data may remain stored until maintenance runs.

Some operational records outlive those windows. Decision shells, content-free command/retry records, archived model cost/usage records, account identifiers, identity mappings, beta-access records and security/audit metadata do not all have an automatic deletion period in the current implementation. They are retained while necessary for account administration, preventing reuse of deleted accounts, service accountability, security and applicable legal requirements. You can request a review of continued retention.

We keep an early-access entry while the early-access list is operating, unless you ask us to remove it earlier. When we stop operating the list, we will review it and delete entries we no longer need for the purpose you signed up for, including product news if you asked for it. Removal is carried out by us on request or at that review; the list has no automatic deletion period. Analytics history in Amplitude is not automatically deleted when you delete your app account; you can ask us to request its deletion.

Azure application-log retention is configured to 30 days. Provider security records and backups have their own lifecycles and may remain after active application data is removed. Deleting an account is not a promise of immediate erasure from every backup or provider system. We limit any legally required retention to the relevant information and purpose; this policy does not authorize indefinite retention for unrelated uses.

12. Account deletion and control

The iOS app provides a Delete account action. In the signed-in app, use Settings → Delete account; the sign-in/access screen also exposes deletion for an authenticated account that has not entered the main app. Confirm the request and complete any requested sign-in verification. If interrupted, follow Continue deletion until the app confirms completion.

The deletion flow first requests backend erasure, cleans local account data, handles Apple sign-in revocation when applicable, and removes the Firebase identity. These are distinct steps: a message that backend data has been deleted can still indicate pending sign-in cleanup. Deleting AItteo does not delete your Apple or Google account.

The backend erases data in a database transaction before returning a successful deletion response; this step does not wait for the periodic retention sweep. It erases application content, confirmed preferences, associated decisions, model-run content and linked onboarding data. A deleted-account marker, identity mapping and some access/security records can remain to prevent account reactivation and misuse. Independent provider logs/backups may persist under their lifecycle. Uninstalling the app or signing out alone does not request server account deletion.

See our account-deletion page for the full workflow. You may also contact support@aitteo.com for access problems or a verified deletion request. Emailing does not automatically delete an account: we must verify authority and confirm the outcome. Do not send your password or authentication token.

13. Your privacy rights

Depending on applicable law, you may request access and a copy of your information, correction, deletion, restriction, portability, or object to processing based on legitimate interests. Where processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing. You may complain to the competent supervisory authority. In Georgia, the current consolidated law identifies the State Audit Office of Georgia; if GDPR applies, you may also contact your relevant EEA authority.

To leave the early-access list or stop product news, email support@aitteo.com from the address concerned, or reply to any email we send. Leaving the list deletes your entry; stopping product news keeps you on the list for the access notice only. We may need proportionate verification when the request does not come from that address.

The backend supports data export and preference correction/deletion. The app’s available controls may differ by build; contact us if a control is unavailable. We may need proportionate verification to avoid disclosing or deleting someone else’s data. We respond within the deadlines required by applicable law, explain any permitted refusal or extension, and do not require you to waive rights to use these processes.

We do not claim that every privacy regime applies to every user. Mandatory local rights remain available where applicable. Contact support@aitteo.com to exercise rights or ask about a result, a stored preference or retention.

14. Security

We use measures designed to protect information, including HTTPS, authenticated account access, restricted database roles, hostname-verifying encrypted database connections, server-side provider credentials, limited input sizes, and protected local storage for relevant files and credentials. Access is limited according to operational needs. No service can guarantee absolute security. This is not end-to-end encryption: our backend and AI providers must process submitted content.

15. Changes and contact

We may revise this policy as the service or legal requirements change. We publish an effective date and version and provide additional notice when required. Material changes do not retroactively remove your rights. Where new consent is necessary, it will be requested separately.

Contact the operator at support@aitteo.com for privacy and support requests. The Terms of Use describe the rules and limitations of the service.