Taleglide | Privacy Policy

Current as of: November 4, 2026

Taleglide (package name: com.taleglide.vidmagic, "Taleglide" or "the App" from here on) is published by SKY VICTORY MANAGEMENT LIMITED. This page works like the log kept at an observatory: entry by entry, it records what information drifts into the App's instruments, why each reading is taken, and the safeguards set around it.

If you keep the App installed, or open it again once this page has been redrawn, that counts as accepting what is written here. Should the arrangement fail to suit you, removing the App from your device ends it.

1. What the Instruments Register

Begin with the plainest fact: almost everything Taleglide works with stays on the phone or tablet in your hand.

Readings never taken:

• No account counter: the App operates no sign-up desk of any kind. A real name, a postal address, a phone number — not one of these is asked for. First launch simply opens an anonymous guest session on the device, and generation can start immediately.
• No archive of your finished pieces: the images and videos Taleglide renders for you are not given permanent shelving on our side, and nothing of yours is passed onward from there.
• Your offline self stays out of view: nothing that could tie the device to a particular human being — a name, a street, an inbox — is hunted for or noted down.

Readings the App does take:

• A blind device token: the service needs a steady, impersonal way of telling one handset from the next. It is computed on the device itself: the ANDROID_ID reading is joined with the App's package name and passed through a one-way MD5 calculation, giving a token that reveals nothing about whoever owns the device. Should ANDROID_ID be unavailable, a random UUID kept in local storage takes the shift. A Firebase installation identifier travels alongside as one more anonymous install label — and, on installs identified as coming from a direct Meta campaign, a marker minted by the Facebook SDK joins as well (its post is described in Section 7).
• The guest session: anchored to that token from the very first opening, the session holds no password, no username, no credential of any description. It carries your working record and similar conveniences while grasping nothing that would identify you personally.
• Neutral hardware readings: model, operating-system build, screen measurements, language, time zone, and neighbours of that family — colourless technical facts that help the App behave across the wide range of Android hardware.
• Footprints of use: which functions get visited and how often — the signs that tell us where mending and new capability belong, and which parts of the App people actually settle in.
• The advertising marker (GAID): the Google Advertising ID may be consulted for advertising attribution. The instant "Limit Ad Tracking" or "Opt out of Ads Personalization" is switched on, the consultation stops entirely, and the system settings can have the ID reissued whenever you say so.
• Sound caught by the recorder: open the built-in recorder and whatever the microphone gathers while that take runs travels to us — collected only for as long as the take stands open, and bound for a single destination: custom audio (a stretch of background music, for example) on the video you placed the order for. Section 3 keeps the detail.
• Push coordinates: notification tokens let service messages (a generation reaching its finish, say) find your device. You may silence them for good; nothing the App genuinely needs rests on them.

2. Material You Send Upward

Certain creation routes need raw material from your side — a photograph, a clip. Any file of that sort is handled this way:

• Why it climbs at all: your file is the substance the computation feeds on — the finished image or video grows from precisely what you handed over. Its ascent to our servers rides an encrypted connection.
• A brief stay: the upload and the piece it yields remain on our servers only for as long as the job stands open; when the job closes, the system sweeps both away.
• Nothing shelved in secret: no copy of your material outlasts the job, and no identifying particulars ride attached to it.

3. The Five-Second Voice Take

An optional recorder sits inside Taleglide's creation flow. It accepts a single take (five seconds at the most) whose sole destination is custom audio — background music among the possibilities — for an AI video:

• The permission belongs to the feature: the microphone question arrives at runtime, at the exact moment the recorder opens; turning it down then, or withdrawing it later through system settings, stays entirely in your hands.
• What fences a take in: your own finger sets it going; the App must stand in the foreground; and one take is the whole of what is ever gathered. Listening from the background, under any disguise, is nothing this App does.
• Where a take may head: exactly one terminus — the audio dressing of the video under generation.
• The climb out: the moment you accept a take, the file boards an encrypted channel and is spent by the generation.
• Its time on the server: a copy holds only through the length of processing and is gone once processing closes.
• No voiceprinting: takes never meet speech recognition, speaker identification, or any effort of that biometric sort.
• While a take runs: the recording waits in a local cache; clearing App data through system settings disposes of it.

4. Faces Inside Your Own Frames

When material you upload carries human faces, Taleglide derives a narrow band of facial signals to drive its AI image and video faculties:

• The signals themselves: eye, nose, and mouth geometry (facial landmarks), along with measures such as contour and proportion — drawn from nothing beyond media you yourself chose to upload.
• The office they hold: composing personalized, high-grade imagery; keeping visual effects anchored on their subject; and raising the fidelity of what comes back to you.
• Their working span: all processing happens on encrypted servers and serves nothing past your result; once the result is delivered, the data clears itself — as a rule within 24 hours.
• Handed to outsiders: never. Face data is at no point passed to outside parties.

5. The Ends Each Reading Serves

The categories set out above are put toward these purposes:

• Running the service: providing and keeping up the faculties you opened the App for.
• Service messages: word of your generation jobs and of App releases.
• Improvement: usage footprints steer the repairs, refinements, and new capability we deliver.
• Defence: keeping fraud, abuse, and unearned reach at arm's length.
• Attribution & measurement: tracing the harbour each user embarked from and judging how campaigns run.

Your information is never sold, leased, or passed to third parties for marketing ends of their own.

6. Payments and the Record They Leave

Wherever money moves inside the App:

