RVLWORKS, S.L.

Privacy Policy

Last updated: 14 September 2026

This Privacy Policy explains how RVLWorks, S.L. (“RVLWorks”, “we”, “us” or “our”), a company based in Spain, handles personal data across RVLWorks websites, mobile applications, games, desktop applications, cloud services and other digital products that link to this policy (collectively, the “Products”). It is written to serve as the general privacy policy for RVLWorks products, including Android applications distributed through Google Play.

Because our Products have different functions, not every data category described below is collected by every Product. A Product may provide an additional privacy notice, in-app disclosure, permission prompt, store listing, Google Play Data safety disclosure or product-specific policy that describes its actual data practices in more detail. If a product-specific privacy notice conflicts with this general policy, the product-specific notice controls for that Product.

1. Controller and privacy contact

Unless a product-specific notice states otherwise, the controller responsible for personal data covered by this policy is:

RVLWorks, S.L.
Spain
Email: rafael@rvlworks.com

For privacy questions, rights requests, account or data deletion requests, or questions about a particular RVLWorks app, contact us at the email address above and identify the Product concerned.

2. Scope and product-specific notices

This policy applies to Products that display or link to it. Some RVLWorks services have their own more specific legal documentation. For example, AgooCloud has a product-specific Privacy Policy describing its backup-service data practices. Where a Product has a dedicated privacy policy, that policy should be read first for that Product.

Third-party platforms used to obtain, install, purchase or interact with a Product—such as Google Play, Steam, payment providers or social platforms—operate under their own privacy policies. Their processing is not controlled by this policy except where they act as a processor or service provider for RVLWorks.

3. Data we may process

The categories below describe data that an RVLWorks Product may process when the category is relevant to its features. A particular Product may process only a subset of these categories.

3.1 Account and profile data

• Name, display name, username or other account identifier.
• Email address and account-verification status.
• Password hashes, authentication tokens or identifiers from a sign-in provider. We do not need to know a password that is managed solely by a third-party sign-in provider.
• Account settings, preferences, subscription status and entitlement information.

3.2 Information you submit to us

• Messages, support requests, bug reports, survey responses and other communications.
• Information you choose to send with a support request, including screenshots, attachments or diagnostic files.
• Business or billing contact details when you purchase or manage a business service directly from RVLWorks.

3.3 Content and service data

Some Products are designed to store, process, synchronize, back up, generate or otherwise work with content that you choose to provide. Depending on the Product, this may include files, documents, saved preferences, game-save information, project data or other content you deliberately submit or select. We process that content only as needed to provide the Product, maintain security, troubleshoot problems, comply with law or as otherwise described in a product-specific notice.

For cloud or backup services, the relevant product-specific policy describes in greater detail the distinction between account/service metadata and customer content.

3.4 Device, application and network data

• Device type, manufacturer/model, operating system and version.
• Application name, package identifier, application version, language, region and configuration.
• Internet Protocol (IP) address, connection timestamps and basic network information.
• Device or installation identifiers that are made available by the operating system or distribution platform and are necessary for product functionality, security, licensing, analytics or fraud prevention.
• Crash logs, error logs, performance metrics and technical diagnostics.

We do not intentionally collect persistent device identifiers or other sensitive identifiers unless they are necessary for a disclosed, policy-compliant feature and permitted by the relevant platform rules.

3.5 Usage and gameplay data

A Product may process information about how it is used, such as screens or features used, session length, feature interactions, game progress, achievements, settings, performance events, error events and similar product telemetry. This information may be used to operate the Product, understand reliability, balance gameplay, improve features and prevent abuse. Whether a particular app sends this information to RVLWorks or a service provider is described by that Product’s disclosures.

3.6 Purchases, subscriptions and entitlements

If you buy a Product, subscription or digital item, we may receive transaction-related information such as the product purchased, order or transaction identifier, purchase status, subscription status, country/region, price or entitlement information. When a purchase is processed by Google Play, Steam or another platform, that platform normally handles payment-card or payment-account details. RVLWorks generally does not receive your full payment-card number from an app-store purchase.

3.7 Device permissions and sensitive data

