Terms & privacy,
in plain sight.

Welcome

Welcome to "喜劳转扩 MeQR" ("MeQR"). MeQR is developed and operated by Li Zhenghang (Lucas Li), an individual developer also known as "重生Rebirth" ("we", "our", or "us"). You should read and agree to these Terms before using MeQR's basic features. Online exchange codes are also covered by these Terms. Multi-device synchronization additionally requires you to read and agree to the MeQR Privacy Policy because it stores selected information on the synchronization service. MeQR is not directed to children under 14. Minors should use MeQR with the supervision of a guardian.

Service and limits

MeQR creates, saves, displays, and shares personal QR cards. Multi-device sync lets you use one card on several of your own phones. A cloud card can have up to five devices, including the owner. Version 1 requires a manual "Sync now" action and has no background real-time sync or local-network transfer. Public exchange codes cannot be used as sync credentials.

Sync covers card text, QR content, Tags, avatar, background, and banner. An avatar may be up to 1 MB. A background and banner may each be up to 5 MB. The service validates image formats and limits total temporary image storage and trial profiles. It may reject a create, upload, or update after a limit is reached.

Pairing and management

Give a pairing code only to the intended device. It expires after 10 minutes. The owner should check the device name before approval. Members can read and edit a bound card. The owner can approve devices, remove members, and delete a cloud card. A device name is for review only and is not identity verification.

There is currently no phone or email recovery, owner transfer, or remote deletion of a member's local copy. Before deleting the app, changing phones, or clearing an owner credential, handle the cloud card and its bindings. A card backup does not contain sync credentials.

Edits and conflicts

Tap "Sync now" after editing, then sync on the other device. Joining creates a new local card and does not overwrite an existing card by name. If both devices edit a card, the app asks you to keep the local version or use the cloud version. It does not merge edits automatically or provide complete history recovery. Export a backup before resolving a conflict and retry after a network interruption.

Content and acceptable use

Upload only material and images that you have the right to use and store. Do not sync another person's private material without permission, distribute illegal content, infringe rights, or try to read another person's card.

Do not guess, steal, or transfer device credentials. Do not bypass approval, occupy capacity in bulk, send repeated invalid requests, or damage the service. Request rate, device count, and storage limits apply.

Before creating an online exchange code, confirm that you are willing to share its contents. Do not post a non-public code publicly or save, distribute, or alter another person's exchanged information without permission. Exchange codes cannot bypass sync approval or prove ownership of a cloud card.

Stopping sync and changes

A member can remove its own binding. When the owner deletes a cloud card, all devices stop syncing it. Local cards, backups, and already shared information remain with their holders. Uninstalling the app, clearing a local credential, or cancelling a request does not delete a cloud card; delete it from the sync screen.

Maintenance, network failures, and capacity limits may make sync temporarily unavailable. Local cards remain usable. Keep your own backups. If a rule affects processing, device permissions, or user rights, we will explain it in the app or on the website and ask for renewed confirmation where required.

For questions, privacy requests, or device-removal requests, contact meqrsupport@icloud.com. These Terms do not exclude rights provided by law or responsibilities that cannot lawfully be excluded. These Terms are governed by the laws of the People's Republic of China. Disputes arising from or related to these Terms will first be resolved through friendly negotiation; if negotiation fails, either party may bring an action before a people's court with jurisdiction in accordance with law. If any provision of these Terms is held invalid or unenforceable, the remaining provisions remain in full force and effect. These Terms apply to your use of the app's features. If these Terms conflict with a specific statement (such as the MeQR Privacy Policy or exchange-code instructions) on the same matter, the specific statement governs for that feature.

Welcome

"喜劳转扩 MeQR" ("MeQR") is developed and operated by Li Zhenghang (Lucas Li), an individual developer also known as "重生Rebirth" ("we", "our", or "us"). MeQR is local first. We process information when you actively use a feature that needs it. MeQR is not directed to children under 14. We do not knowingly collect personal information from children; if we learn that we have, we will delete it as required by law. Minors should use MeQR with the supervision of a guardian.

Local information and permissions

Card names, introductions, avatars, backgrounds, banners, QR content, platform information, Tags, appearance settings, and encounter records are stored on your device by default. The app does not read your photo library in the background or upload photos that you did not select. Camera and photo access are used when you actively scan, import, select, or save content. MeQR has no advertising SDK, third-party analytics SDK, or cross-app or cross-site tracking.

