Orlyra

Orlyra Privacy Policy

Version 1.0 · Last updated 8 October 2026

This notice describes Orlyra’s current services. Production advertising is disabled. The advertising section explains the planned integration and the separate privacy choices that apply to configured test builds.

Who is responsible for your information?

Orlyra is operated by DONKEYBYTE GAMES LTD, Orestou 3, 3096 Limassol, Cyprus. We are responsible for the personal information we process to operate Orlyra.

For privacy questions or requests, email contact@donkeybytegames.com. Our website is www.donkeybytegames.com.

This policy covers Orlyra's app and its supporting services. External websites, official sources, sign-in providers and advertising partners may have their own privacy notices. Our company website may also use services and cookies that are separate from the app.

What Orlyra does

Orlyra helps users find official product recalls, safety notices and information about potentially harmful ingredients or other product-related risks. It supports product searches, barcode lookups, saved items, product submissions and notifications. It is intended for users aged 16 and over.

We do not ask you to provide medical records, diagnoses or health histories. Avoid including health information, personal addresses, faces or other unnecessary personal information in product submissions or photos.

Information we process

Account information

When you sign in, we receive an account identifier and information made available by your sign-in provider, such as your name, email address and profile image. Firebase Authentication supports account access. We use account identifiers to associate saved items and other account features with the correct user. Google sign-in is subject to Google's own terms and privacy notice.

Product searches and barcode lookups

We process the search text, product code and country or filters you provide to return relevant results. Some preferences, recent searches and cached results are stored on your device. Online lookups send request information to Orlyra's backend.

Our backend can query product-information providers, including Open Food Facts, Open Beauty Facts, Open Pet Food Facts, Open Products Facts, UPCitemdb and USDA FoodData Central, depending on the product and available fallback. These requests can contain the product code or relevant product query. Backend queries do not inherently send those providers your Orlyra account identity; providers still receive the network request made to their service. Direct requests from your device, including remote images and external links, can disclose your IP address and normal request information to the recipient.

Camera permission lets you scan barcodes. Barcode scanning is different from deliberately submitting a photo. A photo that you choose to submit may be uploaded and processed as described below.

Saved items, stories and notifications

If you use account features, we process saved product identifiers, saved stories, preferences and relevant activity information. When push notifications are enabled, we process a device registration token and platform information to deliver notifications through Firebase Cloud Messaging. You can manage notification preferences in the app where available and through your device settings. Notification contents may appear on your lock screen according to your device settings.

Product contributions and photos

When you submit a product, we process the product information and photographs you provide, your account identifier, submission status and review history. Product information can include its name, brand, category, quantity and ingredient text. Firebase Storage stores uploaded photos. Administrators can process submitted label photos through Google Cloud Vision to extract text for review. Automated text extraction can be inaccurate; reviewed product information is separate from a medical assessment.

Approved product information and associated product photos can be made available to other Orlyra users. Do not submit confidential material or unnecessary personal information. Unapproved submissions are subject to administrator review rather than automatically becoming public.

Country information

Orlyra uses your selected country and can estimate your country from network information to improve relevance. When country information is unavailable from request headers, our backend can send the request IP address to ipwho.is for country detection. This is approximate network-based information, not a request for GPS access. Choosing a country in the app does not change the fact that online services receive network request information.

Technical and support information

Our infrastructure processes information needed to handle requests and operate securely, including IP addresses, request times, device or platform information, errors and service logs. If you contact us, we process your email address, message and any information you provide so we can respond. Share only information needed to resolve your request.

Optional usage metrics

Optional usage reporting is off by default. If you turn it on, the app sends limited events such as opening a tab or completing/failing a lookup, along with the platform, a random event identifier and your enabled preference. Requests are authenticated. The backend uses account-linked records to enforce limits and prevent duplicates, and maintains aggregate daily counts.

The optional event payload does not include search text, barcodes, ingredient details, submitted photos or medical information. These events are not wholly anonymous because authentication and account-linked rate-limit records are involved. Turning usage reporting off stops future optional events; it does not automatically remove records already processed.

Why we use information

We use information to provide requested features, maintain accounts and saved items, return product information, review contributions, deliver notifications you enable, answer support requests and protect the service against abuse.

Where the GDPR applies, we rely on the following legal bases, according to the purpose of processing:

Information is required only for the feature that needs it. Declining camera permission, sign-in, notifications or optional reporting can prevent the corresponding feature, without granting permission for a different purpose.

Advertising and your choices

Production advertising is not active in the current integration. Registered test builds can use Unity LevelPlay / ironSource to mediate Google AdMob, Unity Ads and Meta Audience Network, together with ironSource inventory where configured. These are planned sources, not a statement that every network is currently active. We will identify the enabled partners and update this notice before production advertising is introduced.

Advertising SDKs can process device and advertising identifiers, IP address, app/device information, ad displays and interactions, approximate location and privacy-choice signals, depending on the network, configuration and your choices. Partners can use this information for ad delivery, measurement, fraud prevention and, where permitted, personalization. Their practices are described in their own privacy notices.