An app may request a device permission only when a feature needs access to the corresponding capability or data. Depending on the Product, this could include access to files or storage, notifications, camera, microphone, contacts, nearby devices, approximate or precise location, or another Android/iOS capability. Whether a permission is requested and how the related data is used depends on the specific app. The operating-system permission prompt, any required prominent in-app disclosure and the Product’s store/privacy disclosures provide the app-specific explanation.

RVLWorks does not treat the presence of a permission as permission to use the underlying data for unrelated purposes.

3.8 Website and cookie data

Our websites may process standard web-server information such as IP address, browser type, requested pages, referrer information, timestamps and security logs. They may use cookies or local storage for essential functions, preferences, security and—where deployed—analytics. If non-essential cookies or similar technologies require consent under applicable law, we will request that consent before using them.

4. How we use data

Depending on the Product and the data involved, we use personal data to:

• provide, operate and deliver the Product and its requested features;
• create and manage accounts, authentication, subscriptions and entitlements;
• store or process content that you ask a Product to handle;
• provide customer support and respond to enquiries;
• maintain reliability, diagnose crashes and bugs, and improve performance;
• develop, test and improve Products and features;
• protect users, RVLWorks and third parties against fraud, spam, abuse, cheating, security incidents and unauthorized access;
• process purchases and verify licenses or entitlements;
• send service messages such as account, security, billing, support or material product notices;
• send optional marketing communications where permitted and where you have not opted out;
• comply with legal obligations, enforce agreements and establish, exercise or defend legal claims; and
• carry out other purposes that are clearly disclosed when the data is collected.

5. Legal bases for users in the EEA, United Kingdom and similar jurisdictions

Where data-protection law requires a legal basis, we rely on the basis appropriate to the particular processing:

• Contract: processing necessary to provide a Product, account, subscription or service that you request.
• Legitimate interests: operating and improving Products, securing systems, preventing abuse, measuring reliability and responding to business/support enquiries, where those interests are not overridden by your rights.
• Legal obligation: processing needed to comply with tax, accounting, consumer-protection, law-enforcement or other binding legal requirements.
• Consent: where consent is required, for example for certain optional permissions, marketing communications, cookies or processing that applicable law requires us to base on consent.

You may withdraw consent at any time where consent is the legal basis. Withdrawal does not affect processing already carried out lawfully before withdrawal.

6. How data may be shared

We do not disclose personal data simply because it may be commercially useful. We share data only when needed for a legitimate purpose described in this policy, a Product-specific notice or applicable law. Recipients may include:

• Service providers and processors: hosting, infrastructure, content delivery, database, authentication, email, customer support, security, analytics, crash-reporting and similar providers that help us operate Products.
• Distribution and platform providers: Google Play, Steam and other stores or platforms when needed to distribute Products, verify purchases, manage subscriptions, provide platform features or comply with platform requirements.
• Payment providers: banks, payment processors or app stores when they process purchases or subscriptions.
• Professional advisers: accountants, auditors, lawyers and insurers where reasonably necessary.
• Authorities or other parties for legal/security reasons: when disclosure is required by law or reasonably necessary to protect rights, users, systems or public safety.
• Business transaction recipients: if RVLWorks is involved in a merger, acquisition, financing, reorganization, insolvency or sale of a business or assets, subject to appropriate confidentiality and legal safeguards.

Where a third party acts as an independent controller—such as an app store processing its own account or payment data—its own privacy policy governs that processing.

7. Google Play, Android and third-party SDKs

RVLWorks Android applications may be distributed through Google Play. Google may process information independently in connection with Google Play, Google Play Services, purchase processing, integrity/security services or other Google features used by an app. Google’s own privacy documentation governs Google’s independent processing.

An RVLWorks app may contain third-party software development kits (SDKs) used for a specific function such as crash reporting, analytics, authentication, cloud infrastructure, advertising, payments or other product features. When an SDK is present, we are responsible for evaluating its data practices and for making the disclosures required for our app. The app’s Google Play Data safety section and any app-specific notice should reflect the SDKs and data flows actually present in that version of the app.

If an app uses advertising or personalized advertising, the app will provide the disclosures and choices required by applicable law and platform rules. Not all RVLWorks Products use advertising.

