Skip to content
BilletIA
ESENPT-BR
Back to BilletIA

Privacy Policy

Last updated: October 12, 2026

Your financial records are stored on your device. Advertising, purchases, updates, exchange-rate requests, and remote AI have data practices explained here.

On this page
  1. 1. Controller and scope
  2. 2. Data stored on your device
  3. 3. Camera, photos, and notifications
  4. 4. System AI and local components
  5. 5. Remote AI you choose
  6. 6. Advertising and consent
  7. 7. Purchases and PRO access
  8. 8. Exchange rates and updates
  9. 9. Website and contact
  10. 10. Purposes and retention
  11. 11. Exports, backups, and deletion
  12. 12. Security and international processing
  13. 13. Your rights
  14. 14. Minors and policy changes
Terms of use

1. Controller and scope

Effective and last updated: 2026-10-12. RENERPDEV SAS is responsible for BilletIA and this website. Its address is Vehicular 1 1430, Pando, Canelones, Uruguay. This policy explains data handling in the app, on the website, and when you contact us.

You can contact the controller with privacy questions or requests.

  • hello@renerp.dev
  • RENERPDEV website

2. Data stored on your device

BilletIA uses a local database and does not require a server account. It stores income, expenses, categories, budgets, recurring records, savings funds, balances, currencies, exchange rates, receipts, conversations, and AI results. Images and attachments are stored as local files. Your profile name and photo are optional; preferences are also local.

RENERPDEV SAS does not automatically receive these records or provide its own financial synchronization service. A remote feature you enable may send the necessary context to the service you select, as explained below. Operating-system backups depend on your device settings and terms.

3. Camera, photos, and notifications

The camera captures receipts, financial images, and QR codes. Photo-library access lets you select an image or profile photo. Image text recognition runs on your device. Notifications are scheduled locally for reminders and financial alerts; they may display information on your lock screen.

You can decline or revoke these permissions in system settings. This limits the corresponding feature while keeping manual financial entry available. Capturing images does not require audio recording.

4. System AI and local components

The default option is the system model, when supported by your device, language, and available model. The app uses Apple Foundation Models on iOS and Gemini Nano through ML Kit and AICore on Android. This mode processes inference content on your device and does not automatically activate a remote provider if unavailable.

Google states that ML Kit may connect to update models or components and send technical usage and performance metrics. According to its documentation, it does not send the images, input text, or results of that local processing to Google. System components are also subject to Apple or Google terms.

  • ML Kit privacy

5. Remote AI you choose

You can supply your own API key and explicitly activate OpenAI, Anthropic, or Google Gemini. Requests are sent directly to the provider over HTTPS. They may contain your message, parts of your conversation, recognized receipt text, and financial context or local query results needed for the task. This integration sends text; the image file is not part of the remote-model request.

Keys are kept in secure device storage and are not included in financial backups or exports. You can return to the system model or delete keys in AI settings. Stopping use of a provider does not delete requests it has already received: retention and use depend on its terms and your account with it.

  • OpenAI API data
  • Anthropic API data
  • Gemini API terms

6. Advertising and consent

When advertising is enabled, BilletIA uses Google AdMob and requests non-personalized ads. It does not add your amounts, categories, profile, or conversations to those requests. The app checks consent options through Google UMP before requesting ads and offers privacy options in Settings when the service requires them.

Non-personalized ads may still involve technical data: an IP address and its inferred approximate location, device identifiers, ad interactions, and diagnostic data. Google may use identifiers or storage for frequency capping, ad measurement, and fraud prevention. Available choices depend on your region and device settings. PRO prevents new ad requests and presentations; it does not delete data Google has already received.

  • How Google uses data from partner apps
  • Non-personalized ads

7. Purchases and PRO access

The RevenueCat integration checks PRO access, validates purchases, and presents store offers. It uses a random installation identifier without a BilletIA account. It may process purchase and subscription information, store receipts or tokens, last activity, and technical device data. An anonymous identifier does not mean that no data is processed.

We do not send your transactions, financial receipts, balances, name, photo, or conversations to RevenueCat as customer attributes. Apple or Google handles payment according to your store. Purchase identity and caches are separate from your financial workspaces. For requests about data RevenueCat processes on behalf of BilletIA, contact hello@renerp.dev.

  • Data processed by RevenueCat

