legal / counting / privacy
Privacy Policy of OPW Counting
- Version
- Effective date
- Last updated
- Responsible
- 1.5.2
- August 2, 2026
- November 18, 2026
- OPW DESARROLLOS DE USA, LLC
Privacy Policy
Application: Counting (the "App" or the "Service")
Data controller: OPW DESARROLLOS DE USA, LLC, a Florida Limited Liability Company (hereinafter "Counting", "we", "us" or "our")
Address: 2187 SW 1st St, Suite 1029, Miami, FL 33155
Florida registered agent: 2187 SW 1st St, Suite 1029, Miami, FL 33155
Data Protection Officer: [email protected]
Website: https://opwapps.com/en/legal/counting/privacy
Effective date: August 2, 2026
Last updated: November 18, 2026
Version: 1.5.2
This is an English translation of the Spanish original, available at https://opwapps.com/legal/counting/privacy. If the two versions differ, the Spanish version prevails, unless applicable law requires otherwise.
1. Introduction
1.1. Who we are. Counting is a personal finance organization mobile app operated by OPW DESARROLLOS DE USA, LLC, a Limited Liability Company organized under the laws of the State of Florida, United States.
1.2. What this policy covers. This Privacy Policy describes how we collect, use, share, retain and protect the personal data of users of the Service, and the rights you have in the United States, Mexico, Panama and other jurisdictions where we offer the Service.
1.3. Our commitment. We are radically transparent with you about your data: we never sell your personal data, we tell you which kinds of providers receive information and why, and we clearly explain what we use each category of data for.
1.4. Scope. This policy applies to the use of the Counting mobile app (iOS and Android) and to the website https://opwapps.com/legal/counting/privacy. It does not apply to third-party sites or services linked from our Service.
2. Data we collect
2.1. Identification and profile data
- Email address
- First and last name (optional in some flows)
- Country of residence and preferred currency
- Profile photo (optional)
- Preferred language and time zone
2.2. Authentication data
- Password (stored using a one-way hash with a strong algorithm; we never store passwords in plain text)
- Apple Sign-In and Google Sign-In authentication tokens (when the User chooses these options)
- Session tokens and refresh tokens
- Email verification codes (temporary)
- Confirmation of legal age (18+ age gate, with timestamp)
2.3. Financial data entered manually by the User
All financial information in Counting is entered manually by the User. Counting does not connect to banks, credit unions, payment processors or financial institutions to read statements or transactions automatically.
- Accounts: name, type (cash, bank, digital, savings), opening balance, currency
- Cards:
- Type (debit, credit)
- Name assigned by the User and last four digits (never the full PAN)
- Card brand (Visa, Mastercard, etc.)
- For credit cards, optionally: interest rate, annual fee, limit, statement and payment dates, all entered manually by the User
- Transactions: amount, date, category, merchant, notes, associated account/card, currency
- Budgets and goals: categories, amounts, periods, progress
- Custom categories and tags
Counting does not process payments, does not move funds, does not access real bank accounts and is not a financial institution. All data is a personal record kept by the User.
2.4. Data derived from scanning receipts and invoices
- Tax QR codes (CFDI Mexico, SFEP Panama): public metadata of the receipt (folio/UUID, issuer RUC/RFC, amount, date) used to fill in a transaction.
- Receipts scanned with on-device OCR or AI: amount, date, merchant and suggested category, extracted from the receipt image.
- Receipt images:
- Free plan: we do not store the images. With on-device OCR the image never leaves the device. With AI OCR, the image is uploaded encrypted to our cloud storage only so the AI provider can read it, and it is deleted as soon as extraction finishes.
- Plus, Pro and Business plans: the receipt image is kept with the transaction the User creates from it, so the User can view it again. It is compressed (JPEG, ~1600 px, typically ~250 KB) and stored encrypted in our cloud storage. If the User does not save the transaction, the image is deleted within 24 hours.
- The data from the tax QR code that was read (invoice number, issuer, RUC/RFC, amounts) is also saved with the transaction.
- The image is deleted when the User deletes the transaction or their account. Images already saved remain available if the User switches to Free.
2.5. Data sent to AI OCR providers
When the User turns on AI OCR:
- The receipt image is sent, through its paid API, to an artificial intelligence provider hired by the Company (Section 5.2).
- The provider processes the image and returns structured text. The provider does not use data sent through the API to train its models, under their commercial terms.
- On the Free plan the image is deleted from our storage as soon as the response arrives, except for the copy described in section 2.5.1. On the Plus, Pro and Business plans it is kept with the transaction, as described in section 2.4; the AI provider does not keep it.
2.5.1. Improving receipt reading
To help the App read receipts better, we keep a copy of every receipt you scan: the image, the text that was read and the data you confirmed when saving the transaction (amount, merchant, date). The copy is kept separate from your transactions, in every scan mode and on every plan, including Free.
- What it is used for: reviewing why a reading went wrong, measuring and correcting the App's reading rules and instructions, and developing and tuning OPW's own receipt-reading models. It is not used for any other purpose, it is not sold and it is not shared with third parties; only the OPW team sees it. The AI providers (section 5.2) do not receive it to train their models.
- How long: each copy is deleted automatically twenty-four (24) months after it was scanned.
- How to turn it off: in the App, Profile › Privacy › "Help improve reading". It is on by default. Turning it off immediately deletes all copies of your receipts kept for this purpose and stops new ones from being kept. The deletion is permanent: the copies cannot be recovered. You can turn it back on at any time for receipts you scan afterwards. Turning it off does not affect your transactions or the receipt images of paid plans (section 7.3).
2.6. Voice notes ("By voice")
When the User records a transaction by voice:
- The audio (60 seconds maximum) is sent to an artificial intelligence provider (Section 5.2) to be transcribed and interpreted, to propose the transaction.
- We do not keep the audio. Only the usage (date, duration and cost) is recorded, to control the AI quota.
- The proposed transaction is not saved until the User confirms it.
2.6. Device and technical data
- Operating system and version (iOS/Android)
- Device model
- App version
- Unique installation identifier (not linkable to hardware)
- Device language and time zone
- IP address (logged temporarily for security and fraud prevention)
- Network type (Wi-Fi/cellular, no specific carrier)
2.7. Usage and analytics data
- Anonymized in-app events: screens visited, features used, aggregated usage times
- Technical errors and crashes (crash reports, including stack traces without PII)
- App performance metrics
We use anonymized analytics to understand how the App is used and to improve it. Events do not include the User's financial content, amounts, merchant names or custom categories.
2.8. Push notifications
- Device tokens issued by the Apple and Google notification services to deliver notifications.
- Notification preferences set by the User.
2.9. Support communications
- Messages, emails and support tickets the User sends to our support team, along with any attachments the User chooses to share.
2.10. Purchase data (IAP)
- Anonymized subscription identifier issued by the Apple App Store or Google Play Store.
- Subscription status (active plan, period, renewal date).
- We do not receive, store or have access to the User's credit card, bank account or payment credential data. All payment financial information is handled exclusively by Apple and Google.
2.11. Data we do NOT collect
- Full card numbers (PAN), CVV/CVC or expiration dates of real cards.
- Online banking credentials.
- Bank statements.
- Precise GPS location (unless the User explicitly authorizes it for future features that require it).
- Contacts, calendars, or full photo libraries (beyond the specific image the User scans).
- Biometric data (Face ID / Touch ID never leave the device; they are processed locally by iOS/Android).
- Special categories of personal data (racial origin, religion, sexual orientation, health, political opinions, union membership).
3. How we use your data
We use your data exclusively to:
3.1. Provide the Service: create and manage your account, let you record transactions, calculate balances, generate reports, sync across devices (Pro), and process scanned receipts.
3.2. Process your subscription: validate your plan status with Apple/Google and enable the corresponding features.
3.3. Improve the Service: aggregated and anonymous analysis, bug fixing, performance optimization and development of new features.
3.4. Communicate with you:
- Transactional (always): account confirmations, password recovery, security notices, material changes to these Terms or Policy, purchase receipts.
- Marketing (only with explicit opt-in): news, financial tips, promotions. You can unsubscribe at any time.
3.5. Comply with legal obligations: respond to valid requests from competent authorities and keep tax records where applicable.
3.6. Prevent fraud and abuse: detect duplicate accounts, automated use, attacks on the infrastructure and violations of the Terms.
3.7. Personalize your experience: remember preferences (currency, language, default categories, filters).
3.8. Anonymous analytics: understand which features are used most, where there is friction and how to optimize the experience.
We do not use your data to:
- Sell it to data brokers.
- Build credit scoring profiles.
- Target advertising based on your financial content.
- Train third-party AI models with your content (our AI providers operate under no-retention clauses). The only exception is improving receipt reading with OPW's own models, described in section 2.5.1, which you can turn off.
4. Legal basis for processing
The legal basis varies by jurisdiction:
4.1. United States
- Performance of a contract: to provide the Service under the accepted Terms.
- Consent: for marketing, non-essential analytics and optional features (AI OCR, attaching images).
- Legitimate interest: for security, fraud prevention and product improvement.
- Legal compliance: to meet tax and regulatory obligations and court orders.
4.2. Mexico (LFPDPPP)
- Tacit consent for the primary purposes described in the Privacy Notice, given by acceptance at sign-up.
- Express consent for secondary purposes (marketing) and for the international transfer of personal data to third parties located outside Mexico (providers in the USA).
- Compliance with a legal obligation where applicable.
4.3. Panama (Law 81 of 2019)
- Prior, express and informed consent of the data subject for the processing of personal data.
- Performance of a contract.
- Compliance with a legal obligation.
- Legitimate interest, duly balanced.
4.4. Users in other countries
If you live outside the United States, Mexico and Panama, the processing of your data is governed by this Policy and by the laws of the State of Florida and applicable United States federal law, as set out in the Terms and Conditions (section 17.1). This does not limit any non-waivable rights granted to you by the law of your country of residence, which you can exercise by writing to [email protected].
5. Who we share data with
5.1. General principle
We never sell, rent or trade your personal data. We do not engage in targeted behavioral advertising based on your financial information.
5.2. Providers that help us run the Service
We share data only with these kinds of providers, to the minimum extent needed to operate the Service:
| Kind of provider | Purpose | Data |
|---|---|---|
| Infrastructure and hosting | Servers, database and storage where the Service runs | Service data, encrypted in transit and at rest |
| Security and network | Protection against attacks and traffic delivery; storage of receipt images | Encrypted Service traffic; receipt images the User uploads |
| Artificial intelligence | Reading receipts and voice notes, only when the User uses those features | Receipt image, audio and text of the voice note. Deleted after processing and not used to train models |
| Sign-in | Signing in with Apple or Google | Email and identifier of the sign-in account |
| App stores and subscriptions | Billing on the App Store or Google Play and subscription validation | Internal User identifier, purchase history and subscription status |
| Notifications | Push notifications and App updates | Device token and notification text |
| Analytics and stability | Measuring App usage and reporting technical errors | Usage events with opaque identifiers and technical device data, without amounts, names or tax data |
| Sending account emails | Email address and message content | |
| Merchant logos | Showing the logo of a transaction's merchant | Merchant name, without User data |
All these providers process data on our behalf, under contracts that require confidentiality and equivalent security measures and forbid them from using it for their own purposes. We may change providers within each kind without changing what is shared or why. If you want to know who processes your data, write to the email in Section 13 and we will answer as the law that applies to you requires.
5.3. Competent authorities
We may disclose data when required by a competent authority through a court order, subpoena or valid legal request, and we will notify you where the law allows.
5.4. Business transfers
In the event of a merger, acquisition, asset sale or reorganization of the Company, data may be transferred to the successor, with at least thirty (30) days' prior notice to Users and keeping the level of protection granted in this Policy.
5.5. Aggregated and de-identified data
We may publish and share aggregated, de-identified and non-re-identifiable data (for example, average spending trends by category at country level) with partners, media or publications. This data does not identify any individual User.
6. International data transfers
6.1. All Service data is processed and stored in the United States, where our infrastructure providers are based.
6.2. Users in Mexico: by accepting this Policy, you expressly consent to the international transfer of your personal data to the United States, under article 36 of the LFPDPPP. Recipients are contractually bound to maintain the same protection conditions.
6.3. Users in Panama: by accepting this Policy, you expressly consent to the international transfer of your personal data to the United States, under Law 81 of 2019. Transfers are made under standard contractual clauses and equivalent confidentiality commitments.
6.4. Users in the European Union or United Kingdom (if applicable): Counting does not currently actively offer the Service in the EU/UK. If we expand operations in the future, we will adopt Standard Contractual Clauses (SCCs) and the corresponding impact assessment.
7. Data retention
7.1. Active account: for as long as you use the Service.
7.2. Deleted account:
- Personally identifiable data: deleted within thirty (30) days of the deletion request.
- Backups: purged within a maximum of ninety (90) days through backup rotation.
7.3. Receipt images (Plus, Pro and Business plans): for as long as the transaction they belong to exists; they are deleted when the transaction or the account is deleted. An image without a transaction is deleted within 24 hours.
7.3.1. Copies kept to improve receipt reading (section 2.5.1): twenty-four (24) months from the scan, or until you turn the option off, whichever comes first.
7.4. Aggregated and anonymized data: kept indefinitely, since it does not identify any User.
7.4. Security and audit logs: up to twenty-four (24) months for incident investigation.
7.5. Tax and accounting records: where applicable law requires retention (for example, transaction records for tax compliance), we may retain them for the minimum period required, typically up to seven (7) years in the United States and five (5) years in Mexico and Panama.
7.6. Support communications: up to twenty-four (24) months for traceability and to improve support.
8. Your rights
8.1. General rights
Regardless of your jurisdiction, you have the right to:
- Access the personal data we process about you.
- Rectify inaccurate or outdated information.
- Delete your account and associated data (right to be forgotten, subject to legal exceptions).
- Object to certain processing.
- Port your data in a structured, commonly used format (CSV or JSON).
- Withdraw consent at any time for processing based on consent (marketing, AI OCR, attaching images).
- File a complaint with the competent authority in your jurisdiction.
8.2. How to exercise your rights
You can exercise any of these rights through:
- App: Profile → "Export data", and Profile → "Delete account" (at the bottom of the screen).
- Email: [email protected]
We will reasonably verify your identity before handling the request, to prevent fraud. We do not charge for handling requests, except in manifestly unfounded or repetitive cases.
8.3. Response times
- United States: up to forty-five (45) days, extendable by another forty-five (45) days when justified (CCPA).
- Mexico: up to twenty (20) business days, extendable by an additional twenty (20) business days (LFPDPPP).
- Panama: within the time limits of Law 81 of 2019.
8.4. Non-discrimination
We will not discriminate against you for exercising your privacy rights. We will not degrade the Service, raise prices or deny access because you exercise these rights.
9. Security
We implement reasonable technical and organizational measures to protect your data, including:
9.1. Encryption
- Encryption at rest: all stored data is encrypted with AES-256, both in the database and in the receipt storage.
- Encryption in transit: all communications between the App, the backend, the database and providers use TLS 1.3.
- Column-level encryption: sensitive PII fields (phone number, address, date of birth, official identifiers) are additionally encrypted at column level with keys managed in a dedicated key management service.
- Key rotation: Data Encryption Keys rotate at least every twelve (12) months; master keys rotate automatically in the key management service.
9.2. Access controls
- Mandatory multi-factor authentication (MFA) for all technical staff with access to production infrastructure.
- Role-Based Access Control (RBAC) under the principle of least privilege.
- Audit logs of critical operations and production access.
9.3. Operational practices
- Separate development, staging and production environments.
- User passwords protected with a one-way hash.
- Passwords are never logged, displayed or returned in API responses.
- Code review, automated testing and secure deployment pipelines.
- Continuous monitoring and security alerts.
9.4. Breach notification
In the event of a security breach that compromises personal data, we will notify the competent authority within seventy-two (72) hours where the law requires it, and affected Users without undue delay, describing the nature of the breach, the data affected, the measures taken and our recommendations.
9.5. A realistic acknowledgment
No online system is completely invulnerable. Although we apply recognized industry standards, we cannot guarantee absolute security. The User is also responsible for protecting their credentials, using strong passwords and turning on biometric authentication when available.
10. Minors
10.1. The Service is NOT intended for anyone under 18. When signing up, the User must confirm through a mandatory checkbox ("age gate") that they are 18 or older.
10.2. We do not knowingly collect personal data from children under 13 (Children's Online Privacy Protection Act, "COPPA", United States).
10.3. If we find that we have collected data from someone under 18 without the verifiable parental consent required by the applicable jurisdiction, we will delete the account and associated data without delay, and notify the parent or guardian when they can be identified.
10.4. If you are a parent or guardian and believe a minor in your care has created a Counting account, write to us at [email protected] and we will delete it.
11. Cookies and similar technologies
11.1. Mobile app. The Counting mobile app does not use traditional web cookies. It uses native local storage (AsyncStorage, SecureStore, local SQLite) for essential Service functions and offline caching.
11.2. Website (marketing / support). The website https://opwapps.com/legal/counting/privacy may use:
- Essential cookies: required for the site to work (session, security). They do not require consent.
- Analytics cookies: to measure traffic and improve the site. Only with explicit opt-in through the consent banner.
- Marketing cookies: disabled by default. They require explicit opt-in.
11.3. You can manage your web cookie preferences from the site's consent banner or from your browser settings.
12. Changes to this policy
12.1. We may update this Privacy Policy from time to time to reflect changes in our practices, new Service features or legal changes.
12.2. Material changes will be notified at least thirty (30) days in advance through:
- Email to the address associated with your account.
- A prominent banner in the App.
- An update to the "Last updated" date at the top of this document.
12.3. Continued use of the Service after the effective date constitutes acceptance of the updated Policy. If you do not accept the changes, you can close your account before the effective date.
12.4. The current version will always be published in the App and on the website.
13. Contact
Data Protection Officer: [email protected]
OPW DESARROLLOS DE USA, LLC
Florida Limited Liability Company
Address: 2187 SW 1st St, Suite 1029, Miami, FL 33155
Registered agent: 2187 SW 1st St, Suite 1029, Miami, FL 33155
Website: https://opwapps.com/en/legal/counting/privacy
14. California notice (CCPA/CPRA)
Applies when the User resides in the State of California, United States.
Under the California Consumer Privacy Act ("CCPA") and the California Privacy Rights Act ("CPRA"):
14.1. Categories of personal data collected (last 12 months)
- Identifiers: email, name, IP address, device identifier.
- Categories under section 1798.80(e): name, email, personal financial information (entered manually).
- Commercial information: subscription history.
- Internet and network activity: interaction with the App, anonymized analytics events.
- Geographic data: country declared by the User.
- Inferences: suggested categories and preferences derived from use.
14.2. Categories of data shared
See Section 5.2 above. We share only with providers needed to operate the Service.
14.3. Purposes of use
See Section 3 above.
14.4. Right to opt out of "sale" and "sharing"
Counting does not sell or share (under the broader CPRA definition for cross-context behavioral advertising) personal data. However, if a California resident wishes to formally confirm their do-not-sell/do-not-share preference, they can write to [email protected].
14.5. Right to limit the use of sensitive personal information
Under the CPRA, you can ask us to limit the use of your sensitive personal information to what is strictly necessary to provide the Service. Write to us at [email protected].
14.6. Right to non-discrimination
We will not discriminate against you for exercising your CCPA/CPRA rights.
14.7. Contact for CCPA/CPRA requests
Response time: up to forty-five (45) days, extendable by another forty-five (45) days.
15. Mexico notice (LFPDPPP)
Comprehensive Privacy Notice in compliance with the Federal Law on the Protection of Personal Data Held by Private Parties.
15.1. Identity and address of the controller
OPW DESARROLLOS DE USA, LLC, a Florida Limited Liability Company, located at 2187 SW 1st St, Suite 1029, Miami, FL 33155, United States.
Contact email for exercising ARCO rights: [email protected].
15.2. Personal data collected
See Section 2 of this Policy. The controller does not collect sensitive personal data.
15.3. Primary purposes of processing
See Section 3 (subsections 3.1, 3.2, 3.3, 3.4 transactional, 3.5, 3.6, 3.7).
15.4. Secondary purposes of processing
- Sending commercial communications, promotions and marketing content (explicit opt-in).
- Analysis for the development of new products.
You can refuse the secondary purposes at sign-up, at any time from Profile → Notifications, or by writing to [email protected].
15.5. Data transfers that require consent
The controller transfers personal data to the providers listed in Section 5.2, all located in the United States. By accepting this Notice, you expressly consent to that international transfer.
15.6. ARCO rights
You have the right to:
- Access your personal data.
- Rectify inaccurate information.
- Cancel the processing.
- Object to specific processing.
To exercise your ARCO rights, email [email protected] stating: (i) the name and email associated with the account, (ii) an official document proving identity or representation, (iii) a clear description of the right you are exercising and the data involved. We will respond within a maximum of twenty (20) business days, extendable when justified.
15.7. Withdrawal of consent
You can withdraw your consent at any time, with the effects provided for by the LFPDPPP. Withdrawal is not retroactive and may prevent the Service from being provided if it involves essential data.
15.8. Competent authority
National Institute for Transparency, Access to Information and Personal Data Protection (INAI):
Website: https://home.inai.org.mx
15.9. Changes to the Notice
Changes will be notified as described in Section 12 of this Policy.
16. Panama notice (Law 81 of 2019)
Applies when the User resides in the Republic of Panama.
Under Law 81 of March 26, 2019 on Personal Data Protection:
16.1. Data controller
OPW DESARROLLOS DE USA, LLC, a Florida Limited Liability Company. Email: [email protected].
16.2. Definitions
The terms "personal data", "data subject", "processing", "controller" and "processor" have the meaning given in Law 81 of 2019.
16.3. Rights of the data subject
- Access: know the personal data processed and its purposes.
- Rectification: correct inaccurate or incomplete data.
- Cancellation / Erasure: delete the data when it is no longer needed.
- Objection: object to processing on legitimate grounds.
- Portability: obtain a structured, commonly used copy.
- HABEAS DATA: the constitutional right to request information, updating, rectification or erasure.
16.4. How to exercise your rights
Write to [email protected], identifying yourself and clearly describing the right you wish to exercise. We will respond within the time limits of Law 81 of 2019.
16.5. International transfers
Data is transferred to and processed in the United States. By accepting this Policy, you expressly consent to that transfer, under standard contractual clauses and equivalent confidentiality commitments.
16.6. Competent authority
National Authority for Transparency and Access to Information (ANTAI):
Website: https://www.antai.gob.pa
16.7. Consent
The data subject gives prior, express and informed consent by accepting this Policy at sign-up. Consent can be withdrawn at any time as described in Section 8 of this Policy.
Last updated: November 18, 2026



