Privacy policy

Information we use

LINE sign-in provides an identifier, display name and profile image. Apple sign-in provides an identifier and a name when first authorized. Google sign-in provides an identifier, display name and profile image; we do not collect your Google email address (any address stored by an earlier version is not used and is erased on account deletion). Only if you turn on Google Calendar sync do we receive the email address of the connected account (see Google Calendar sync below). An email provided by Apple is never used to automatically merge accounts. We store your nickname, playing area, optional playing start month, gender and date of birth, manually entered DUPR details, event registrations, check-ins, results, journals, chat text and reports, notification preferences and tokens, AI image generation requests, and support requests.

Purpose and visibility

We use information for authentication, event hosting and participation, pairings and scores, personal records, notifications, abuse prevention and support. Nicknames and participation status appear in an event's participant list to signed-in users (not between users who have blocked each other). A manually entered DUPR ID is visible to the event's organizer and co-hosts so results can be submitted to DUPR. Gender, date of birth, playing start month and journals are private. Event chat is available to eligible participants and organizers; reports are reviewed by organizers and administrators.

Service providers

Cloudflare stores and processes data. LINE, Apple or Google provides sign-in; LINE, Expo and platform push services deliver notifications. DUPR ratings are entered manually without automatic synchronization or submission. Organizers can export a results CSV. Opening external news links or images connects to their publishers. We do not process in-app payments or collect card details. Pay any entry fee directly to the organizer on site.

Google Calendar sync

Only if you turn on Google Calendar sync, we ask Google (United States) for permission to create a dedicated calendar in your Google account and write events to it. We write the title, date and time, venue name and address, and a link to the event page for events you are confirmed to attend and events you organize. To provide sync we store your Google account identifier and email address (to show you which account is connected), a refresh token (encrypted), and a mapping of the events we wrote. When you disconnect or delete your account, we try to delete the dedicated calendar and revoke the token, and erase the stored data. Data obtained from Google is used only to provide sync and is never used for advertising or sold to third parties.

AI image generation

Only when an organizer creates an event cover, or a community admin creates a community image, with AI, we send generated text to an external AI service. Both are processed by Google Gemini (United States). The text is built from the event title, type and beginner-friendly flag, or the community name, icon and area name, plus the chosen style. We do not send reference images such as photos, profiles or email addresses. Requests and generation history are stored for you, and the input text is erased on account deletion. According to both providers' API terms and published documentation, data sent through the API is not used to train models by default; we do not opt in to training. The providers may retain data for a limited period to monitor abuse. Do not put personal information in event or community names.

Providers outside Japan

We entrust the handling of personal data to the following providers: Cloudflare, Inc. (United States; storage and processing), Expo (United States; push relay), Apple (United States; Apple sign-in and push), Google (United States; Google sign-in, Android push, and event cover and community image generation) and PostHog (United States; usage analytics). LINE (LY Corporation, Japan) is used for LINE sign-in and notifications. Each handles data only for the purposes we set, and we choose providers with systems adequate to protect personal information. Information about each country's personal data protection rules and each provider's protective measures is available on request.

Retention and deletion

We use encrypted transport and access controls. Request deletion in My page > Delete account. The operator normally processes requests within seven days after resolving unfinished hosted events and registrations. Profiles, sign-in connections, journals and chat text are removed. Shared match results remain under Deleted user. Request processing status and anonymized internal IDs remain to prevent duplicate processing. Requests can be cancelled before processing starts. Backups expire under the infrastructure provider’s retention period.

Security measures

Data is encrypted in transit over HTTPS. Sign-in credentials are kept in the device's secure storage, and the server keeps only a digest of the refresh token. Apple connection data is stored encrypted. What you can see and do is limited by role: you, organizers and administrators. The operator accesses personal data only to the minimum extent needed for support, troubleshooting and deletion. Secrets such as API keys are kept out of the code and managed as runtime secrets. Our policy is not to write chat or journal text, authentication tokens or images to troubleshooting logs. Processing is entrusted only to the providers listed above.

Retention

Your information, such as profile, participation records, journals, chat and AI image input text, is kept until you delete your account. Refresh tokens are deleted 30 days after they expire or are revoked. Notification delivery records are deleted 30 days after delivery completes or fails. The location sent with a court request (latitude, longitude and accuracy) is erased when an administrator approves or rejects the request, and in any case 90 days after submission. App usage analytics data (PostHog) is deleted when you delete your account. Website visit data (PostHog) is recorded under an anonymous ID not linked to you, so it is not covered by account deletion and is kept according to the PostHog data retention setting (currently one year). Unused images are deleted after expiry. Deletion request processing records are kept to prevent duplicate processing. Backups expire under the infrastructure provider’s retention period.

Event images

We store organizer-selected photos or posters, their owner, format and dimensions. Images attached to published events are accessible through their image URL. Unpublished images are accessible only to their owner. Image metadata such as location is removed during upload. Unused images are deleted after expiry; account deletion stops public access and removes stored images.

Home courts

Saved venues and responses to home-court suggestions are private. We use participation records to suggest venues. You can add or remove venues in My page. Account deletion removes saved venues and suggestion responses.

Event feedback

We store satisfaction, reactions and comments sent after an event. Content is visible to its sender and recipient; satisfaction totals are visible only to that event's organizer. Administrators can review content reported by its recipient. Senders can edit or withdraw feedback. Account deletion removes feedback sent or received and its related reports.

Profiles, communities and location

We store your profile photo, bio, level, play styles, paddles (including photos), play records and badges, and show them on your profile to other users. Daily play days and frequently visited courts are shown only to you and your friends. We store friend and block relationships and community names, descriptions, images, messages and polls; community content is visible to its members. Your device location (latitude, longitude and accuracy) is sent only when you choose Use current location in a court request, and is used to review that request; it is erased when the request is approved or rejected, and in any case after 90 days. Arrival checks at your saved courts run on the device and never send your location. Reports are received by email by the operator. Account deletion removes your profile, paddles, court requests and friend and block relationships, and erases the text of your community messages. Guest names entered by an operator for events you organized are replaced with Guest.

Usage analytics

To improve the app, we send the type of screen you open (such as event details, without individual IDs), key actions (joining or creating events, creating communities, confirming scores, recording play), and your device model, OS, language, time zone and app version, together with your internal user ID, to PostHog (servers in the United States). We do not send names, email addresses, chat or journal text, location or screen recordings, and we do not use this for advertising or tracking across other companies' services. You can stop sending it with "Share usage data" in My page > Settings. When you delete your account, your usage data stored in PostHog is deleted too. On our website (picklenow.life), we send the pages viewed, the referrer, campaign names (utm parameters in the URL) and clicks on the App Store link to PostHog, together with an anonymous ID derived from your IP address and device information that changes every day. We do not send the IP address itself, we strip parameters from the referrer URL, and we do not use cookies. This visit data is not linked to your account and is therefore not covered by account deletion (see Retention).

Your choices and support

You can edit your details in the app. Contact the address below for access, correction or deletion requests, including when you cannot sign in. The operator is an individual (Kosuke Shibayama); the address is disclosed without delay on request. We may verify your identity using only the necessary information. Material policy changes will be announced in the service.

Operator and contact

Operator: Kosuke Shibayama (individual)
Address: disclosed without delay on request
advalay.company@gmail.com