8. Exchange rates and updates

Exchange-rate mode is manual by default. If you enable automatic updates or request a refresh, the app queries Frankfurter using public currency codes, without amounts, transactions, or a financial identifier. The provider receives the request and technical connection data, including your IP address.

  • Frankfurter

Versions with updates enabled may query Expo EAS Update and download app files. These communications include necessary technical data such as platform, compatible version, and update channel, as well as connection data. They do not back up or synchronize your finances.

  • Expo updates

9. Website and contact

The website is hosted on Vercel. When you visit it, its infrastructure receives your IP address, the requested URL, browser information, and the date and time; it may derive an approximate location from the IP address. This technical data helps deliver content, operate the service, and protect it. We do not add analytics trackers, advertising pixels, or marketing cookies.

  • Vercel privacy information
  • Data processing at Vercel

If you write to us, we receive your email address, message, and any attachments you choose to send. We use them to respond and handle your request. Do not send API keys or unnecessary financial data. External links lead to services with their own privacy practices.

10. Purposes and retention

Processing necessary for features you request is connected to providing the service. We use consent for optional features where applicable, legal obligations for retention required by law, and, where permitted, legitimate interests for proportionate website security and operation. Declining a permission or not activating a provider limits that feature without automatically enabling another.

Financial data remains local while you keep your workspace. Some individual deletions retain local references to prevent duplicate recurring records or preserve savings history. Complete deletion lets you remove that data. Support messages and technical logs are kept for the time necessary for their purpose and applicable obligations. External services apply their own retention terms; we do not claim local deletion erases their data.

11. Exports, backups, and deletion

You can export CSV reports, JSON data, and .billetia files using app options. A complete backup may contain images and conversations. If you share it or save it with another service, that copy is under your control and the destination’s terms. Protect these files; your AI keys are not included.

Deleting financial data and deleting the local account have different scopes. Financial deletion keeps your profile and settings; local-account deletion also removes preferences, photos, managed files, and AI keys, and creates a new workspace. Neither action removes previously exported files, data sent to providers, or external purchase records, or cancels an Apple or Google subscription. We cannot recover from a server data that existed only on your device.

12. Security and international processing

Local files rely on your device protections and settings. Provider keys use secure device storage, and the remote connections described here use HTTPS. We do not promise additional encryption for the entire database or every exported file. Keep your device and operating system updated and control who can access them.

Google, RevenueCat, Expo, and AI providers may process data outside Uruguay or your country. The service and your configuration determine recipients, locations, and processing terms. Transfers must use mechanisms required by applicable law; HTTPS protects communication but does not replace those requirements. You can request information about recipients and safeguards at hello@renerp.dev.

13. Your rights

Depending on applicable law, you can request information, access, correction, deletion, portability, objection to or restriction of processing, and withdraw consent. Withdrawal does not affect the lawfulness of earlier processing. For local data, the app provides editing, export, and deletion; we do not need to receive your finances for you to use these options.

For data RENERPDEV SAS processes or instructs a service to process, write to hello@renerp.dev. We may request minimal information to verify your request. If we do not have the data or another controller is responsible, we will tell you. In Uruguay, Law 18.331 recognizes data-protection rights, and you can contact or complain to the URCDP. Where applicable, European GDPR or Brazilian LGPD rights and the ability to contact the competent authority also apply.

  • Uruguay URCDP
  • Brazil ANPD

14. Minors and policy changes

BilletIA is not specifically directed at children. Use by minors and any purchases require a legal representative’s involvement or authorization where required by law. If you believe we improperly received a minor’s data, contact us so we can review it.

We will publish policy updates with their date. If a practice changes in a way that requires prior notice or renewed consent, we will communicate it and request consent where applicable. This policy does not replace the app’s permissions or consent choices.

Contact

RENERPDEV SAS
Vehicular 1 1430, Pando, Canelones, Uruguay
hello@renerp.dev
renerp.dev

You can save or print this page from your browser.

BilletIA
PrivacyTerms of useContact
© 2026 BilletIA · RENERPDEV SASDeveloped by RENERPDEV