Privacy Policy

Operator: Hangzhou Liansu Technology Co., Ltd. (“we”, “us”, or “WinTalk”)

1. Introduction

This Privacy Policy explains how we collect, use, store, share, and protect your personal data when you use WinTalk instant messaging services (the “Services”), including clients on all supported platforms and related web features. “You” means a user of the Services. Read this Policy together with our Terms of Service.

1.1 Privacy principles

• We do not use chat content for ads. We do not use your private or group chat content or contact relationships to show ads, and we do not sell your data for that purpose.
• We only store what the service needs for WinTalk to work as a secure, usable messaging product.
• Location is opt-in. We obtain precise location and reverse-geocode it only when you choose Send location. Opening a chat or viewing someone else’s location does not trigger reverse geocoding.
• No ad tracking profiles. We do not integrate advertising analytics SDKs and we do not use ATT-style advertising tracking.

1.2 Consent and access

By using the Services, you acknowledge that you have read and understood this Policy. When registering, you must agree to the Terms of Service and this Privacy Policy. You can reopen this Policy and the Third-Party Sharing List anytime under Me → About.

2. What personal data we use

2.1 Account and basic profile

You typically sign up or sign in with an email (or similar first-party identity) and a password. We store a password hash or equivalent—not plaintext. After you create an account we assign an account identifier and may store nickname, avatar, and other profile fields you edit. We do not require your nickname to be your real name, and we do not collect gender or interest preferences for profiling. You may enable MFA (e.g. TOTP, trusted devices, backup email); we store related binding status.

2.2 Email and verification codes

Login, registration, and some security actions send a one-time password (OTP) by email. That address is used only for identity verification and security notices—not marketing. OTPs are delivered by our servers through an email channel.

2.3 Your messages and media

WinTalk provides cloud-synced conversations so you can read history across devices. We process text, images, video, voice notes, files and folders, location messages, and replies/quotes/system notices. Media is uploaded to object storage via server pre-signed URLs (vendor depends on deployment; see the third-party list). Messages may also be stored in a local database on your device.

Note: Cloud messages use encrypted channels (e.g. HTTPS), but the Services do not offer end-to-end “secret chat” where only the two parties hold keys and the server cannot read content. Do not assume that servers or node operators can never access plaintext cloud messages. WinTalk does not provide voice or video calling.

2.4 Devices and push

To maintain sessions, trusted-device lists, and multi-device features, we may process device identifiers, device name, platform, and app version. For offline notifications: iOS uses APNs and device push tokens; other clients may use Firebase Cloud Messaging when configured (not initialized until properly configured). You can turn off notifications in system settings.

2.5 Location data

If you actively send a location: we use system location for precise coordinates (or a map pick); the client may call OpenStreetMap Nominatim for an address title/description; coordinates and text sync as a location message. We do not call Nominatim merely because you opened a chat or viewed someone’s location; we do not track movements continuously in the background; we do not include account id, nickname, or chat body in reverse-geocode requests. Requests may include coordinates, client IP, User-Agent, and language.

2.6 Translation (when you request it)

When you actively translate a message, the source text of that message and the target language are forwarded by our servers to Alibaba Cloud Machine Translation (provided by Alibaba Cloud) to generate a translation for you. This is processing and third-party sharing of user content, and it happens only when you tap translate; we do not bulk-send your full chat history to the translation service for this feature. Our servers may cache translations to reduce repeat calls. If you never translate, we do not call the engine for that reason. Translation requests do not include passwords or OTPs, and translations are not used for advertising or profiling. Some node deployments may configure an alternate translation provider; the provider actually used is listed in the Third-Party Sharing List.

2.7 Operational logs and support

Clients and servers may log API errors and sync status for troubleshooting. From About, you may voluntarily upload logs so support can help.

2.8 Crash and diagnostics

On mobile, in production (non-Debug) builds with Firebase Crashlytics configured, reports may include crash stacks, device info, and an account key for correlation. Chat bodies, passwords, OTPs, address books, and phone numbers must not be attached to crash reports. Desktop crash dumps are outside this Crashlytics scope.

2.9 What we do not collect (summary)

• We do not read the device system contacts book (in-app “Contacts” means friends/groups, not the phone address book);
• We do not use chat content or contact relationships for ad targeting;
• We do not sell personal data.

3. System permissions

Permissions are requested when needed. Denying a permission only affects features that need it. You can manage these anytime in system settings.

