English
Effective October 15, 2026
Ping is operated by Wontak Choi. Questions about this policy or your data can be sent to support@ping.io.kr.
Information we handle
- Account: your Ping user identifier, the identifier supplied by Apple or Google sign-in, and the email address supplied by the provider.
- Profile: your chosen display name, emoji, and optional photo.
- Activity: invitation tokens, friend relationships, ping reactions and times, and reminder preferences.
- Notifications: device push tokens, Firebase installation identifiers on Android, app version information, and Live Activity tokens on supported iPhones, used to deliver pings and reminders.
- Support and feedback: the message, category, optional reply email and screenshot you provide, submission time; support emails also include the sender address. Earlier form versions may include an overseas-processing consent record or details-display preference.
- Safety reports: the reporting and reported account identifiers, selected reason, optional explanation, and moderation records.
- Technical data: request and error logs that our hosting providers need to operate and protect the service and invitation website.
Account information comes from Apple or Google sign-in; you provide profile and support information; activity and notification tokens are generated as you use Ping. Hosting providers generate technical logs when you use the app or website. Ping uses the system photo picker on iPhone and Android for your optional profile photo. It does not access or upload your address book.
Why we use it
We use this information to create and secure your account, show your profile to friends, manage invitations and pings, send requested notifications, maintain the service, and answer support requests. We also use service statistics recorded by our backend, without account identifiers, to understand service usage. We do not sell personal information or use it for advertising.
Who can see it
Your friends can see your display name, avatar, and shared ping activity. Anyone with your invitation link can see the display name used in its preview. Do not share an invitation link with someone you do not want to invite; you can reset it in Ping settings.
Service providers and location
Apple provides sign-in and iPhone notification delivery. Google provides Google sign-in; Firebase Cloud Messaging and Firebase Installations provide Android notification delivery and installation identifiers. Supabase hosts account, database, storage, and realtime services; Ping’s Supabase project is in Seoul, South Korea. Tally BV receives and stores feedback sent through our optional web forms. Your chosen email app and provider send support emails and feedback from older app versions; Zoho Mail receives those emails in our support inbox. Vercel hosts the invitation and information website and may process website request metadata in its infrastructure. These providers process data for the stated services and maintain privacy and security protections consistent with this policy. We use access controls and encrypted connections to protect information.
Tally feedback and overseas processing
Settings → Send feedback opens a Korean or English Tally form according to the app language. The form is optional. Ping does not automatically pass your account identifier, sign-in email, tokens, friends, or ping history to the form, and does not move existing support emails to Tally. Only information you choose to include in your message or image is included.
- Recipient and work entrusted: Tally BV, Belgium (hello@tally.so), for hosting, receiving, storing and displaying feedback to the Ping operator so we can review it, address issues and reply if requested.
- Information: category, message, optional reply email and screenshot, submission time. Please omit passwords, sign-in codes, sensitive information and other people's private information. We remove information that is unnecessary for handling the feedback.
- Location, timing and method: responses are sent over an encrypted internet connection on submission; selected images are uploaded when attached. Tally lists Google Cloud in Belgium for response hosting and Cloudflare storage in the European Union for optional uploaded images. Tally publishes the region, rather than individual storage countries, for those images. See its current processing-provider list and privacy notice for infrastructure and technical-data processing.
- Basis and choice: limited handling of feedback that you initiate, issue resolution and requested replies relies on service-contract performance where necessary (Article 15(1)(4) of Korea's Personal Information Protection Act), and otherwise our legitimate interest in reviewing voluntary feedback within a reasonable scope (Article 15(1)(6)). Transfers of these responses and attachments to Belgium/EU rely on the EU/EEA adequacy recognition under Article 28-8(1)(5), effective September 16, 2025, rather than separate overseas-transfer consent. See the official recognition status. The form shows a short summary and a link to this privacy policy, without a consent checkbox. Screenshots are optional and can be attached immediately. You can avoid this form and continue using Ping, and contact support@ping.io.kr instead. Contact the same address to object to processing or request deletion; information already processed is handled as described below.
- Retention: normally 90 days after the case closes. The operator manually deletes expired Tally submissions and uploaded files and empties Tally's Trash. Necessary records may be held longer for an ongoing dispute or a specific legal obligation. Deleting your Ping account does not automatically delete feedback; request deletion by email if needed.
Form-response email notifications, partial-response collection and saved answers for later are disabled. A signed webhook passes each submission payload to a notification function in our existing Supabase project in Seoul, South Korea. The function uses it transiently to send an arrival alert, without storing or logging the payload or downloading attachments. Discord receives only a generic new-feedback notice and a form-level Tally dashboard link that requires the operator to sign in; message contents, reply email, images, respondent/submission identifiers and tokenized preview links are not sent to Discord. Reply email and screenshots are optional. We review submissions in Tally; actionable issues may be manually summarized in our internal issue tracker. We do not add advertising or analytics integrations to these forms.
Retention and deletion
Account and activity data is kept while your account exists. In Ping, open Settings → Account management → Delete account to remove your active account, profile photo, friendships, ping history, invitations, and registered push tokens from active systems. Safety reports and handling records, including necessary account identifier snapshots, are normally retained for 180 days after final review and case closure; deleting an account does not automatically erase these records. Necessary records may be held longer for an ongoing investigation or a specific legal preservation obligation, and are removed when that reason ends. Service statistics without account identifiers, such as signup and ping counts, may remain after account deletion. Feedback from the updated app is stored in Tally as described above, rather than as a Ping app record. Support messages and feedback emails from older versions, including optional images, are normally retained for 90 days after the case is closed; deleting your Ping account does not automatically delete these emails or Tally submissions. Necessary records may be retained longer for an ongoing dispute or a specific legal obligation. Provider backups and technical logs may remain for a limited period under their retention schedules or where law requires. You can ask about those periods or request help at the email above. You can also request account deletion without opening the app.
Crash and service error reporting
Versions that include crash reporting send crash diagnostics, stack traces, app version, operating-system and device information to Sentry in the United States to find and fix failures. We disable screenshots, session replay, performance traces and interaction breadcrumbs, and remove user details, request contents and exception messages before sending crash events. Server alerts contain fixed service names and error categories rather than request contents or account data. Sentry forwards error alerts through Cloudflare Workers; Discord receives only a generic error notice, project identifier and a Sentry issue link. Cloudflare stores delivery summaries for up to 30 days after successful delivery and retains failed deliveries for retry. Sentry retains diagnostics according to the project’s retention settings. These diagnostics are used for service reliability, not advertising.
Earlier app versions
Earlier versions with a Share usage analytics setting may still send optional events to PostHog in the US if you previously enabled it. Those events include a random app identifier, invite and ping event names and times, a hash of an invitation link identifier, and basic device and app information. The hash can be matched to an invitation in Ping's systems; names, photos, and invitation URLs are not sent. Turn off that setting in the earlier app or update to the version that removes it to stop new collection. Previously collected events remain subject to the provider's retention settings and are not automatically deleted with your Ping account. Contact us for help requesting their deletion. Updated versions without that setting do not send these analytics events.
Your choices and changes
You can change your profile and notification settings in the app, decline notification permission in your device settings, and withdraw from Ping by deleting your account. Email us to request access to, correction of, deletion of, or restriction on processing of your information, including if you cannot access the app. We will update this page when our practices change and show the effective date above. The October 15, 2026 update adds optional Tally feedback, its EU/EEA overseas-transfer basis and its retention procedure. It does not transfer existing account data or past support messages to Tally. Previous policy (October 10, 2026).