Olarila · Android

Olarila Privacy Policy

DNMTechLabs · Updated: October 26, 2026.

Publisher and scope

DNMTechLabs publishes Olarila for Android, package com.olarila.mobile. For app support and privacy requests, contact dnmtechlabs@gmail.com. This policy covers the Android app, its local navigation and download features, the forum experience it displays, and native advertising when available.

The app displays olarila.com. Public forum browsing is available without creating a DNMTechLabs account; posting, attachments and other member features may require an Olarila forum account. The website also provides its own privacy policy, cookie information and terms of use.

Forum accounts, content and website services

When you register, sign in, post, contact forum support or attach files, the website receives the information you provide. This can include your display name, registered email address, authentication information, posts, support messages and selected attachments. Public posts and profile information may be visible to other people according to forum settings. Google sign-in, if selected, is also subject to the identity provider’s terms and privacy policy.

The embedded website uses its own cookies, storage, advertising and measurement services. The public website currently includes NitroPay advertising, Google Analytics and Meta’s Facebook Pixel. Google Analytics measures website use and derives approximate location from IP address. The Pixel supports analytics, advertising measurement, matching and advertising or marketing. These services may receive visited URLs, page-view and other interaction events, cookie or similar identifiers, IP address and browser/device information. The forum’s published privacy and cookie policy also lists Google AdSense.

Automatic advanced matching is enabled for the website’s Meta Pixel. Its configuration enables name, email, external identifiers and location parameters when those details are available in website fields or content. Options for gender, telephone number and date of birth are also enabled, but this does not mean the website asks for or sends those details on every page or from every visitor; processing depends on the fields or information actually present. Meta may normalize and hash matching identifiers to associate website activity with a person or account. Hashed or pseudonymous identifiers can still be personal data.

The Pixel’s additional page and product details and automatic event detection without code are enabled. Depending on the page and available information, Meta may receive additional page/content or product details and detected actions beyond the explicit PageView call. This capability is not a statement that every post, attachment or possible field is always sent. Website analytics and advertising services can process information outside your country; their availability and behavior can vary with page, provider settings and website controls.

This Android build applies a host-specific filter to block HTTPS NitroPay script and subresource requests inside the app’s WebView. That filter does not block Google Analytics or Facebook Pixel, change the forum when opened in an external browser or guarantee that every website ad or tracker is blocked. Website services follow the website’s controls and the providers’ policies, including NitroPay, Google and Meta. Website content and service configuration can change.

The native advertising controls do not disable the forum website’s Google Analytics, Facebook Pixel, cookies or other independent network traffic. The native providers’ privacy signals and regional eligibility check do not configure those website services. The targeted NitroPay filter operates separately. Use the website’s privacy and cookie controls for its services. The app does not promise an entirely ad-free or tracking-free forum session.

Navigation, cookies, downloads and diagnostics

The app saves the last eligible internal page locally to offer a continuation shortcut. The device’s web engine keeps session cookies, cache and website storage for browsing and sign-in. The download center holds a bounded list of transfers for the current app session; Android’s download service manages saved files and transfer status.

When you request a download, the app contacts the selected HTTPS destination and may use the relevant session cookies, user-agent and a scoped referring page to preserve authorized access. The destination receives ordinary request data such as your IP address. Downloaded files remain in the location selected or managed by Android until you remove them; uninstalling the app does not necessarily remove files saved outside its private storage.

A small page-to-app bridge reports whether an editor is focused, the browser user-agent and metadata for links you choose to open, share or download. It does not read the text you type into password or other form fields. Information you submit through the website is still handled by the website.

Copy diagnostics is a manual action. It copies app/build version, platform and operating-system information, loading status and session download counts to the clipboard. The app does not automatically send that diagnostic snapshot to DNMTechLabs. Information is sent to support only if you choose to share it.

Android permissions and external services

The app uses internet access for the forum, downloads, the regional eligibility check and available advertising. It can request camera access when you choose to capture media for an attachment. Android’s system picker lets you choose files, photos or videos to attach; older supported Android versions may request storage permission for downloads. You can manage permissions in Android settings.

The advertising-enabled build includes the Android advertising ID permission for the SDK services described below. Native advertising requires valid app configuration, an eligible regional decision and readable local advertising preferences. A refusal saved by an earlier app version continues to block native ads. The release being prepared does not ask for or automatically record affirmative advertising consent.

