Last updated: 25 Nov 2025
Welcome to “Zivo AR Drawing” (“the App”). This Policy explains how Nanjing Heyback Technology Co., Ltd. (“Company”, “we”) collects, uses, shares, and protects information when you use the App. Because Zivo does not provide account registration, all data is linked only to device-level identifiers or randomly generated session IDs.
| Item | Details |
|---|---|
| Company | Nanjing Heyback Technology Co., Ltd. |
| Registered Address | F2594, No. 18 Yinchun Road, Maigaoqiao Innovation Park, Qixia District, Nanjing, Jiangsu, China |
| Support & Privacy Email | support@xiaoheigohome.com |
| Legal Representative | jed@xiaoheigohome.com |
| Data Protection Officer | Not appointed; please contact us via the support email |
We do not ask you to create an account, and we do not upload your drawings or live camera feed to our servers. We may process the following categories of information in order to deliver AR drawing features, subscriptions, and advertising:
Device & App Diagnostics (Firebase
Analytics)
Device model, OS version, language, region, time zone, app version,
first launch time, coarse location inferred from IP, engagement events
(e.g. “created AR board”, “exported timelapse”).
Purpose: product analytics, crash reproduction, feature
prioritisation.
Crash & Performance Logs (Firebase
Crashlytics)
Stack traces, device status at crash, anonymised installation ID. These
logs help us stabilise AR rendering and camera pipeline.
Subscription & Purchase Metadata
(RevenueCat)
Store country, product identifier, receipt / purchase token, renewable
status, pricing, promotional offers. No full payment instrument data
reaches us.
Advertising & Attribution Data
Camera & Photo Library Permissions
We use the rear camera, LiDAR/ARKit/ARCore data, and optionally your
photo library to overlay drawing guides. Frames and photos are processed
on-device and are not uploaded to our servers; only
permission status is logged for diagnostics.
Support Communications
If you email us, we receive the information you provide (email,
attachments, device screenshot). We use it solely to resolve your
request.
| Purpose | Legal Basis |
|---|---|
| Render AR scenes, brushes, offline assets | Contract performance (Art. 6(1)(b)) |
| Manage subscriptions and entitlements via RevenueCat | Contract performance (Art. 6(1)(b)) |
| Measure product performance, prevent abuse, debug crashes | Legitimate interests (Art. 6(1)(f)) |
| Deliver and personalise ads, attribute installs (AdMob, Meta, Apple Ads) | Consent where required (Art. 6(1)(a)); otherwise legitimate interest |
| Comply with legal / tax obligations | Legal obligation (Art. 6(1)(c)) |
You may withdraw consent for advertising tracking at any time in iOS Settings › Privacy › Tracking or Android Settings › Google › Ads. This will not affect processing performed before the withdrawal.
| Permission | Reason of Use | Storage |
|---|---|---|
| Camera / ARKit / ARCore | Render live AR brushes and anchors; capture reference planes | Frames stay on device; we only log permission status |
| Photo Library / Storage | Import pictures as tracing layers | Imported files stay local; metadata is not uploaded |
| Network | Download brush packs, sync subscriptions, load ads | Minimal telemetry (as listed above) |
| App Tracking Transparency / Advertising ID | Deliver personalised ads when you opt in | Identifier is shared with ad partners per their DPAs |
We currently do not access motion sensors beyond what ARKit/ARCore requires; if future versions do, we will update this Policy first.
| Data Type | Retention Policy |
|---|---|
| Firebase Analytics events | 26 months (default Google retention) |
| Crashlytics logs | 90 days, automatically purged by Google |
| RevenueCat subscription metadata | Retained during active entitlement + 3 years for tax/audit |
| Ad impression / attribution data | Up to 24 months depending on network requirements |
| Support tickets | Deleted within 24 months of resolution unless law requires longer |
Uninstalling the App removes locally cached brushes, preferences, and any downloaded scenes.
Operational services run on Alibaba Cloud (Singapore region). Telemetry may also be stored by Google (United States, EU), RevenueCat (United States), Meta (global infrastructure), and Apple (United States/EU). We rely on Standard Contractual Clauses (SCC 2021/914/EU) or equivalent safeguards provided by each processor.
| Provider | Role / Data Scope | Documentation |
|---|---|---|
| Google Firebase Analytics | Event analytics, device info | https://policies.google.com/privacy |
| Google Firebase Crashlytics | Crash diagnostics | https://firebase.google.com/support/privacy |
| Google AdMob & Privacy Sandbox | Advertising delivery, contextual targeting, attribution | https://support.google.com/admob/answer/6128543 |
| Meta Audience Network | In-app ads (if enabled in your region) | https://www.facebook.com/about/privacy |
| Apple Search Ads / AdServices / SKAdNetwork | Install attribution for iOS | https://searchads.apple.com/privacy/ |
| RevenueCat, Inc. | Subscription entitlement, receipts | https://www.revenuecat.com/privacy |
| Alibaba Cloud (Singapore) | Static asset hosting, optional CDN logs | https://www.alibabacloud.com/help/en/legal/latest/fe2cxg |
Each partner processes data strictly under our instructions and agreements.
Where applicable (GDPR / UK GDPR / LGPD / etc.), you may:
Please email support@xiaoheigohome.com with your device model, OS, app version, and (if possible) advertising ID so we can locate relevant telemetry.
Because Zivo stores drawings and brushes locally:
Zivo is rated 4+ on the App Store / E for Everyone on Google Play and is intended for a general audience. Children should use the App under parental supervision to ensure safe spatial awareness. We do not knowingly collect personal data from children beyond minimal analytics described above.
We may update this Policy to reflect product or regulatory changes. Material updates will be announced via in-app notice and will require renewed consent if the change affects advertising or sensitive permissions.
Contact us:
If you are dissatisfied with our response, you may contact your local data protection authority.