The Orlyra integration does not pass your Firebase account identifier, saved products, barcode scans, search text, ingredient information or submitted photos to LevelPlay as advertising targeting data. Do not interpret a product displayed next to an advertisement as an endorsement by Orlyra or an official authority.

Where required, Google's User Messaging Platform presents advertising privacy choices before the application starts its advertising flow. Permission to request an ad can include restricted or nonpersonalized delivery; it does not mean you have agreed to all purposes or all vendors. On iOS, the operating system can separately ask for tracking permission. Advertising choices, that operating-system permission and optional usage reporting are different decisions.

Where the consent service requires a privacy-options entry point, Settings offers Advertising privacy choices. In the current test integration, changing those choices pauses application ads until you fully close and restart the app. Refusing optional advertising consent does not require accepting optional usage reporting. Production advertising will not be enabled before the applicable regional choices are configured.

The intended minimum age of 16 is not permission for personalized advertising to minors. Advertising remains disabled in production while the audience and regional privacy controls are being completed.

Partner notices:

Who receives information?

Recipients include Google/Firebase for hosting, authentication, storage, notifications and label-text extraction; product-information providers for applicable lookup requests; ipwho.is for fallback country detection; authorized administrators reviewing submissions; and advertising services when that integration is enabled. External image, font and linked-site services receive request information when contacted.

Approved contributions can be shared with app users as described above. We may also disclose information when legally required or when necessary to investigate abuse or protect legal rights. We do not pass your saved-product or ingredient information to LevelPlay as advertising targeting data. Some advertising disclosures can count as sale or sharing under particular laws; applicable opt-out choices and enabled partners will be described before production advertising is introduced.

Storage locations and international processing

We are based in Cyprus. Our primary Firestore database is in Warsaw, Poland (europe-central2). Our Firebase product-photo storage bucket is in the EU multi-region. These locations do not mean that every service or every request is confined to the EU: Orlyra uses both European and US function endpoints, Google/Firebase services can involve international processing, and external lookup, image and country-detection services receive requests as described above. The “global” location of our logging buckets is not a promise of EU-only storage.

Google publishes information about its privacy and security practices, applicable data-processing terms and safeguards for international transfers, including standard contractual clauses for relevant services. These descriptions do not establish that every third-party recipient uses the same safeguards. You can contact contact@donkeybytegames.com to ask about recipients and safeguards applicable to your information. See also the ipwho.is service privacy notice for fallback country detection.

How long information is kept

Account-linked information is kept while needed to provide the features you use, subject to deletion requests and justified legal or security needs. Saved items can be removed using available controls. Submitted information is kept while it is under review or remains part of the product catalogue; account deletion has a separate cleanup process described below.

Our current automated retention settings are:

The first three categories have active Firestore expiry policies. Expired documents are removed by background processing, so expiry is not a guarantee of deletion at an exact instant. An account-deletion request also removes its account-linked usage quota records as part of cleanup.

Recovery copies: Firestore point-in-time recovery retains historical database versions for up to 7 days. Deleted product photos can remain recoverable in restricted storage for 7 days under the storage bucket’s soft-delete setting. Removal from active app use therefore does not mean every recovery copy disappears immediately. No scheduled Firestore database backups were configured when these settings were checked on 8 October 2026; the seven-day database recovery window remains enabled. Restoring data requires administrator access and is not ordinary public app access.

Support correspondence is kept while needed to resolve your enquiry and any related complaint, security investigation or legal claim. The relevant criteria include whether the matter remains open, applicable limitation periods and legal preservation duties. A request to delete support correspondence is assessed against those purposes and obligations. Third-party services have their own retention practices, which may differ from ours.

Account deletion and your rights

You can request account deletion through Settings. We may require recent sign-in to protect your account. Deletion is a background process and may involve retries; it is not completed merely because you sign out or uninstall the app. The current cleanup removes the account's saved data, owned product submissions and related product photos/catalogue entries, and then the authentication account. Some moderation references are anonymized. Aggregate counts and limited deletion/security records can remain, subject to appropriate retention.

Where applicable, you can ask to access, correct, delete, restrict or obtain a portable copy of your personal information, or object to processing based on legitimate interests. You can withdraw consent without changing the lawfulness of prior consent-based processing. Email contact@donkeybytegames.com. We may request proportionate identity verification. We normally respond within one month and explain any lawful extension or limitation.

You can complain to a data-protection authority, including the Cyprus Commissioner for Personal Data Protection or the authority where you live or work. Orlyra does not use solely automated decisions about you with legal or similarly significant effects; product matching is an informational service.

Users under 16

Orlyra is not intended for users under 16. If you believe someone under 16 has provided personal information through Orlyra, contact us so we can investigate and take appropriate action. The current app does not verify every user’s age. Production advertising remains disabled while audience controls are completed.

Security and changes

We use access controls and other measures designed to protect information. No online service can guarantee absolute security. Protect access to your device and sign-in provider.

We will update this notice when the service or relevant practices change. This page identifies its version and last-updated date. Material changes and any new consent requirements will be presented before the affected optional processing begins.