Privacy Policy
This Privacy Policy explains how Arivano handles the information used by the current app build for style previews, community posting, profile controls, legal-page access, and preview credit purchases.
1. Information Stored on Your Device
Arivano keeps a set of on-device ledgers so the app can reopen your local session, remember likes and hidden profiles, keep preview credit balances, and restore the posts or profile details you save in the app. The current build also stores cached avatar images and published post images in local app storage when you choose those actions.
- Current-user session state and sign-in flags
- Seeded users, posts, and like records used by the app surface
- Hidden-profile and report-related local ledgers
- Preview consent preference, credit balance, and credit history
- Cached avatar images and cached post images stored on device
2. Camera and Photo Permissions
Arivano requests photo access when you choose a selfie, a profile photo, or images for a published style. Arivano requests camera access when you choose to capture a profile photo from the device camera. These permissions are used only after you trigger the related action.
3. Preview Requests and Third-Party AI Processing
When you start the preview flow, Arivano asks for explicit consent before sending the selected selfie image and selected reference image to the external preview endpoint api.gpt.ge. If you choose Not Now, the request does not proceed.
The current build prepares those images from local files, cached post images, or assets so the preview request can be processed. Arivano uses the returned result to show your preview inside the app and lets you save the result to your gallery if you choose.
4. Purchases and Preview Credits
Arivano uses the platform in-app purchase flow for preview credit packs. Purchase settlement is handled by the platform billing system, and Arivano receives the purchase state needed to update your local credit balance. Arivano does not present a separate card-entry form in the current build.
5. Community and Safety Actions
If you publish a style, like a post, hide another profile, or use a report action, Arivano stores the related local state needed to make that app behavior work. Community actions in the reviewed build are backed by app-side ledgers and profile/post records rather than a separate public moderation portal.
6. Microphone and Tracking Declarations
The iOS build also includes microphone permission text for optional support or account flows and tracking permission text for install quality measurement on supported builds. Those declarations do not create an always-on microphone or always-on tracking feature by themselves; permissions only matter if your build presents the related request and you choose to allow it.
7. Your Controls
You can review the legal pages from the login screen and from Settings. You can sign out, use the Delete Account action available in Settings, block or report another profile inside the app, decline preview consent, or save a preview result to your own gallery.
8. Support and Privacy Requests
Questions about this policy, preview credits, deletion help, or privacy requests can be sent to support@arivano.app.
Arivano publishes this page together with the public Terms & Conditions and Support pages for the same release.