Online exchange codes

When you create an online exchange code, the app uploads the information you choose to share. This may include your name, full introduction, avatar, and the names and QR content of selected platforms. The code may also contain a shorter offline fallback text. Anyone who holds the code or link can access the information in it, so share it only with those you intend to tell. Exchange-code credentials are separate from synchronization credentials.

Multi-device synchronization

You turn synchronization on yourself. The selected card can include its name, full introduction, pass subtitle, platform names, QR content, template, Tags, Tag colors and weights, appearance settings, avatar, background, and banner. A joining device downloads this information.

Synchronization does not include other cards, encounter or activity records, the short offline exchange-code settings, your whole photo library, or independent widget settings. The first version uses a manual "Sync now" action. It has no background real-time sync or local-network transfer.

The service stores a profile ID, device ID, device name, owner/member role, creation time, revision, and hashes used to verify credentials and pairing codes. The device name comes from the iOS device name or the Android manufacturer and model, to help you check a pairing request. iOS stores its credential in Keychain. Android encrypts it with the system Keystore in an application directory excluded from system backup. Credentials are not included in public exchange codes or exported card backups. Pairing does not require a phone number, email address, or password. A pairing code expires after 10 minutes, and the owner must approve a new device. An approved device then keeps using its own credential and does not depend on the pairing code remaining valid.

Server and security

The synchronization service runs on an Alibaba Cloud server in Shanghai, mainland China. Text and images are transferred separately, and the service uses HTTPS throughout. A valid synchronization credential is required to download an image.

Synchronization is not end-to-end encrypted. The server must store and read the card and images, so authorized server operators may be able to access them. Do not upload passwords, verification codes, identity documents, or unrelated sensitive material. If a personal-information security incident occurs (such as leakage, alteration, or loss), we will take remedial measures immediately and, in accordance with law, notify you and report to the competent authorities.

The service processes source IP addresses for rate limiting, and this rate-limit data is held in process memory. The endpoint does not keep routine access logs, and application logs do not record pairing codes, device credentials, or card contents. Host and reverse-proxy errors may be logged. Server logs are rotated daily (by logrotate), keeping up to 14 rotated files and skipping empty logs. This does not promise deletion after a fixed number of days.

Retention, deletion, and your choices

A cloud card remains until its owner deletes it. The service stores the current revision, not a complete edit history. The owner can remove a member device. The removed device cannot access the cloud card, but its downloaded local copy is not remotely erased. A member can remove its own binding.

Deleting a cloud card removes the card, related images, device bindings, and pairing requests. Existing local copies, exports, and information already shared through exchange codes are not affected. Clearing a local credential, deleting the app, or cancelling a request does not delete the cloud card. Images that were uploaded but are no longer referenced by the current card enter a temporary retention period: on the next upload or update, the service cleans up old images that are more than one hour old and no longer referenced; if there is no new request, such images may remain until the cloud card is deleted. Expired, unconfirmed pairing requests are cleaned up when a new pairing code is generated.

This service runs on Alibaba Cloud. Even after you delete a cloud card, disk snapshots or cloud backup copies on the platform may persist, with no fixed deletion schedule at this time. We cannot promise complete erasure of all backup copies by a specific date. If you request deletion, we will cooperate to the extent permitted by law, subject to the platform's backup mechanisms.

You may leave synchronization off and continue using local features. To view, copy, or export your card data, correct a card, remove a binding, delete a cloud card, or make a privacy request, contact meqrsupport@icloud.com. If you lose your owner credential, contact this address and describe the data you need handled. Do not send credentials or pairing codes in email or public tickets. A public exchange code does not prove ownership of a synced card and cannot be used by itself to restore sync management.

Changes and governing law

If processing, device permissions, or user rights change, we will explain the change in the app or on the website and request renewed consent where required. This Policy is governed by the laws of the People's Republic of China. Disputes arising from or related to this Policy will first be resolved through friendly negotiation; if negotiation fails, either party may bring an action before a people's court with jurisdiction in accordance with law. If any provision of this Policy is held invalid or unenforceable, the remaining provisions remain in full force and effect. This Policy, together with the MeQR Terms of Use, constitutes the agreement between you and us regarding the processing of information.