Misturando Privacy Policy
This policy explains in detail how the Misturando app (package com.misturando.android on Android, distributed through Google Play, and identifier com.misturando.ios on iPhone, distributed through the App Store) handles your information, business records, and integration with Google services. It transparently describes how the app actually works. If this translation and the Portuguese version differ, the Portuguese version prevails.
Summary
- In the current version, your data stays on your device. Misturando is offline-first, does not require account registration, and maintains no server of its own to store your records.
- We do not receive your business records. Technical crash diagnostics are sent to Firebase Crashlytics (Google) only if you authorize it; sending is off by default. There are no advertisements or behavioral tracking.
- If you choose to turn on Google Drive backup, a compressed copy of your data is sent exclusively to the private application data folder in your own Google account. Neither the developer nor any third party has access to that copy.
1. Application Controller
Jonatas Augusto Sallazar Antunes
Contact & Support: jonatassallazar@gmail.com
2. Data Stored Locally on Your Device
To provide management and pricing features, the application stores locally, within an internal database and private application files protected by the device operating system (Android or iOS):
- Studio or business name and maker name, when voluntarily provided;
- Studio profile picture chosen from your device (the app stores a local copy, including the original image to allow non-destructive re-framing);
- Raw materials, ingredients, suppliers, purchase costs, units of measure, stock balances, movement history, and reasons entered for manual stock receipts and withdrawals;
- Ingredient photos chosen from your device, when you choose to add them (the app keeps the framed version and the original image in private app storage, to allow non-destructive re-framing);
- Normalized quantities and the preferred units used to enter measurements, to preserve precision and make editing easier. Read-only screens may show quantities in more compact units. This information remains local and is included in existing optional backups when enabled;
- Recipes, preparation batches, yields, scrap/waste rates, and product photos (including framed versions and the original photo retained in private app storage for re-framing adjustments);
- Reference links and titles saved within recipes and preparations;
- Preparation times measured by the in-app clock (active and wait time of each preparation and the time the running count started), used to show how long preparations really take and the average per recipe;
- Pricing parameters: hourly labor rate, overhead cost percentages, and target profit margins;
- Sales and orders: dates, items sold, total amount, sales channel, payment method, transaction fees, payment status, and buyer name (when entered);
- Custom payment methods configuration and app preferences (such as color theme).
Photo selection: profile, product and ingredient photos are chosen through the system's own photo picker (Android or iOS). The app receives only the image you choose, does not request access to your whole photo library or storage permission, and the photo is not sent off the device except inside the optional Google Drive backup.
These records stay on your device and are not sent for diagnostics. They leave the device only through optional Google Drive backups (when enabled by you) or when you open a saved reference link in your browser.
Atelier synchronization in development
We are developing optional atelier synchronization. It is not enabled in the app: Flutter does not send your records to the new API, and the service has not been made available in production.
The API in development can receive and store confirmed atelier states: pricing settings, categories, ingredients, suppliers and purchases, recipes, products and kits, preparations (including the times measured by the clock), leftovers, stock balances and history, sales and payment methods. These records may include buyer names, sales channels, notes and photo references when provided. Atelier, device, operation and version identifiers support access control, resumption, conflicts and retries without duplication.
The protocol keeps incomplete publications separate from active state and preserves previous generations when replacing an atelier. Business records, buyer and supplier values and credentials are excluded from this API's diagnostics. The artisan's personal name, device preferences, consent, tokens and operational backup state are not part of synchronized atelier records.
Photo file upload and storage and the protection and recovery mechanisms for this synchronization are not yet available. The API requires trusted evidence of files and protected state when applicable; a client-supplied indication does not authorize replacement. Enabling the feature in the app and in production depends on completing the account, device, synchronization, file and recovery flow and reviewing privacy information and Google Play Data safety. Access, retention and deletion rules for this new service will be provided before it becomes available. The optional Google Drive backup described below remains a separate feature.
Artisan name in your account
When the Misturando account is active and you sign in, the artisan name entered in your Profile will be sent to the Misturando API and stored linked to your account, so it can be restored if you reinstall the app or change devices. Edits made in the Profile update this name in the account. It belongs to you, not to the atelier: the atelier name, photo and other business data are not sent by this feature. The name is never copied from your Google profile. If the name on this device and the one in your account differ, the app asks which one to keep. The name stored in the account will be deleted together with the account. This feature is not active in production yet.
Devices connected to the atelier
When the Misturando account is active, you can connect this phone to your atelier in Profile → Devices. Nothing is sent until you confirm. When you confirm, the app sends the Misturando API a random identifier the app itself creates for this device and the device name you accepted or typed. By default, that name contains the phone's manufacturer and model (for example, “Samsung SM-S911B” or “iPhone 15”), read locally by the device_info_plus package, which makes no network connections and requests no permissions. The app does not read or send the name you gave the device in the system settings, the advertising ID, the serial number or any other hardware identifier.
The API stores the identifier and the name together with the dates of connection, last activity and disconnection, linked to the atelier. They are used to ensure that only connected devices send atelier data, to enforce the device limit and to show the list when you need to choose which device to disconnect. They are kept while the atelier exists and are deleted together with the account. On the device, the identifier and the connection state are kept out of backup copies; reinstalling the app or clearing its data creates a new identifier. Unlinking this phone in Profile → Devices disconnects the device from the atelier and replaces the local identifier; the data on the device stays on it. This feature is not yet enabled in production.
Account deletion
When the Misturando account is active, you can delete it at any time in the app (Profile → Account → Delete account) or by e-mail request, as described on Delete your Misturando account. Deletion immediately removes from our servers the account, the stored e-mail, the artisan name and all of your atelier's cloud data, including change history and deleted items; this data leaves our infrastructure backups within 30 days. The data on your device, the backups in your Google Drive and your Google account are not affected, and the app remains usable without an account. A Google Play subscription is not cancelled by deletion: cancel it in Google Play. E-mail requests are handled within 15 days. This feature is not yet enabled in production.
3. Google Integration and Handling of Google User Data
Misturando offers optional Google account sign-in and Google Drive backup and restore. Signing in does not enable backup. Drive access is requested only when you activate backup or when, on the app’s first opening, you choose to look for a backup to restore. Looking for a backup does not turn backup on: the app only lists and downloads the copies already in your Drive, and uploads or deletes nothing. You can use the app without an account.
3.1. Google User Data Accessed & Requested Scopes
- Basic Google Account Identification (Profile & Email): Used to identify the signed-in account and verify backup ownership. The app stores the stable account identifier on the device and displays a masked email. When Misturando's remote features are active, the device also stores the internal person and atelier identifiers returned by the API, used only to prevent the device's data from being linked to another account. This session data stays on the device and is excluded from backups. When the Misturando account is active, the API stores your Google account e-mail, only if Google reports it as verified, and updates it at each sign-in. It is used only to locate your account in a deletion request and is deleted with the account.
- Scope
https://www.googleapis.com/auth/drive.appdata(Google Drive Application Data Folder): Grants restricted permission to create, read, and delete files exclusively within the hidden folder dedicated to the app (appDataFolder) in your own Google Drive. Misturando cannot access your personal files, folders, photos, or documents on Google Drive.
Google Drive authorization is separate from Misturando account sign-in: enabling backup does not sign you in, and signing out does not disable backup. To verify the destination of automatic copies, the app retrieves the account identifier returned by Drive and stores it only on this device, outside backups. Temporary tokens obtained by the app are held in memory and are not included in business records or backups. Google manages account authentication on the device. If you authorized Drive to look for a backup, turning backup on later may reuse that same authorization, without a new Google screen, while it stays valid for the same account.
3.2. Purpose and Use of Google User Data
Information accessed through Google services is used to identify your account in the app and to:
- Storing backup archives (containing the app's database and associated photos, such as product, ingredient, and profile photos) within your private Google Drive space;
- Listing available backup copies and enabling data restoration when reinstalling the app or switching devices;
- Executing automated backup schedules (when enabled by you in the settings, respecting Wi-Fi preferences).
3.3. No Sharing and No Transfer of Google Data
Misturando maintains strict data protection principles:
- No third-party transfers: We do not sell or rent Google user data. The future Misturando API may receive a Google identity token to verify your account when remote features become available; it is not active in production yet.
- Direct connection: Backup communication takes place directly between your mobile device and Google's secure servers via encrypted protocols (HTTPS/TLS). The developer does not operate intermediate proxy servers through which your backup data travels.
3.4. Prohibition of Use for Advertising and AI Model Training
- Google user data is never used for serving ads, ad retargeting, or personalized marketing.
- Google user data is never used to train, fine-tune, or improve artificial intelligence (AI) or machine learning (ML/LLM) models.
Misturando's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
4. Other Google Services
In the version distributed through Google Play Store, the app utilizes Google Play's standard In-App Updates library to check whether newer application releases are available. This check is performed natively on-device by Google Play and does not transmit personal data to the developer.
iPhone (iOS): the iPhone version uses the same services described in this policy, under the same rules: Google Sign-In and the Google Drive API for the optional backup, and Firebase Crashlytics for diagnostics (sent only with your authorization, as described in section 11). The Google Play update service does not exist on iOS; updates arrive through the App Store.
5. What We Do Not Do
- We do not display advertisements.
- We do not utilize invasive analytics libraries, behavioral trackers, or ad networks.
- We do not collect or request permissions for GPS location, microphone, contacts, or camera.
- We never monetize user data under any circumstance.
6. Customer Records Entered by You
If you enter customer names, sales channels, or buyer details in sales records, that information is maintained under your direct control, stored only on your device and within your private Google Drive backup.
7. Data Retention, Deletion, and Revoking Access
- Deleting your Misturando account: When the account is active, delete it in the app (Profile → Account → Delete account) or by e-mail, as described on Delete your Misturando account. The account and your atelier's cloud data are deleted immediately and leave our infrastructure backups within 30 days. Device data and Drive backups are not affected; to delete them, use the options below.
- Connected devices: Unlink this phone in Profile → Devices. The atelier no longer accepts the device and the local identifier is replaced. The device record (identifier, name and dates) is kept while the atelier exists and is deleted together with the account.
- Device Deletion: You can delete recipes, ingredients, products, or sales records at any time within the app. When a profile, product, or ingredient photo is removed or replaced, or when a product or an ingredient is deleted, the corresponding local files (framed photo and original image) are permanently deleted from private device storage. To delete all local data at once, uninstall the app or clear app data via Android Settings (Settings → Apps → Misturando → Storage → Clear Data). On iPhone, delete the app (touch and hold the icon → Remove App → Delete App).
- In-App Backup Deletion: The app allows deleting manual backup copies individually within the backup management screen. The app maintains a rolling history of up to the 7 most recent automatic copies.
- Complete Deletion of All Backups in Google Drive: To permanently remove all backup files (including automatic copies), open Google Drive in a web browser, navigate to Settings (gear icon) → Manage Apps → Misturando → Options → Delete hidden app data.
- Revoking Google Access: You can disable backup or sign out in the app. To revoke Misturando's Google access, use your Google Account security permissions page: myaccount.google.com/permissions. Important: disabling backup or signing out does not revoke Google permission; neither action nor revoking access deletes previously saved backup files in Drive; to delete them, perform deletion via Google Drive as described above.
We cannot access your device records or private Drive backups. The options above put their management and deletion in your hands.
8. Your Privacy Rights
Under applicable data privacy regulations (such as Brazil's LGPD, EU GDPR, and others), you can manage app records in the app, backups in your Google Account, and diagnostic authorization in Profile settings. For inquiries, contact jonatassallazar@gmail.com.
9. Children's Privacy
Misturando is a business management and costing tool designed for artisans and makers, and is not directed at children.
10. Changes to This Privacy Policy
If our data practices or feature integrations change, this policy will be updated with a revised effective date at the top. We encourage you to review this page periodically.
11. Optional technical diagnostics
In a separate Android development-only tool, the tester can trigger a crash and manually authorize sending pending reports to Firebase/Google. This tool does not open the business database and should be used on a dedicated test device or emulator. Reports may include the crash stack, app version, technical device characteristics, and technical installation identifiers generated by the SDK. In this tool, automatic collection remains disabled. It is not available in the production version.
Misturando keeps sanitized technical records on your device for up to 7 days, limited to 20 events and 256 KiB. They may contain an error category and stage, support code, app and schema versions, a duration bucket, timestamp, up to eight references to internal app files and, for local database failures, the technical error family, SQLite numeric error codes and the schema version stored on the device. Raw error messages, recipes, sales, customer records, photos, database files, local paths, SQL, credentials, and attachments are excluded from these events.
Remote reporting is off by default, including before the app starts. If you authorize it in Profile or on the recovery screen, the app sends Firebase Crashlytics (Google) the sanitized technical events described above and the app's crash reports. Beyond what the app sends, the Crashlytics SDK adds to each report the crash stack, the app and operating system versions, the device model and technical characteristics (such as free memory and storage, screen orientation and whether the device is rooted) and a technical installation identifier generated by the SDK. For crashes in the app's native code, the report also includes the error message produced by the system or by the failing library; Misturando does not put business data in those messages. We do not send your name, email, Google account identifier or business records, and the app does not use Firebase Analytics. Reports travel over an encrypted connection and are used only to find and fix crashes. Reports are kept on the device and sent the next time the app opens, after it confirms your authorization. Reports recorded before your authorization are discarded, not sent. Firebase availability does not affect local use or data recovery.
You can revoke authorization in the same screens. From then on no report is sent: the app stops recording its events and discards reports not yet sent, including those of crashes that close the app after the revocation. Revoking does not delete reports Firebase has already received, which follow Crashlytics retention; to request deletion sooner, use the contact email in this policy. Any individual report sharing, if made available, will require an explicit action from you after review.