Spellift Privacy Policy

Public beta · 19 November 2026

Spellift is operated by Yongming Mo. To ask a privacy question or request access, correction or deletion, email yomingmok@gmail.com.

Data we handle and why

Where processing happens and who receives data

Access traffic is relayed through Tokyo, Japan; main data processing and storage take place in Chengdu, China. Tencent Cloud carries service traffic. Google supports recovery email and delivers Android notifications via Firebase Cloud Messaging. Browser push providers deliver web notifications. Cloudflare may relay calls. Other chat participants receive the content you send them.

Earlier beta versions could use external AI services as described in the notices in effect at the time.

The app connects to Spellift over encrypted connections. The service requires account verification for private account actions and restricts staff access to reported evidence by role.

We use the Google sign-in data we receive for authentication and account management. The nickname you confirm is part of your Spellift profile and can identify you to contacts. Google processes authorization requests under its own policies.

Retention and deletion

We keep data as needed to provide and secure the beta and handle requests. Retention varies by data and feature. You can delete your Spellift account on the web or use Delete account in the app. Other people retain their own copies of conversations. The hold on selected evidence is lifted when a report closes; if it remains open, that hold lasts at most 90 days from submission.

The Google identity link is stored with your account and removed when the account is deleted. Google access and refresh tokens are not stored persistently. Short-lived OAuth verification materials are for single-use verification and expire. You can revoke authorization in your Google Account connections settings; deleting a Spellift account still uses the account deletion process above.

Account merging requires verification of both accounts and your explicit confirmation. It keeps contacts and chat histories from both accounts; duplicate settings use the Google target account's values with priority. The source account can no longer sign in. Necessary retired-account security marks may remain to prevent old credentials from being reused. Deleting the target account removes associated private data; other people's legitimate conversation copies remain subject to the retention rules above.