Privacy Policy

Effective date: November 9, 2026

This Privacy Policy explains how Oneva handles information in its native garden game and connected services. The provider is the developer identified on Oneva's App Store product page ("we", "us"). This Policy provides information; using the App is not blanket consent to tracking or optional collection. Permissions and consent are requested separately where required.

Summary

Native game progress, squad badges, voice notes and preferences are stored on the device. The App also sends a persistent device identifier and technical request information to our startup service to create or recognize a guest session. Connected pages communicate with their servers and may keep website data. Local storage of game content does not mean that no information leaves your device.

Information the App Processes

The categories below distinguish local game content from information sent to connected services. We use personal information for the described service purposes, not as permission for unrelated advertising or tracking.

Game and progress data: your current run, records, best distance and score, unlocked items, completed goals, milestones, bookmarks, practice results, and your choice of look. This is saved locally using the device's on-device database.

Your created content: the native badge and voice-note tools save the selected or captured photo and microphone recording as local files. Those native tools do not upload that content. If you independently submit information through a connected page or external website, that submission is separate and should be explained at the point of collection.

Preferences: simple settings such as sound, haptics, and motion effects.

Device and guest identifiers: at startup, the App sends a device-associated identifier to the startup service in request headers and as a guest credential. It is derived from Apple's identifier for vendor, with a generated random identifier as a fallback, and cached in local preferences and Keychain. The service returns a guest user ID and session token; the token is saved locally, and the guest ID can be included in later requests. These identifiers support recognition, authentication and session operation. They are not the advertising identifier (IDFA).

Technical request information: requests include device model, operating-system and app versions, build number, package identifier, language, region setting and time zone. Region is obtained from device settings, not GPS. Servers receiving requests necessarily receive the connection IP address and the requested address. The native App does not request contacts, GPS location or health data.

Permissions and Their Uses

The native camera and microphone tools request permission when you choose those features; the photo picker gives access to the item you select. Denying access prevents the corresponding optional feature. The App can also display an ATT prompt when the main interface opens. System permission decisions can be changed in Settings.

Camera: the native badge tool requests access when you choose to take a photo and saves the cropped badge locally. Connected pages may also request camera access through WebKit; only allow it for a feature you choose and whose purpose you understand. A page receiving a camera stream can process or transmit that stream, so the local badge-storage statement does not apply to that separate web feature.

Photos: when you tap to create a squad badge from an existing picture, the App opens the system photo picker. You pick the exact photo yourself; the App does not scan or read your full photo library, and the selected picture is stored locally as your badge.

Microphone: the native voice-note tool requests access when you choose to record and saves the recording locally. Connected pages may separately request microphone access through WebKit; audio made available to a page can be processed or transmitted by that page. Decline access if you do not wish to use that feature.

Tracking permission: Oneva contains an App Tracking Transparency prompt. The native implementation does not read the advertising identifier or include an advertising or attribution SDK. First-party guest authentication using a device identifier is distinct from tracking activity across other companies' apps and websites. ATT refusal does not authorize such tracking, and an ATT prompt alone is not evidence that tracking occurs. Any tracking must be specifically disclosed and require your prior ATT permission; device identifiers must not be used to bypass your choice. You can change the ATT choice in Settings.

How Your Information Is Used

Native on-device information supports game progress, records, collections, badges, voice notes and preferences. Device and guest identifiers support startup authentication and session continuity; technical request information supports device compatibility, language selection and service operation. If you contact us, we receive the email address and message you send and use them to respond. Do not send passwords or session tokens. A new, incompatible use of personal information requires an updated notice and any consent required by law.

Data Sharing and Third Parties

Our startup service receives the request information described above; production API requests are configured for api-linker.onevabig.com. The native game does not include third-party advertising, attribution or social-login SDKs. Connected pages and links can contact additional servers, and the applicable collection notice must identify the provider and purposes before you submit information. When we engage a service provider to process personal information on our behalf, we require it to use the information only for the authorized service and provide protection at least equivalent to this Policy. Apple processes App Store and device-service information under its own privacy policy.

Data Storage, Security, and Retention

Native game data, badges, voice notes and preferences remain in the App's local storage until removed through the relevant controls or ordinary app-data deletion. Device identifiers are also stored in Keychain and may survive uninstalling. Session tokens are stored in local preferences. WebKit maintains website data in its persistent website-data store. Device or cloud backups follow your backup settings and may retain copies separately. We rely on platform storage protections and HTTPS for configured startup API requests; no storage or transmission system is completely secure.

Service-side retention: device-linked guest records and related service information are retained only for as long as needed to provide the service and meet applicable security, dispute-resolution or legal obligations. Retention is assessed by data type, purpose and legal requirements rather than by the App uninstall date. On a verified deletion request, information no longer needed for a lawful purpose is deleted or de-identified; any retained exception must be explained. This Policy does not promise that uninstalling automatically triggers server deletion.

Your Choices and Controls

You can remove a saved badge or voice note using its in-app controls, clear the run journal, or use Settings > Reset all progress to remove native game progress and media. These controls do not delete server-side guest records, Keychain identifiers or all website data. To request access, correction or deletion of service information, email lanyun707yu@sina.com. We may request proportionate information to verify your request; do not send your session token or password. Requests are handled subject to applicable law, including any legally required retention, with reasons provided for any limitation.

Cookies and Tracking Technologies

The App uses a persistent WebKit website-data store, so connected pages can store cookies, cache and local website data. These can support sessions and page operation; their specific contents depend on the pages you visit. The bundled launch page alone is not a complete description of the App's web activity. Website storage must not be used to bypass tracking choices. An external browser has its own storage and privacy controls.

Children's Privacy

Oneva is not designed specifically for children. Follow its App Store age rating and applicable local age requirements. A guest startup request can transmit the device information described above even without an email/password registration; therefore the absence of registration does not mean that no data about a child can be received. A parent or guardian who believes a child has provided personal information should contact us to request review and deletion. Where parental consent is legally required, the relevant collection must not proceed without it.

Changes to This Policy

We will update this Policy when our practices change and show the effective date. Material changes will be brought to your attention through the App, an update notice or another appropriate channel. New collection or uses that require consent will not rely solely on continued use of the App.

Contact Us for Privacy-Related Inquiries

For privacy questions or requests concerning your information, contact lanyun707yu@sina.com. The developer identified on Oneva's App Store listing is responsible for this Policy. Depending on your location, you may have rights to access, correct, delete, restrict or object to processing, obtain a portable copy, withdraw consent, and complain to your local data-protection authority. Withdrawing consent does not affect earlier lawful processing.