中文

Yaypik Privacy Policy

Effective date: November 18, 2026

Yaypik (the "App") is developed and operated by Shigong Liu (individual developer) ("we", "us"). This policy explains what we collect, how we use it, and your choices.

1. Our principles

  • Photos are processed on your device. Beauty, retouch, blemish removal, collage, cutout, background replacement, outpainting, body shaping, ID photos, color analysis and hairstyle suggestions run on your iPhone; those photos are not uploaded. (On Android and the web, Smart Remove, Expand and the face-shape and hair-length analysis in hairstyle suggestions use cloud AI; see below.)
  • We ask before uploading. A few AI features need the cloud. Each asks for your consent the first time, and you can withdraw it at any time.
  • We do not sell your personal information and do not use your photos for advertising.
  • Ads only when you choose them. A rewarded video ad plays only when you tap "Watch ads for credits"; there are no banner or interstitial ads, and none at all with Pro or the one-time No Watermark · No Ads unlock.

2. Information we collect

Account (only if you sign in)

You can sign in with email, phone number, Google, Facebook or Apple. Through Google Firebase we store: user ID, display name, email, phone number (for phone sign-in), email verification status, sign-in methods, account creation and last sign-in/activity times, sign-in count, a sign-in log (method, time, app version, device model and iOS version), and your Pro subscription status and whether you bought the No Watermark · No Ads unlock. Most features work without an account.

Photos you send to AI features

With your consent, Real Hair Try-On, Professional Headshot, AI Makeup, AI Style Portraits, Photo Restoration, Skin Check and the color-test outfit preview, and on Android and the web also Smart Remove, Expand and the face-shape and hair-length analysis in hairstyle suggestions (on iPhone they run on the device), send the selected photo to Google's Gemini models (via Firebase AI Logic) to create the result. We do not keep these photos on our servers. Google processes them as a service provider under its own terms. You can withdraw consent in Settings › AI 功能与照片上传.

Print orders

To fulfill a print order we collect the photos to print, products and quantities, contact name, email, phone, shipping address (for delivery) or pickup store, and order amounts and status. Photos are uploaded to our Firebase storage only to produce and deliver your order. Payments are processed by Stripe; we never see your full card number. If you choose Walgreens store pickup, the photos and pickup contact are sent to Walgreens to print, and we also keep the order number, store, items, contact and pickup status on our server to follow up on the order. We track whether Walgreens orders are picked up to limit repeated no-shows: an order not collected long after it is ready (14 days by default), or cancelled by Walgreens, is recorded as not picked up; several of these within a period (90 days by default) pause printing on your account for a while (30 days by default) or turn it off until you contact us. These records are kept with the order and your account.

Location

Only when you use printing and allow location, to find nearby pickup stores and delivery options. We do not track your location in the background.

Photo printing is available only within the US. On iOS and Android, when you open printing (and again before you submit a print order if the last check is more than about 30 minutes old), we get your device's approximate location only to confirm that you are currently in the US. The location is turned into a country on your device and then discarded: coordinates are not stored and are not sent to us or to Walgreens; when an order goes through our server, only the result (a country code such as US) is sent with it for this check and is not stored. The web version does not access your location; it only reads your browser's time zone setting to confirm you are in the US.

Purchases, AI credits and invites

Pro subscriptions, AI credits and the one-time No Watermark · No Ads unlock can be bought through the Apple App Store, Google Play or our website (Stripe). To verify purchases, the App sends the Apple / Google purchase receipt to our server. We store your subscription status, start and expiry, purchase receipt IDs, whether you own the unlock, credit balance and usage/gift history (including gift recipients and notes), and records of free new-user credits, monthly Pro credits and credits earned by watching ads (including daily view counts); we never see your full payment details. Pro members receive free AI credits each 30-day cycle, spent like purchased credits; free and purchased credits never expire. When you use an invite code we store the invite relationship and the Pro days or AI credits earned. To prevent repeat new-user rewards, we keep one-way hashes of your email, phone number and sign-in account IDs (they cannot be turned back into the originals), and these hashes remain after account deletion.

Skin Check cloud saving

If you sign in and turn on Save to Cloud, your Skin Check photos, spot names, the symptoms you select and the results are saved to your account (Firebase), accessible only to you, so you can view and compare changes across devices. You can turn it off, delete a check or a whole spot at any time, and it is deleted when you delete your account.

Holiday card links