8. Data security

We use technical and organizational measures designed to protect personal and sensitive user data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure or access. Depending on the Product and the sensitivity of the data, these measures may include encrypted network transport (such as HTTPS/TLS), access controls, separation of duties, authentication controls, software and dependency updates, logging/monitoring, backups, data minimization and incident-response procedures.

No system can be guaranteed to be completely secure. You are responsible for protecting passwords, device access and recovery credentials under your control and for using appropriate security settings available in the Product.

9. Data retention

We retain personal data only for as long as reasonably necessary for the purpose for which it was processed, taking into account the Product, the user’s relationship with us, security needs and legal obligations. In general:

• account and service data is retained while an account or service relationship remains active and is then deleted or anonymized when it is no longer needed, subject to the exceptions below;
• diagnostic, security and anti-abuse logs are retained for a limited period appropriate to troubleshooting, reliability and security, and may be retained longer when they relate to an active incident, abuse investigation or legal claim;
• support communications may be retained for a reasonable period so we can maintain case history and defend or resolve disputes;
• transaction, invoice and accounting information may be retained for the period required by applicable tax, accounting and consumer-protection law; and
• residual copies may remain temporarily in secure backups until they are overwritten or rotated in the ordinary course, unless law requires longer preservation.

Product-specific retention periods may be provided where a Product’s data model requires more precise rules.

10. Account deletion and data deletion

If an RVLWorks Product allows you to create an account, you can request deletion of that account and the data associated with it. Where an app provides an in-app account-deletion control, you should normally use that option first. You can also start a request through our Data & Account Deletion page or by emailing rafael@rvlworks.com.

Deleting an app from your device does not necessarily delete an account or server-side data. When we complete a valid account-deletion request, we delete or irreversibly anonymize data associated with the account except information that we must retain for legal compliance, fraud/security prevention, dispute resolution or another lawful reason. Any retained information is limited to the relevant purpose and retained only as long as necessary.

11. International data transfers

RVLWorks is based in Spain, but service providers or platform partners may process data in other countries. Where personal data is transferred from the European Economic Area, United Kingdom or another jurisdiction that restricts international transfers, we use an appropriate legal transfer mechanism where required, such as an adequacy decision, approved contractual clauses or another lawful safeguard.

12. Children’s privacy

Unless a Product’s store listing or product-specific notice expressly says otherwise, RVLWorks Products are not directed to young children. We do not knowingly collect personal data from a child in a way that requires parental consent without obtaining the required consent or using another lawful basis permitted for the relevant Product and jurisdiction.

If a Product is specifically designed for children or participates in a platform’s families program, we will apply the additional rules relevant to that Product, including restrictions on SDKs, advertising and personal-data collection. If you believe a child has provided personal data inappropriately, contact us at rafael@rvlworks.com.

13. Your privacy rights

Depending on where you live and the circumstances, you may have rights to:

• request access to personal data we hold about you;
• correct inaccurate or incomplete personal data;
• request deletion of personal data;
• restrict or object to certain processing;
• receive certain data in a portable format;
• withdraw consent where processing is based on consent;
• opt out of direct marketing; and
• lodge a complaint with a competent data-protection authority.

To exercise a right, email rafael@rvlworks.com and identify the Product and account concerned. We may ask for information reasonably necessary to verify your identity and protect the account from unauthorized requests.

If you are in Spain, you may also contact the Agencia Española de Protección de Datos (AEPD) at www.aepd.es.

14. Automated decision-making

Unless a Product-specific notice states otherwise, RVLWorks does not use personal data to make solely automated decisions that produce legal or similarly significant effects on individuals. Products may use automated systems for ordinary functions such as spam, fraud, security, matchmaking, game balancing, content organization or service reliability where those functions do not have such legal or similarly significant effects.

15. Changes to this Privacy Policy

We may update this policy when our Products, data practices, providers or legal obligations change. We will publish the revised policy on this page and update the date at the top. If a change materially affects how an existing Product handles personal data, we will provide additional notice where required by law or appropriate to the Product.

16. Contact

For privacy questions or requests:

RVLWorks, S.L.
Spain
rafael@rvlworks.com

← Back to RVLWorks