4. How we protect and store data

4.1 Transport and access control

Client–server traffic uses encrypted transport (HTTPS, etc.). Credentials are stored as hashes or equivalent. Access to production data is restricted by operations and access control.

4.2 Storage location

Primary database and object storage are hosted in Singapore, US East, US West, the Middle East, Japan, or Europe, depending on node/deployment configuration. Some third parties used for features (Nominatim, map tiles, email, Firebase, etc.) may run in other countries or regions—see Section 6 and the Third-Party Sharing List.

4.3 Nodes and spaces

WinTalk can connect to nodes (spaces) run by organizations or individuals. Messages and media may be stored and synced under that node’s policies. Node operators handle data on their nodes under their own rules and applicable law. This Policy covers WinTalk clients and the platform we operate.

4.4 No over-claims

We take reasonable technical and organizational measures, but no internet service is perfectly secure. Keep passwords and OTPs safe, and sign out on shared devices.

5. How we use information

• Provide the Services: messaging, friends and groups, multi-device login, files and location messages, profiles, and sync across your devices.
• Safety and abuse prevention: account verification, MFA, trusted devices, unusual-login protection; complaints, reports, and security incidents; legal obligations where required.
• Notifications: deliver message alerts via system push when you grant notification permission.
• Features you trigger: translation, sending location, log upload, feedback—processed when you use them.
• Stability improvements: when Section 2.8 conditions are met, use crash reports to diagnose crashes and improve quality.
• No ads based on chat content: we do not target ads from chat content or friend relationships, and we do not sell the data described here for advertising.

6. Third-party sharing and cross-border transfers

To fulfill Section 5, we may share necessary data with third parties or have our servers call them, including maps and reverse geocoding, map tiles, system push (APNs; FCM on other clients is planned), email for verification codes, Alibaba Cloud Machine Translation (when you actively translate a message, we forward the source text and target language), object storage, and crash reporting (Crashlytics). Names, fields, scenarios, and status are authoritative in the Third-Party Sharing List.

We share personal data with third parties only as needed to fulfill the purposes in this Policy, and we require those third parties to provide protection of personal data that is no less protective than this Policy; specific parties, scenarios, and fields are listed in the Third-Party Sharing List.

Some third-party servers may be outside Singapore, US East, US West, the Middle East, Japan, and Europe. Using those features (e.g. send location, receive email OTPs, load maps) may transfer related data there. Third parties keep their own logs under their policies; we usually cannot delete records already on their servers. You can limit some processing by not using a feature, revoking permissions, or deleting your account.

7. Retention and account deletion

7.1 Retention

• Account and messages: while you use the Services and until deletion completes; afterward we delete or anonymize server-side account data per product rules. Local databases may remain until you uninstall or clear app data.
• Location messages: retained as message content, same as other messages.
• OTP email: short-lived for verification; retention follows email channel configuration.
• Crash reports: per Firebase (or similar) project settings.

7.2 Delete account

In-app: Account & security → Delete account. You must accept the Account Deletion Notice. After you submit, the account enters a deletion cooling period (default 30 days, subject to server config). Completing a full sign-in during that period can restore the account if it is not banned. After full deletion, self-service restore is unavailable. Pre-checks may fail for reasons such as an untransferred super-admin role, remaining nodes, or a ban. After full deletion we stop providing the Services and delete or anonymize account data in our control; third-party logs already created may not be erasable by us. Other people’s devices may still keep local copies of messages.

8. Your rights

• Access and correct profile data (edit profile, change email, etc.);
• Manage permissions in system settings; turning them off only affects related features (e.g. no GPS auto-pin; you may still pick a map point, which may still reverse-geocode);
• Delete your account (Section 7);
• Make other requests via the contact emails below under applicable law.

9. Minors and age limit

The Services are only for users aged 16 and over. Do not register or use WinTalk if you are under 16. If we learn that personal data was collected from someone under 16, we will delete it promptly and restrict the account.

10. Policy updates

We may update this Policy. Material changes will be announced in-app, via About, and/or by showing consent again. If re-consent is required before you continue, the product flow will guide you.

11. Contact us

Operator: Hangzhou Liansu Technology Co., Ltd.

Privacy email: [email protected]

Backup email: [email protected]

For product use and technical support, see Technical Support.

Appendix: App store data labels

For app store privacy questionnaires. Store checkboxes follow legal review at release time.

Not used for third-party ads; not sold.