• Traces of dealings: purchase tokens, product identifiers, order references, and subscription standing go on the record so that whatever you paid for can be honoured and delivered.
• The ledger is Google's: every charge is conducted by Google Play Billing. Cards, billing avenues, and the rest of the financial machinery never enter our keeping — that ground lies under Google's own privacy policy.
• Standing of a plan: whether a plan runs, has lapsed, or was cancelled is tracked so premium faculties switch at their proper moments.
• How long the records hold: transaction traces stay on file to the extent delivery duties, statutes, and dispute handling call for.

7. Services Stationed Outside the Walls

Taleglide relies on these outside services to run, measure, and deliver:

• Google Play Services: distribution, in-app purchasing, and subscription administration all move along this channel; whatever Google gathers answers to Google's own privacy policy.
• Google Play Billing: purchases and plans cross it; purchase tokens and transaction traces ride the Google Play rails.
• Firebase Analytics: nameless usage statistics and interaction patterns; device facts, usage matter, and anonymous markers may be gathered. See Firebase Privacy Information.
• Firebase Installations: the mint striking the unique, nameless installation identifier the service leans on.
• Firebase Cloud Messaging (FCM): the conduit beneath the App's self-built push line (generation standing, service notices). Device settings hush notifications whenever you please. See Firebase Privacy Information.
• Google Play Install Referrer: the lane through which the App learns how it arrived on the device (install attribution); attribution and measurement are its only occupations.
• Google Advertising ID: serves advertising attribution and nothing else — and goes unread from the moment "Limit Ad Tracking" is thrown.
• Facebook SDK (Meta): holds one commission only: counting installs that trace back to our direct Meta (Facebook) ad campaigns. As shipped it is off and stays wholly dormant — nothing initializes, nothing reports — unless an install is ruled direct-campaign traffic. Only then does it pass Meta the install/activation event together with a nameless device marker; our backend receives the same marker and sets it against Meta's server-side Conversions API to weigh conversions. Purchases travel the server lane exclusively. Facebook sign-in, sharing, and deep links play no part in the App. Details: Meta Privacy Policy.

Every service on that roll publishes a privacy policy of its own for whatever it handles — worth reading.

8. Tracing an Install Back to Its Origin

To weigh our marketing and to sharpen the service, the following may be brought together:

• Attribution material: install-referrer payloads, advertising identifiers, and anonymous device fingerprints (model, maker, resolution, language, time zone, carrier, network class) kept for our marketing attribution.
• Direct-campaign counting (Meta): where an install is classed as direct Meta campaign traffic, the Facebook SDK may rise and hand Meta the install/activation event plus a nameless device marker for conversion measurement; under any other verdict it sleeps the whole way through.
• Analytics material: nameless usage statistics, feature-interaction counts, and performance figures, all carried by Firebase Analytics.
• IP address: for attribution ends your IP may be noted in passing; pinning a person to it was never the brief.
• The way out: Settings > Google > Ads offers "Opt out of Ads Personalization", and your advertising ID can be struck and reissued at your word.

9. Nothing Sold to Other Traders

Selling, bartering, or otherwise passing personal data to third parties for their marketing is no trade conducted here. Anonymized, rolled-up material may reach the services named in Section 7, for the ends this policy states and no others. Disclosure also occurs where statute compels it or where defending our rights calls for it.

10. Locks on the Observatory Doors

The following provisions keep watch over your data:

• Every stage of the crossing runs under encryption (HTTPS)
• Storage at work on our servers keeps its contents encrypted
• Access vetting and security rounds mind the doors

No lock yet forged answers every pick. Reasonable measures stand posted as they should be, yet whatever crosses a network carries a residue of hazard.

11. How Long Each Reading Is Held

Each category waits precisely as long as the ends above demand of it:

• Uploaded media, voice takes, face data: cleared without prompting when processing ends — typically within 24 hours.
• Device tokens and session matter: carried on the books for as long as the App remains aboard your device.
• Transaction traces: kept as far as statutes and dispute handling call for.
• Analytics matter: stored in aggregate, anonymized form.

12. Children Outside the Field of View

Taleglide addresses nobody under 13, and no such person's information is gathered knowingly. Should you judge that a child's data has reached us, write to the address below and it will be struck without delay.

13. The Controls That Stay With You

Over your own data, these controls remain in your grip:

• Inspection & correction: request a view of what we hold; call for amendments or erasure.
• Erasure: one message to the address below sets the removal in motion. Since finished images, videos, and personal information never sit in our lasting custody, there is ordinarily little to strike — the weight of your data rests on the device itself.
• Tracking cut: cap ad tracking from system settings, and have the advertising ID struck and reissued at any hour.
• Notification settings: pushes answer your on/off word at every turn.
• Subscription controls: plans are looked after or called off inside your Google Play Store account.
• Uninstall: see the App off whenever it suits — gathering halts and the local store departs in the same boat.

14. Skies the Work Happens Under

Processing may occur on servers stationed outside your home country. Wherever your data travels, fitting safeguards ride with it.

15. When This Page Is Redrawn

As the operation, the faculties, or the law shifts, this Privacy Policy shifts in step; every shift advances the "Current as of" line at the top. An occasional glance keeps you current.

16. The Keeper's Address

Questions or objections about this policy, or about the handling of your data? Put them here:

Registered entity: SKY VICTORY MANAGEMENT LIMITED

Registered office: Rm 1809, 18/F, ETON TWR, 8 HYSAN AVE, Causeway Bay, Hong Kong

Email: ralphnguyen19980@gmail.com