Holiday cards are made on your device and are not uploaded. Only when you choose Share as link does the App upload that card's video and cover image to our Firebase storage and create a random, hard-to-guess link (such as https://picstory-22465.web.app/c/…).

  • Kept for 90 days: the card's video, cover image and the share record (your account ID, the template and occasion, when it was shared and expires, the view count, and the invite code you chose to include) are kept for 90 days and then deleted automatically.
  • Anyone with the link can view it: anyone who has the link can watch the card without signing in, including people the link is forwarded to. Card pages are not indexed by search engines and we never list shared cards publicly. Don't share photos you wouldn't want others to see.
  • Surprise photo: if you add a surprise photo to the card, sharing as a link uploads that photo separately and keeps it with the card for 90 days. People with the link see it only after they scratch or tap to open it on the page; it never appears in link previews.
  • You can delete it at any time: when you delete a shared card in the App, the link stops working right away and the video, cover image and surprise photo are deleted. Shared cards are also deleted when you delete your account.
  • When someone opens the link, our server counts the view (without identifying the viewer); link previews (Messages, WhatsApp, Facebook and others) fetch the cover image and video.
  • The page's "Make your own" and app store buttons go through our server first; we only count taps per day (without identifying who tapped). The link to the website carries the card's ID, and the Google Play link carries the card's ID and the sender's invite code through Google Play's install referrer, so we can count how many new users a card brings (see "Card and invite sources" under Usage statistics).

Cloud photo sources

When you import from Google Photos, Dropbox, Box or OneDrive, we read only the photos you choose. Access tokens are stored in your device Keychain and are not sent to our servers (Box sign-in exchanges a code through our cloud function without storing it).

Rewarded ads (Google AdMob, iOS and Android apps only)

If "Watch ads for credits" is available and you choose to watch, the App shows a rewarded video ad through Google AdMob. AdMob may collect device information, IP address, the advertising identifier (IDFA on iOS, advertising ID on Android) and ad interaction data to serve and measure ads and prevent fraud. On iOS you are asked for tracking permission (App Tracking Transparency) right before the first ad; if you decline, the App does not access the IDFA and you still get the reward. On Android you can reset or delete your advertising ID in Settings › Privacy › Ads. To grant the reward, AdMob sends a confirmation of the view (with your account ID and a request ID) to our server; we keep only daily view counts and credits earned. The website has no ads, and the App shows no ad entry once you have Pro or the unlock. AdMob handles data under Google's policies (https://policies.google.com/technologies/ads).

Data on your device

Recent works, skin check history (unless Save to Cloud is on), editing preferences and downloaded template images stay on your device. You can clear them in Settings › 存储空间 or by deleting the App.

Third-party SDKs

