Who we are and our roles
Last updated: 1 November 2026. App: TradeFlow for Android (com.cdrapps.tradeflow).
TradeFlow is published by CDR Apps di Rusu Cosmin Dumitru (Italy; VAT no. 18569901004; REA RM-1793518; see the business details). Privacy contact: [email protected]. We have not appointed a Data Protection Officer.
- We are the controller of the data needed to run accounts, usage limits, Premium access, security, support and deletion requests (sections below).
- We act as processor on your behalf when you choose to send job details or a recording to the AI features. If you use TradeFlow for your trade or profession, you are the controller of your clients’ data; see Data processing terms.
- Data that stays only on your phone is not received by us; we do not process it.
What stays on your device
TradeFlow works offline and stores the following in the app’s private storage on your phone. We do not receive it unless a section below says so.
- Jobs: titles, client names, addresses, dates, status, notes and materials.
- Photos you attach to jobs and client signatures.
- Voice recordings you make for a job, and transcripts or reports you generate.
- Invoice drafts, your business details used as invoice issuer, and generated invoice PDFs.
- Your acceptance of the Terms of Use (and, if you use TradeFlow professionally, of the Data Processing Terms) and your acknowledgement of the AI data-flow notice: the document versions, the time, the app language, whether you chose professional or personal use, and your account ID if you are signed in. This record is kept on your phone only; we do not receive it.
- App preferences such as language.
- The Free-job ledger: a single device-wide count of the jobs ever created on this phone, with no job content. It is used to enforce the limit on job creations in the Free tier and to stop that limit being avoided by deleting jobs, deleting the account or creating a new one. It is not tied to your account, and neither deleting jobs nor deleting your account resets it. An Android backup restore can bring back a saved copy of it (see Android backup), so we do not promise that uninstalling the app or clearing its storage resets it.
- A temporary deletion record. When you start deleting your account, the app first writes your pseudonymous account ID and a status (for example request sent, retry needed, outcome unknown, or signed out with cloud cleanup unconfirmed) on your phone. It holds no email address, password or sign-in token, stays on your phone only and is not part of the Android backup. The app removes it when it is told that the deletion finished. If the outcome could not be confirmed, it stays, and while it exists the app prevents Premium checks from recreating your RevenueCat customer record. A record for a sign-in that is already gone stays until you dismiss the notice in the app, clear the app’s storage or uninstall it.
TradeFlow V1 keeps one local workspace per installation. It does not support switching between accounts and has no ordinary Sign Out: the jobs on a phone belong to that installation, whichever sign-in it uses. If you share an invoice or file by email or a messaging app, it goes to the recipient and the app you choose, under their terms.
Your responsibilities toward your clients
If you enter other people’s data (for example your clients’ names, addresses, voices, photos or signatures) you are responsible for doing so lawfully. If you use TradeFlow purely for personal or household purposes, data protection law may not apply to your own use of such data, but the points below are still good practice. If you use it in your trade or profession, in particular:
- Have a legal basis for what you record and send (usually performing a contract with the client or your legitimate interest) and tell your clients how you use their data, including that you may use online transcription and AI services.
- Record voice only where you are entitled to, and tell the people being recorded. Do not send recordings or notes containing health, children’s or other sensitive data unless you really need to.
- Send only what you need. Review AI output before you rely on it or give it to anyone.
- Requests from your clients to access, correct or delete their data are yours to handle; we help as described in the Data processing terms.
Account and sign-in (Firebase Authentication)
- Data: a random user ID; for email accounts your email address and a password credential managed by Firebase (we never see your password); sign-in provider and timestamps. Google also logs technical data such as IP address and user agent.
- Purpose and legal basis: to give you an account and online features you request (performance of a contract, Art. 6(1)(b) GDPR). When you use an online feature without an email, TradeFlow creates an anonymous account with a random ID. That ID is still personal data because it can be linked to your device’s activity.
- Recipient: Google (Firebase Authentication).
- Kept: until the account is deleted. Google states that it keeps logged IP addresses for a few weeks and removes a deleted user’s authentication data from live and backup systems within 180 days.
- Providing it: optional for local use; needed for online features and Premium.
Security checks (App Check)
- What: online requests are designed to be protected with Firebase App Check using Google Play Integrity, which sends attestation data about your device and the app to Google to confirm the request comes from a genuine copy of TradeFlow installed from Google Play.
- Legal basis: our legitimate interest in security and preventing abuse (Art. 6(1)(f); Art. 32 GDPR).
- Kept: Google’s documentation states that App Check does not retain attestation material and that tokens last at most 7 days.
Usage allowance records
- Data: a counter per user ID per day for transcription and for AI reports, and project-wide daily counters. They contain no job content.
- Purpose and legal basis: fair-use limits and cost control for the AI features (legitimate interests, Art. 6(1)(f)). Because they hold only counters, the impact on you is minimal.
- Recipient: Google (Firestore).
- Kept: each daily counter, per-user and project-wide, is given an expiry timestamp set at the end of its UTC usage day plus 30 days. Firestore’s time-to-live (TTL) feature then deletes eligible records automatically, but asynchronously: we do not guarantee deletion at an exact time or within a fixed interval, so a record may remain for some time after its expiry. Per-user records are also removed when your account is successfully deleted. Project-wide counters contain no personal data. This expiry applies only to these counters, not to your jobs, invoices, photos, signatures or any other data.
Optional voice transcription
- Data: the recording you select (m4a, up to 8 MB) and a language hint. Recordings can contain spoken personal data of your clients or other people.
- How: the app uploads it to our Firebase Cloud Function in Milan (europe-west8), which forwards the audio to OpenAI and returns the text to your phone. The function does not save the audio or the transcript in our database, and our logs record event names only.
- Purpose and legal basis: to transcribe because you asked (performance of a contract, Art. 6(1)(b)). For your clients’ data we act as your processor.
- Recipients: Google (hosting the function), OpenAI.
- Kept: by us, not stored. OpenAI’s documentation (checked 30 October 2026; it may change) states that API data is not used for training by default and lists no abuse-monitoring retention for the transcription endpoint. That is not a statement that OpenAI keeps nothing, and we cannot verify retention for our account.
- Providing it: optional. Do not use it for recordings you are not entitled to process.
Optional AI job reports
- Data sent: the language, job title, client name and address, date, status, summary, materials list and the transcript or notes text (up to 20,000 characters). Photos and signatures are not sent. Free-text notes can contain any personal data you type; enter only what you need.
- Output: a report (summary, work performed, materials, follow-up) comes back to your phone. It is generated by an AI model and may be wrong; you review it. It is not a decision about you or your client.
- Purpose and legal basis: to generate the report you request (Art. 6(1)(b)); for your clients’ data we act as your processor.
- Recipients: Google (hosting), OpenAI.
- Kept: by us, not stored. OpenAI’s documentation (checked 30 October 2026) states that API data is not used for training by default and that requests to its chat completions endpoint are subject to default abuse-monitoring retention of up to 30 days, longer where the law requires; it also describes short-term prompt caching. We cannot verify or change retention at OpenAI.
Premium subscriptions
- Data: purchase and subscription status. Your RevenueCat customer ID is your TradeFlow user ID. RevenueCat also receives the technical data its SDK collects. TradeFlow does not send your email address or name to RevenueCat.
- Purpose and legal basis: to sell and unlock Premium (Art. 6(1)(b)); to keep accounting and tax records (legal obligation, Art. 6(1)(c)).
- Recipients: Google Play processes the payment under its own terms (we do not receive card details). RevenueCat acts as our processor; its data processing addendum incorporates the EU Standard Contractual Clauses.
- Kept: at RevenueCat until your customer record is deleted (see Account deletion); accounting records for the period required by Italian accounting and tax law.
Support and deletion requests
- Data: your email address, the content of your message, and any confirmation code exchanged. Mail sent to [email protected] is forwarded by Cloudflare Email Routing to the owner’s Yahoo inbox, and our replies are sent from that mailbox.
- Purpose and legal basis: to answer you and handle your rights requests (legal obligation, Arts. 12 and 15–22 GDPR; and our legitimate interest in proving how we handled a request).
- Recipients: Cloudflare and Yahoo as email providers.
- Kept: while your request is open, and afterwards only as long as needed to show how we handled it and to deal with any complaint or claim about it. We do not use these emails for other purposes.
Deletion record and technical logs
- Deletion record: when an account is deleted, our server writes a completion marker that holds the former user ID (a pseudonymous identifier once the sign-in is gone), a status, the RevenueCat deletion progress, an attempt count and timestamps. It holds no email address and no job content. We keep it so the deletion can be completed and shown to have been done (legal obligation and legitimate interest, Arts. 6(1)(c) and (f)). This record is separate from the usage allowance records described above and is not deleted automatically. Once a deletion is fully completed and RevenueCat has confirmed that no customer record remains, the marker becomes eligible for manual removal by us only after at least 30 days have passed since completion, and subject to our safety checks. A marker for a deletion that is incomplete, or whose billing status is still unresolved, may be kept longer. We do not promise removal on any particular date.
- Logs: our cloud functions log event names such as “request failed” without request content (legitimate interest in security and reliability). Google Cloud and Firebase keep their own operational logs, for example IP addresses; Google states that Cloud Functions saves IP addresses only temporarily. In our project, the default log bucket (application logs, such as the event names above) is set to keep logs for 30 days, and the required log bucket (required audit logs of administrative actions) for 400 days; that setting is locked. Not every log necessarily contains personal data, and other Google or provider logs follow their own retention periods.
Android backup
If you have Android backup turned on, your phone may back up the TradeFlow jobs database to your Google account and may copy it to a new phone when you set one up. That database holds each job’s stored record (for example client name and address, dates, status, notes, materials, transcripts, AI reports and invoice data, and the file paths of attachments), the free-job counter and a list of attachment files waiting to be cleaned up. It can therefore contain personal data about your clients. It does not include the photo, signature and voice-recording files themselves, your preferences, your invoice issuer profile, or your sign-in and subscription details. A restore brings jobs back without their attachments; it is not a complete backup.
We do not receive this backup, and we cannot verify what Google keeps or for how long. You control it in your Android and Google account settings. After a restore the app starts signed out; use Restore purchases to re-check Premium. A restored free-job counter may be older than your current one. Keep a separate copy of photos, signatures and recordings you need.
Who receives data, and transfers outside the EEA
- Google (Firebase Authentication, Cloud Functions in Milan, Firestore, App Check, Google Play): processor for us, except Google Play payments which Google handles itself. Our agreement with Google incorporates the Firebase Data Processing and Security Terms, under which Google acts as processor. For transfers outside the EEA those terms rely on the EU-U.S. Data Privacy Framework for certified Google entities in the US and otherwise on Standard Contractual Clauses. Our Firestore database is located in Milan (europe-west8); that does not mean every Google processing operation is limited to Italy or the EU.
- OpenAI: transcription and AI reports, only when you use them. OpenAI is a United States company and its processing for us may take place outside the EEA. We make no statement about its processing locations. OpenAI’s published Data Processing Addendum is incorporated into its Services Agreement and describes Standard Contractual Clauses and adequacy-based transfer mechanisms where relevant.
- RevenueCat (United States): Premium entitlements; its data processing addendum, which its terms incorporate by reference, includes Standard Contractual Clauses.
- Cloudflare and Yahoo: support email.
We do not sell personal data, TradeFlow contains no advertising SDK, and we do not make decisions about you based solely on automated processing.
Your rights and complaints
Under the GDPR you have the right to access your data and receive a copy, have it corrected or erased, restrict or object to its use (including processing based on legitimate interests), receive data you provided in a portable format, and withdraw any consent. Write to [email protected] (forwarded to our inbox; replies may come from a different address). We may need to verify your identity first and we never ask for your password. We respond without undue delay and at the latest within one month; where requests are complex or numerous we may extend this by up to two further months and will tell you. That is a duty to respond; it is not a promise that every provider will have erased data within that time.
You can complain to the Italian data protection authority, the Garante per la protezione dei dati personali (garanteprivacy.it), or to the authority where you live or work.
Deleting your account
Account deletion is designed to remove your cloud identity (your Firebase sign-in), your usage-allowance records and your customer record at RevenueCat. The RevenueCat deletion is requested and completes asynchronously. It does not automatically erase the local job records, photos, signatures, recordings or invoices on your phone, does not cancel a Google Play subscription, and does not delete a Google backup or data already sent to OpenAI. We do not promise complete erasure of every copy held by providers. Deletion by email is available for email accounts; anonymous accounts can be deleted only in the app. See Account Deletion.
Children, security, changes
TradeFlow is intended for adults and is not directed at children. Data sent to our servers and providers travels over HTTPS. Local data is kept in the app’s private storage; we do not claim additional encryption of it. We will update this page and its date when our practices change. This policy is available in English and Italian; if they differ, tell us. TradeFlow’s screens are available in English, Italian, Romanian, Spanish, German and French.