Publication 2026-05-11 · Google Play distribution · English governing text for listing context

Privacy statement concerning Savorly

LUMU TRADING LIMITED publishes this statement as controller. Postal venue: Rm 701, Unit 108, 7/F, Twr B, New Mandarin Plaza, 14 Science Museum Rd, Tsim Sha Tsui, Hong Kong. You may correspond with info@lumutrading.com. The Data Protection Officer is Liu Min, reachable at dpo@lumutrading.com.

I. Territorial coverage and your relationship to us

You install an Android package from Google Play; we process personal data only where that relationship implies a processing role for us.

This statement does not cover imaginary iOS builds. You do not receive a password from us—there is no registration and no login. You nevertheless accept in-app Terms and Privacy notices. You certify adult status through a first-run declaration; we do not perform documentary age verification.

II. Catalogue of processing purposes

You generate live audiovisual streams when you place or accept calls. You generate chat text and attachments when you compose messages. You generate diagnostics whenever the client records stability events. You optionally generate safety artefacts when you block or report. Technical correlators may accompany diagnostics so engineers can separate one broken handset from a million healthy ones.

We do not sell your personal data or sensitive user data.

III. Legal bases (EEA / UK)

Where you fall under GDPR or UK GDPR, we articulate: performance of steps you request (and, where applicable, the digital service contract) for communications payloads; legitimate interests—balanced and documented—for integrity analytics; legal obligation where a statute compels retention; consent when a discrete control requires it and you may withdraw where feasible.

IV. Android permissions and foreground posture

Savorly is a warm-toned cooking community and memory log. Three runtime permission constants appear in the manifest, each scoped to specific in-app gestures:

  1. Camera — android.permission.CAMERA — invoked when you shoot a cooking moment from the “Memory” composer (Take Photo / Record Video) or attach a screenshot to a feedback ticket. Declining suppresses live-capture surfaces only.
  2. Microphone — android.permission.RECORD_AUDIO — invoked when you record the audio track of a Memory video, or attach a ≤60-second voice note inside a feedback submission. Declining produces silent videos and disables the voice-feedback path.
  3. Photos / videos read — READ_MEDIA_IMAGES / READ_MEDIA_VIDEO on API 33+ (or READ_EXTERNAL_STORAGE on prior Android releases) — invoked when you import existing footage into a Memory post or attach up to 3 photos to a feedback ticket. Declining disables gallery selection; live capture remains.

Savorly does not request gallery-write, contacts, calendar, location, SMS, or call-log permissions for this build. Each prompt tracks an explicit gesture; we do not describe these channels as covert always-on surveillance feeds.

V. “Device ID” inside diagnostics

Questionnaires may use the label “Device ID.” In practice we mean installation-scoped or device-scoped tokens surfaced to diagnostic SDKs. Purposes: crash deduplication, reliability, fraud signals. Not sold; not used to stock an ad exchange.

VI. Recipients

Hosting/CDN entities, moderation processors, analytics/crash vendors—each under data processing terms that forbid independent marketing exploitation.

VII. International hosting

Servers may sit abroad; SCCs / UK IDTA modules backstop transfers lacking adequacy.

VIII. Retention logic

Routing buffers clear quickly; chat persists per schedule; diagnostics roll; safety cases may extend for investigations.

IX. Security measures

Access control, encryption in transit where stacks allow, monitoring. Incidents crossing legal thresholds trigger notices when required.

X. Your rights (enumerated)

  1. You may request access to personal data we hold about your usage footprint.
  2. You may request rectification of inaccurate personal data.
  3. You may request erasure where law permits.
  4. You may request restriction or object where law provides grounds.
  5. You may request portability where technically feasible without disproportionate effort.
  6. You may lodge a complaint with a supervisory authority.

Channel: info@lumutrading.com. Because you lack an account key, we may request contextual verification. We target substantive answers within fifteen business days once satisfied.

XI. United States disclosures (summary)

California residents may email with subject “California Privacy Request.” Virginia residents may use VCDPA-labelled subjects. We do not sell personal data or operate cross-context behavioral ads for this app; pathways exist for disagreement.

XII. Opt-out mail merge strings

Use “Opt-Out of Sale/Sharing Request” or “Opt-Out of Targeted Advertising” in the subject when you wish to exercise those categories even if our stance is that they do not apply.

XIII. Children

Not directed to persons under eighteen.

XIV. Supplement — retention principles without login credentials

Without a dashboard key, retention questions become category questions. Ask us; we explain what remains and why.

XV. Amendments

We revise this statement; the publication line updates; material changes may also surface in-app.

XVI. Technical dependencies

Android frameworks, optional Play services, RTC infrastructure, moderation interfaces, diagnostic SDKs—no broader footprint.