Links may open your browser, email service or another installed app. The Android release being prepared blocks the known routes for purchasing digital plans and services inside the app, while preserving sign-in and existing member access. Olarila does not provide a native Premium purchase or subscription or collect payment-card details.

Native advertising

The app integrates Unity LevelPlay for one native banner format and occasional interstitials from Unity Ads, ironSource Ads and Meta Audience Network, when enabled and available. Availability depends on the installed version, valid app configuration, region and network approval. Some versions keep native advertising unavailable.

The Android release being prepared does not display an advertising consent screen and does not automatically grant or save affirmative consent. Before any native ad initialization, the app checks regional eligibility and readable local advertising preferences. A refusal saved by an earlier version continues to block native ads. A missing preference is not treated as affirmative consent. Forum access does not depend on native ad availability. The privacy policy remains accessible in Quick actions.

When active, providers may process and share device and advertising identifiers, identifiers generated by their networks, IP address and approximate location derived from it, technical device and network information, diagnostics, app usage and ad interactions. Purposes may include delivery, measurement, analytics, service operation, security and fraud prevention. Processing may occur outside your country. Provider SDK features and remote configuration may also involve purchase or usage information as described in their policies; this does not mean the app receives payment-card details.

GDPR consent is set to false, sale/sharing is restricted through the supported Unity/ironSource privacy signals, and Meta’s Limited Data Use option is set before native ad initialization. Their scope differs by provider and region; they do not remove all processing or guarantee that every provider’s ads are nonpersonalized everywhere. Data already processed by providers is not deleted by blocking subsequent ad requests. These controls do not change the forum website’s independent services described above.

Regional check before native advertising

When the native advertising configuration and local eligibility checks permit it, the app queries a fixed DNMTechLabs HTTPS eligibility endpoint hosted by Cloudflare. The request omits cookies and does not put an account identifier in the URL. Cloudflare receives the source IP address and technical request data needed to deliver and protect the service under its privacy policy. The service returns only an eligibility flag, not a country or location history to the app. The Worker does not keep its own request log; Cloudflare infrastructure may keep technical or security records.

Native ads remain blocked in the European Economic Area, the United Kingdom, Switzerland and Quebec, and when the region is unknown or the check is unavailable, offline or indeterminate. The cached decision is short-lived and may be renewed. The app does not use a local choice or an automatically granted consent to enable native advertising in restricted regions. These native controls do not replace the forum website’s own obligations or controls.

Retention, deletion and your rights

Saved app preferences and the continuation page remain locally until replaced, app storage is cleared or the app is uninstalled. Cookies and website storage can be removed by clearing the app’s Android storage. Downloaded or shared files may need to be deleted separately from their destination. Local deletion does not delete your forum account, public posts, messages or records already held by websites or service providers.

To request deletion of your Olarila forum account and associated personal data, use the prominent Olarila account deletion request page. It provides an email request mechanism and explains ownership verification, manual processing and possible retention. You do not need to reinstall the app to submit a request.

Section 5 of the forum’s Guidelines describes account termination through Client Area contact and states that existing community posts may remain after termination. This does not replace a request to delete the account and associated personal data. Where public contributions are lawfully retained, identifying account/profile details and personal data in them must be deleted or anonymized unless a specific lawful retention reason applies. The deletion page explains how to identify posts containing personal data and request their review.

For access, correction, deletion or other applicable rights over information handled by DNMTechLabs, email dnmtechlabs@gmail.com, identify Olarila and describe your request. Provide only necessary information; do not send a password, two-factor authentication code, advertising identifier or payment-card information. Support messages are used to answer and investigate requests for as long as needed for that purpose and applicable legal or security obligations.

Advertising and website providers also maintain their own rights channels and retention criteria. See the Unity policy and privacy choices, Meta policy, NitroPay policy and Google policy. Deleting local app data or contacting DNMTechLabs does not automatically erase records independently held by those providers.

Adult audience and child safety

The Olarila Android app is intended for adults aged 18 and older. Our Olarila Child Safety Standards prohibit child sexual abuse and exploitation and explain how to report concerns, how reports are reviewed, and the designated child-safety contact. Child-safety reports are used to investigate and address the concern and fulfill applicable legal obligations, with access restricted to those who need the information for those purposes.

Policy updates

Material changes to app features or data handling will be reflected in this policy before the corresponding configuration is distributed. The date above identifies this revision. The Android native interface supports English and Portuguese; forum content and website services follow website and account settings.