Oraivex AI is strictly for adults aged 18 or older
You must be 18 or older to install, register, purchase, access or use Oraivex AI. The birth-date gate is designed to allow only a date on or before the exact calendar date eighteen years before setup. There is no parent-or-guardian authorization path for a minor. Anyone under 18 must not use the app.
1. Controller, operator and scope
Oraivex AI is operated by its independent developer from Lebanon under the Oraivex AI name. For privacy questions, rights requests or complaints, contact support@oraivexai.com.
This policy covers the Android app, the Oraivex website, Google Sign-In, subscriptions, requested AI features, Coach, Mind Room, image tools, optional precise foreground location for Weather and requested live nearby search, notifications, server security, support and account deletion.
Oraivex is a general wellness, fitness, planning, nutrition-estimation and reflection product. It is not a medical device, healthcare provider, therapist or emergency service.
2. Clear data flow — where your information goes
Stored on this phone: Body profile, feelings, plans, Lab and photo history, sleep, Mind Room memory, detailed coin explanations and detailed intelligence history are normally stored locally on this phone.
Removed sensitive profile inputs: Current Oraivex builds do not ask for or keep dedicated allergy, medical-condition, injury, pain or movement-consideration profile selections. Legacy selections from older builds are removed from the local body/nutrition profile. These fields are excluded from online AI requests, and the Oraivex server strips them from older-client payloads before Google Gemini processing.
Removed location memory: Oraivex no longer creates map trails, saves named places, links Wi-Fi networks to places, or keeps feeling, score, photo or proof history tied to a place. A live nearby search remains available only when the user requests it; its results are not saved as place history. The app update clears legacy Oraivex map, saved-place, Wi-Fi-place and place-based feeling memory.
Sent online when you use an AI feature: AI requests go through the Oraivex API hosted on Hugging Face Spaces to Google Gemini. Depending on the feature, the request can include your text, a selected image, live audio or transcript, and the specific profile, plan, score or derived weather measurements needed for the result. Oraivex does not send GPS coordinates, readable location labels, nearby-place results, directions, map history, saved-place labels, Wi-Fi identifiers or place-based feeling history to Gemini. A location word that you deliberately type remains part of your own request.
Why precise location is used: Precise foreground location is optional and used only when you request current Weather or a live nearby-place search. For Weather, rounded coordinates go through the Oraivex API to MET Norway; a city or country typed in Weather may go to OpenStreetMap Nominatim. For nearby search, current coordinates and search words may go to OpenStreetMap Overpass or Nominatim to find supermarkets, pharmacies, gyms, cafés and similar useful places. If you open directions, Google Maps receives the selected destination. Oraivex does not request background location or build location history. Only derived weather measurements—not GPS coordinates, location labels or nearby results—may be included in Gemini prompts.
Other providers: LiveKit carries active Coach and Mind Room audio, video or data. Google Sign-In and Firebase handle account identity and security. Google Play and RevenueCat handle purchases and subscription access.
Server records: Firebase and the Oraivex server keep account identity, billing and entitlement state, trials, quotas, live-minute balances, request status, anti-abuse markers and the current coin balance. Oraivex is not designed to keep readable AI prompts, images, live audio or detailed results in Firestore after a request finishes.
Provider retention: Google says Gemini API prompts, context and outputs may be kept for up to 55 days for abuse monitoring. LiveKit retention depends on the deployed project settings and provider policies. Oraivex does not promise zero provider retention.
Background processing: Supported Android builds may show a foreground health-service notification while recording supported steps, motion and local score snapshots. This service does not enable background location, camera or microphone recording.
3. Categories, purpose, destination and retention
| Category | Examples and purpose | Where it goes | Oraivex retention |
|---|---|---|---|
| Account identity | Google subject/account ID, email, display name and sign-in timestamps to authenticate, restore access and process deletion. | Device cache; Oraivex backend; Firebase/Google identity services. | While the account is active; eligible readable account records are deleted after confirmed account deletion, subject to minimized security/legal exceptions. |
| Birth date and adult eligibility | Birth date and calculated age to enforce 18+, personalize adult wellness estimates and support birthday features. | Primarily protected local storage. A calculated age or age range may be sent only when the selected AI feature needs it for the requested wellness result; the full birth date is excluded from Paid Intelligence and Life OS requests. | Local until edited, cleared, account deletion, app-data clearing or uninstall. Oraivex does not describe the birth date as government identity verification. |
| Body and wellness profile | Height, weight, body goal, difficulty, wake/sleep schedule and calculated targets for adult fitness and wellness personalization. Oraivex does not collect dedicated allergy, medical-condition, injury, pain or movement-consideration profile fields. | Primarily device storage. Depending on the selected feature, only the specific body goal, difficulty, wake/sleep schedule or calculated target needed for the result may pass through the Oraivex API to Google Gemini. Legacy removed-profile fields are stripped by the app and server. | Local until user deletion; not intentionally stored as readable AI-result history on the backend. |
| Plans and personal intelligence | Plan, Flow, Right Now, Life OS, Paid Intelligence, check-ins, Day/Future plots, feedback and pattern learning. | Saved primarily on-device. A requested AI feature may send the typed request and only the plan, score, sleep summary, feedback, pattern summary or Lab memory listed for that feature through the Oraivex API to Google Gemini. | Local exact pattern and compact daily intelligence memory may be retained for up to 365 days; other local content remains until cleared. |
| Steps, movement and sensors | Step totals, estimated distance, motion/stillness, light, sound-level numbers and score snapshots for walking and wellness estimates. | Primarily on-device. A visible Android foreground health service may save supported local snapshots. A requested AI feature may receive the current step total, estimated distance, motion state, light level, sound-level number or score summary only when that feature needs it. | Local retention follows feature history and user controls; no background location, microphone or camera foreground service is intended. |
| Photos, camera and pose | Food, menu, outfit, progress, proof, room and optional current camera images; Coach pose guidance and live visual coaching. | Original files remain in app-controlled device storage. Requested compressed images pass through the Oraivex backend to Google Gemini. Coach pose counting uses on-device Google ML Kit where supported; an active LiveKit Coach session may transmit camera media when the user turns it on. | Oraivex does not intentionally store original Lab photos in Firestore or keep a permanent backend photo archive. Local originals remain until cleared. Provider security/operational retention may apply. |
| Voice and live sessions | Microphone audio, transcript, prompts, room ID, heartbeat, duration and technical metadata for Coach and Mind Room. | LiveKit transports real-time media/data; the Oraivex backend and Google Gemini generate live assistance. Android/Google speech services may process speech recognition when separately selected. | No intentional permanent raw-audio archive by Oraivex. Session/billing metadata remains as needed for usage, fraud and support; provider observability or security logs may have separate retention. |
| Precise foreground location | Optional coordinates and accuracy for requested current Weather or a live nearby-place search; a city or country typed into Weather; and search words such as supermarket, pharmacy, gym or café. | For Weather: device, authenticated Oraivex backend and MET Norway; OpenStreetMap Nominatim when a Weather place is typed. For nearby search: device and OpenStreetMap Overpass or Nominatim. Google Maps receives a selected destination only when directions are opened. Only derived weather measurements—not GPS coordinates, readable location labels or nearby results—may be included in Google Gemini requests. | Oraivex does not create map trails, save named places, build Wi-Fi place memory or keep feelings tied to places. Weather forecasts/geocoding may use bounded server-memory caches; live nearby results are used for the requested lookup and are not written as readable place history to Firestore. Oraivex does not request Android background-location permission. Providers may retain connection or query logs under their policies. |
| Purchases, quotas and coins | Product ID, entitlement, subscription/trial status, purchase transaction identifiers, live-minute balance, quota counters and current coin balance. | Google Play, RevenueCat, Oraivex backend and Firebase/Firestore. | Active-account state while needed; transaction, tax, fraud, chargeback and anti-abuse records may be retained for legal/business needs. Google Play and RevenueCat keep independent records. |
| Security, diagnostics and signup funnel | One-way install/device markers, App Check/Play Integrity result, request ID, feature/stage, status, timing, app/build/platform and limited error code. | Oraivex backend and Firebase/Firestore; Google/Firebase attestation services. | Minimized for reliability, deduplication, fraud and abuse prevention. Funnel records do not contain the user’s prompts, photos, voice, device location, GPS coordinates, map history, Wi-Fi identifiers or wellness profile. |
| Support communications | Email address, message content and attachments voluntarily sent to resolve a request. | Oraivex support email provider and relevant service provider only when needed. | For the time needed to resolve the request and meet security, billing or legal obligations. |
4. Named service providers and exact roles
| Provider | Role | Data that may be processed |
|---|---|---|
| Google Gemini | Principal generative-AI provider for requested text, image analysis and live AI output. | The typed request or transcript, selected/compressed image, live-session audio, video or data, generated output, and the specific profile, plan, score, sleep or derived weather measurements needed for the selected result. Dedicated allergy, medical-condition, injury, pain and movement-consideration profile fields are not collected or forwarded. Oraivex excludes GPS coordinates, readable location labels, nearby-place results, directions, map history, saved-place labels, Wi-Fi identifiers and place-based feeling history. Paid Intelligence and Life OS also exclude account name, email, Google/Firebase identifier and full birth date. Requests go through the authenticated Oraivex API; the mobile app does not contain the Gemini secret key. Google says Gemini API prompts, context and outputs may be kept for up to 55 days for abuse monitoring. Oraivex does not promise zero provider retention. |
| Hugging Face Spaces | Hosts the Oraivex authenticated backend/token service. | Authenticated requests, request metadata, feature payloads in transit, quota/billing calls and limited operational logs. |
| Google Identity / OAuth | Google Sign-In and token verification. | Google account ID, email, display name, authentication tokens and verification timestamps. Oraivex does not receive the Google password or broad Gmail/Drive content. |
| Firebase / Cloud Firestore / App Check | Server account state, app attestation, security, quotas, deletion and one-way anti-abuse records. | Account identifiers, entitlement/quota/coin/live state, request status, app/device attestation and security metadata. |
| Google Play and Play Integrity | App distribution, purchase checkout, subscription management, transaction verification and integrity signals. | Store account and purchase/transaction data controlled by Google; integrity verdict and product status provided to Oraivex. |
| RevenueCat | Subscription entitlement and purchase-status synchronization. | Oraivex app-user identifier, product/entitlement, purchase and subscription status, transaction identifiers and related technical metadata—not body photos, wellness conversations or precise location. |
| LiveKit | Real-time audio, video and data transport for Coach and Mind Room. | Room/participant identifiers, live microphone/camera media when enabled, data messages, connection/device/network metadata and session observability if configured. |
| Google ML Kit | On-device pose detection for supported Coach rep/form features. | Camera frames processed locally by the device library for pose landmarks; separate live Coach media processing is described under LiveKit/Gemini. |
| MET Norway | Global weather forecasts for up to nine days. Weather attribution: Data from MET Norway under CC BY 4.0/NLOD 2.0. | Foreground coordinates rounded to four decimals and backend connection metadata. Typed place text is not sent to MET Norway. |
| OpenStreetMap Nominatim and Overpass operators | Typed Weather-place geocoding and user-requested live nearby-place search. | Nominatim may receive typed city/country Weather text. Overpass or Nominatim may receive current foreground coordinates, search words and normal connection metadata to return nearby supermarkets, pharmacies, gyms, cafés or similar places. Oraivex does not use these services to build map trails or saved-place history. |
| Google Maps | Optional external directions after the user selects a nearby result and taps directions. | The selected destination and normal connection/device information under Google Maps policies. Oraivex does not send the nearby result list to Gemini. |
| Android/Google system services | Permissions, notifications, speech recognition, activity recognition and device security capabilities. | Only the signals needed by the system service and granted feature. |
Provider policies and contracts can change. Current official information is available from Google Gemini API terms, Gemini abuse-monitoring policy, Firebase privacy information, RevenueCat privacy, LiveKit privacy, Hugging Face privacy, the MET Norway service terms, MET Norway licensing and crediting policy, the OpenStreetMap copyright and license page and the OpenStreetMap Foundation privacy policy.
5. Purposes, minimisation and legal bases
- Provide the requested service: authenticate, calculate local estimates, generate a requested result, run a live session, show requested weather and restore paid access.
- Adult-user consent: optional camera, microphone, photos, optional precise foreground location for Weather or live nearby search, activity, speech and submitted wellness content are used only after the adult user grants permission or affirmatively provides/activates the feature. Where applicable law treats health or wellness information as sensitive, Oraivex relies on the adult user's explicit, feature-specific choice and legal acceptance where consent is the appropriate basis.
- Legitimate security interests: protect accounts, trials, quotas, purchases, live minutes and systems against fraud, duplication, abuse and unsafe use.
- Legal obligations: preserve limited purchase, dispute, tax, security or compliance records where required.
Oraivex aims to send only the information listed for the selected feature. For Paid Intelligence and Life OS, the phone creates a feature-specific request and the server removes fields that are not allowed for that feature. Depending on the result requested, this may include a body-profile field, current score, sleep summary, plan detail, weather measurements, feedback, pattern summary or Lab memory. Dedicated allergy, medical-condition, injury, pain and movement-consideration fields are excluded. Account name, email, Google/Firebase identifier, full birth date, device location, GPS coordinates, readable location labels, nearby-place results, directions, map history, saved-place labels, Wi-Fi identifiers and place-based feeling history are excluded. Only derived weather measurements may be included. Detailed Lab memories are used only for Advanced Lab Memory. A location word deliberately typed by the user remains part of that user-authored request. Do not submit passwords, payment-card data, identity documents, confidential records, or another person's private information.
You may withdraw optional consent by stopping the feature, revoking Android permission, using the in-app AI data controls, clearing the relevant local category or deleting the account. Withdrawal prevents future personalized Paid Intelligence and Life OS requests until consent is granted again, does not disable local features, and does not invalidate processing already completed before withdrawal.
6. Android permissions and sensitive signals
- Camera: on-device Coach pose guidance, optional image analysis and live visual coaching only when opened/enabled.
- Microphone and speech: active Coach, Mind Room or speech-input features; background recording is not enabled.
- Photos: selected/captured content for optional Lab analysis.
- Activity recognition: steps, movement and supported visible foreground health processing.
- Precise foreground location: optional, used only for a requested current Weather result or live nearby-place search. Weather coordinates go through the Oraivex backend to MET Norway; typed Weather places may go to OpenStreetMap Nominatim; current coordinates and search words may go to OpenStreetMap Overpass or Nominatim for nearby supermarkets, pharmacies, gyms, cafés and similar places; and Google Maps receives a selected destination only when directions are opened. Background location is blocked. Only derived weather measurements—not GPS coordinates, location labels or nearby results—may be included in Gemini prompts.
- Notifications: user-selected reminders, plans, Flow, hydration, weather, birthday, safety and health-service status.
- Advertising ID: the current Android configuration blocks the Advertising ID permission.
Permissions can be denied or revoked in Android Settings. A related feature may stop or become less accurate.
7. Retention and deletion schedule
- Local content: remains until the user clears a category, permanently deletes the account, clears app data, uninstalls, changes device, or a documented local retention rule removes it.
- Pattern history: current exact-pattern and compact daily-intelligence memory may retain up to 365 days locally.
- Readable server account state: retained while the account is active and removed through the confirmed account-deletion flow, except narrowly retained records below.
- Weather and nearby requests: the backend uses rounded coordinates or typed Weather destination text only while obtaining the requested Weather result. Forecasts and Weather geocoding may remain in bounded in-memory caches to honor provider caching/rate-limit rules. Live nearby searches send current foreground coordinates and search words to OpenStreetMap services for that lookup. Oraivex does not write readable Weather-query or nearby-place history to Firestore.
- AI payloads and Google Gemini retention: Oraivex is not designed to keep readable Gemini prompts, selected image payloads, live audio or detailed generated responses in Firestore after the request finishes. Limited quota, request-status, timing, size, error and safety metadata may remain for service operation and protection. Google says Gemini API prompts, context and outputs may be kept for up to fifty-five (55) days for abuse monitoring, safety, security and required legal or regulatory disclosures. Oraivex does not promise zero provider retention.
- Live media: Oraivex does not intentionally keep a permanent raw-audio or raw-video archive. LiveKit/provider observability or security retention may apply if configured by the service.
- Deletion tombstone: the current server design uses a one-way account-deletion tombstone designed to expire after approximately 30 days to prevent race-condition restoration.
- Trial/anti-abuse locks: keyed one-way account/device eligibility markers may remain while needed to prevent repeated trials, quota bypass or fraud. They are not intended to contain readable profile, photo, prompt, feeling, plan or voice content.
- Billing/legal records: transaction, chargeback, tax, fraud or dispute records may remain for the period required by law, provider policy or a legitimate claim.
- Independent providers: Google, RevenueCat, LiveKit, Hugging Face, MET Norway, OpenStreetMap endpoint operators and other providers control their own security and legal retention.
8. International processing and transfers
Oraivex is operated from Lebanon and uses providers that may process data in the United States and other countries. Data is not guaranteed to remain in the user's country. Where a law requires transfer safeguards, Oraivex intends to rely on applicable provider data-processing terms, contractual transfer mechanisms or other lawful safeguards. Market availability may be limited while jurisdiction-specific compliance arrangements are reviewed.
Food and movement responsibility
Oraivex does not maintain an allergy or medical-condition profile and cannot certify that a food, restaurant item, meal plan, ingredient or scanned product is safe for you. You are responsible for checking official labels, ingredients, preparation methods and cross-contact and for asking the restaurant or manufacturer before eating or buying.
Oraivex also does not maintain an injury, pain or movement-consideration profile. You are responsible for deciding whether an exercise, movement, load, range of motion, pace or intensity is suitable for you, stopping if pain, dizziness or unusual symptoms appear, and obtaining qualified medical or fitness guidance when appropriate.
9. Your choices and privacy rights
Adult users can update local profile information, revoke permissions, clear Mind Room memory, photos, sleep/place histories and other local categories, or use Privacy Center → Permanently delete my account.
Depending on applicable law, you may request access, correction, deletion, restriction, objection, portability or withdrawal of consent. Email support@oraivexai.com from the Google account used for Oraivex. Reasonable verification may be required. Rights can be limited where security, fraud, billing, tax, legal or provider obligations require retention.
You may complain to the competent data-protection authority where that right applies.
AI-personalization consent can be withdrawn from the in-app AI data controls. Withdrawal prevents future Paid Intelligence and Life OS requests that send feature-specific wellness information until consent is granted again; it does not remove local histories or disable non-AI local functions.
10. Security
Controls include HTTPS encryption in transit, secure local token storage, Firebase App Check, Google Play Integrity, authenticated requests, server-side purchase verification, rate limits, one-way/HMAC anti-abuse markers, idempotency controls, minimized logs, no-store backend response headers and direct account deletion. No system is perfectly secure; compromised devices, malware, weak screen locks, provider incidents or user disclosure can expose information.
11. No sale, no in-app behavioral advertising and website measurement
Oraivex does not currently sell personal data or use body profile, plans, feelings, photos, voice, precise location or fitness history for third-party behavioral advertising. The Android build blocks Advertising ID permission.
The updated public website does not intentionally load Google Analytics or advertising-tracking scripts. The website host may still receive ordinary server connection data such as IP address, browser, requested page and security logs under the host's policy.
12. Changes and contact
Material changes to age eligibility, data categories, providers, permissions, background processing, AI, billing, retention or deletion may require a new in-app acceptance. Contact support@oraivexai.com.