Google Firebase (Authentication, Firestore, Storage, Cloud Functions, AI Logic, and Crashlytics for crash reports in the iOS and Android apps, see Crash reports below); Google Sign-In, Facebook Login and Sign in with Apple (only when you use them; the Facebook SDK may collect device and usage information under Meta's policy); Stripe (print orders, web subscriptions and AI credits); Google Play Billing (Android subscriptions and AI credits); Walgreens (prints and in-store payment when you choose store pickup); Apple StoreKit (subscriptions, AI credits and the unlock); Google AdMob (only when you choose to watch a rewarded ad). Each handles data under its own privacy policy.

Usage statistics

To understand how the App is used (for example, how many people use each version, platform and language), the apps and the website send our server the following when they open (at most once a day), after you sign in or switch accounts, and after you change the App language: app version, device type and OS version (on the web, browser name and version), the App's display language, your device's language and region setting (such as en-US, US), and time zone. The server adds your sign-in method (such as email, Google or Apple, or guest when you are not signed in) from your sign-in credentials.

  • This is stored with your account ID (the latest values plus first and last seen times), and also counted per day into totals that contain no account IDs (such as daily active users per platform and language).
  • Install identifier: the iOS and Android apps create a random install identifier the first time they run (a random string, not a device serial number, IDFA, IDFV, Android ID, IMEI, MAC address or phone number), keep it on the device together with the time it was created (first install time), and send both with the information above. It is used only to count active devices and how long the App is used: we count daily use by this identifier (as a guest when you are not signed in) and keep, for that device, the latest values above, the first install time, the first and last time it was used and the number of days it was used (deleted after about 13 months without use). It is not linked to your identity unless you sign in; the first time you sign in, we record when that happened and link the identifier to your account, so we can measure how many guests go on to sign in. It is not used for advertising or to track you across apps or websites. On Android, uninstalling the App or clearing its data deletes it; on iOS it is kept in the device keychain and may carry over if you reinstall.
  • To prevent abuse, the server counts requests from signed-out devices per day and keeps only a salted, one-way hash of the IP address (it cannot be reversed and can no longer be matched to an IP after two days). We do not store the IP address itself or use it to determine your location.
  • We do not collect precise location: the region comes from the language and region setting on your device, not from GPS or your IP address.
  • Card shares: when you share a card as a file (choosing Messages, WhatsApp, Email, More and so on), the apps and the website send one share record: the share option you chose, the file format (video, GIF or image) and the card's holiday or occasion; a card shared as a link is recorded once by the server when the link is created. Records never include the card itself, your message or the recipients. We count these per day and keep, for each sender, a one-way hashed identifier (made from the account ID or install identifier) with the date of the latest share and that day's count, to count senders and prevent abuse (deleted after about 13 months).
  • Card and invite sources: if you reached the App or website through a card page, the QR code on a card or an invite link, the App or website sends the source type (card page, card QR code, invite link or invite code) and the card ID or invite code when you first use it or sign up. We record on your account or install identifier only the source type, the card's holiday or occasion and when it was recorded (not who sent it to you), and count new users per source per day to measure how many new users cards bring. The Android app reads Google Play's install referrer once after installation to get this; the website keeps the source in your browser's local storage for up to 30 days.
  • It is used only in aggregate to understand and improve the App, only administrators can view the totals, and it is not sold or used for advertising. When you delete your account, the statistics linked to it are deleted; the daily totals, which contain no account IDs, are kept.

Event pages and RSVPs (invitations)

Invitations are made on your device. Only when you choose Create event page do we store the event on our server and create a random, hard-to-guess link (such as https://picstory-22465.web.app/e/…) that the invitation's QR code points to.

  • Hosts (you, when you create an event): we store the event details you enter (title, date, time and time zone, venue and address, schedule, dress code, notes, the contact details you choose to show, reply settings), the event photos and invitation cover you upload, the guest names you add and their personal links, your account ID, and the invite code you choose to include.
  • Guests' replies: when a guest replies on the page, we store the name they enter, their answer (attending / not attending / maybe), the number of adults and the number of kids, the meal they choose, their note to the host, when they replied or changed it, and a random token for changing the reply (we keep only a hash of it). Guests don't need an account.
  • Who can see it: anyone with the link can open the event page, but the page never shows the guest list or anyone's reply; replies are visible only to the event's host in the App, who can also export them. Event pages are not indexed by search engines and we never list events publicly.
  • Abuse prevention: to limit spam, the server counts replies per network address and keeps only a salted, one-way hash of the IP address that changes every day (it cannot be reversed and can no longer be matched to an IP after about two days). We do not store the IP address itself or use it to determine location. Event pages carry no ads or third-party tracking.
  • How long: event pages, guest lists, all replies and event photos are deleted automatically 30 days after the event date, and immediately when the host deletes the event or their account. Guests who want their reply removed can ask the host or email support@yaypik.com.
  • Guest information belongs to people the host invited; hosts must use event pages only for genuine invitations. We do not sell this information, use it for advertising, or send guests any messages.
  • Send status and reminders: when you send invitations or reminders one by one from the App or the website, each message goes out from your own phone's Messages, your email or your share sheet; we never send them for you. We record only whether each guest was sent the invitation or a reminder, how and when, plus the reminder times and message templates you set for the event, to show your progress and remind you. Reminders reach you as local notifications on your device (a banner on the website), never the guests.

Guest groups

When signed in, you can save people you often invite as guest groups (such as "Family" or "Coworkers"), synced between your phones and the website, so you can add them to new events quickly.

  • What is stored: the group name and, for each member, the name, phone number, email address, note, expected party size (adults / kids) and message language that you enter or pick from your contacts.
  • Only the contacts you pick are uploaded: when importing from your contacts, only the name, phone number and email of the contacts you select are uploaded; we never read or upload your whole address book. On iPhone the system contact picker is used and the App needs no Contacts permission; on Android the App reads your contacts on the device, only after you allow it, so you can pick from them.
  • Purpose: only to help you prepare invitations and reminders, which you send yourself, one at a time, from your own Messages, email or share sheet. We never contact the people in your groups, never sell or share this information, never use it for advertising, and never use it to find or match other users.
  • Who can see it: only your account can view and change your groups; the data is accessible only through our server.
  • How long: groups don't expire. They are kept until you delete the member, the group or your account (deleted immediately). Guests you add to an event keep a copy in that event, which is deleted with the event (see Event pages and RSVPs above); deleting a group doesn't affect invitations already sent.
  • People in a group who want their information deleted can ask the host who added them, or email support@yaypik.com.

Crash reports (Firebase Crashlytics, iOS and Android apps only)

When the App crashes, it sends a crash report to us through Google's Firebase Crashlytics so we can find and fix the problem.

  • What it contains: the crash stack trace, device model, OS version, app version, the time of the crash, some device state at the time (such as orientation and free memory and storage), the App's display language, and a random identifier Crashlytics creates for this installation (to count crashes per installation).
  • What it doesn't contain: no photos or creations, no account ID, name, email, phone number or guest information. Crash reports are not linked to your account and are not used for advertising or to track you across apps.
  • On by default, off any time: crash reports are on for everyone, including guests who are not signed in. You can turn them off in Settings › Send crash reports; reports are then no longer sent and any reports not yet sent are deleted. The website does not collect crash reports.
  • How long: Google deletes crash reports after about 90 days. Crashlytics handles data under Google's privacy terms (https://firebase.google.com/support/privacy).

3. How we use information

To provide sign-in, account linking and Pro features; to produce the AI results you request; to process, produce and deliver print orders and send order notices; to keep accounts secure, fix problems and prevent abuse; to understand usage of the App in aggregate (see Usage statistics above); and to comply with law.

4. Sharing

We share information only with the service providers above to deliver the feature you use, with your consent, when required by law, or to protect the safety and rights of you, other users or the public.

5. Storage, retention and security

Data is stored with Google Firebase in the United States. Account data is kept while your account exists and deleted when you delete your account. Deleting your account removes the account and the data linked to it (profile, sign-in history, AI credits and their history, invite records, Skin Check cloud records, invitation events and guest groups, cards shared as a link, linked usage statistics). These records are kept without your account ID or contact details: Walgreens print orders for 180 days and paid print orders until 3 years after the order (support and disputes); purchase and subscription records for up to 7 years (legal and accounting requirements); and, only if printing was restricted on your account after repeated no-shows, one-way hashes of your email, phone number and sign-in IDs for 90 days so the restriction can't be avoided with a new account. A web Pro subscription is cancelled when you delete your account; App Store or Google Play subscriptions must be cancelled in the store. Details: https://yaypik.com/delete-account . Print order records are kept up to 3 years for fulfillment, support and accounting; order photos are deleted within 90 days after the order is completed. Cards shared as a link (video, cover image, surprise photo and share record) are deleted automatically after 90 days, or earlier when you delete them. Invitation event pages (event details, photos, guest list and all replies) are deleted automatically 30 days after the event date, or immediately when the host deletes the event or their account. Guest groups are kept until you delete the member, the group or your account. We use encryption in transit (HTTPS), access controls and Firebase security rules, but no method is 100% secure.

6. Your rights

  • View and edit your account in 我的 › 账号 (Me › Account). Delete your account there (我的 › 账号 › 删除账号; on the website: Settings › Account › Delete account). Without the app, sign in at https://yaypik.com/delete-account to delete it, or send a deletion request there. What is deleted and what is kept, and for how long, is in section 5.
  • Withdraw AI upload consent in Settings; turn off camera, photos, location, notification and tracking access in iOS Settings; delete your advertising ID in Android Settings.
  • For a copy of your data or any other request, email support@yaypik.com. We reply within 15 business days.
  • California residents (CCPA/CPRA): you have the right to know, delete and correct your personal information and not to be discriminated against for exercising these rights. We do not sell personal information. Only when you choose to watch a rewarded ad may AdMob use your advertising identifier to serve ads, which may count as "sharing" under the CCPA; you can opt out by not watching ads, declining tracking on iOS or deleting your advertising ID on Android.
  • EEA/UK users: we process data to perform our contract with you, with your consent, and for legitimate interests. You may access, correct, delete, restrict, port or object to processing, and complain to your local data protection authority.

7. Children

The App is not directed to children under 13 (under 14 in mainland China), and we do not knowingly collect their personal information. Contact us and we will delete it.

8. Changes

We may update this policy. We will notify you in the App of material changes and update the effective date.

9. Contact

Shigong Liu (individual developer) · support@yaypik.com