Privacy policy
Updated: 2026-11-12Information 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, chat images and videos, and reports, event likes, questions and comments and their reports, notification preferences and tokens, AI image generation requests, and support requests. If you apply as a coach, we store your self-introduction, qualifications, career and achievements, target levels, coaching areas, fees, photos and introduction video. If you request a lesson, we store the requested time, your companions' names and a note. If you review a coach, we store your 5-star rating and comment. If you use a referral code, we store the code and who referred whom. If you answer "How did you hear about picklenow?" at sign-up, we store the option you chose and an optional free-text detail (up to 100 characters). If you choose to enter them, we store your Instagram username and Facebook profile URL.
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. Images and videos (up to 30 seconds) attached to chats have location and other metadata removed on upload and are shown only to people who can read that chat, through short-lived links. Coach applications are reviewed by administrators. While an approved coach profile is listed, its self-introduction, qualifications, career and achievements, target levels, coaching areas, fees, photos, introduction video and nickname are visible to signed-in users. Companion names and notes in a lesson request are visible to the coach you apply to. A coach's average star rating and number of reviews are shown on the coach's page, and comments you choose to publish are shown with your nickname and profile image. A person who enters your referral code sees your nickname, and you see only how many people you referred and how many have joined; the referral relationship is used to calculate points. Your answer to "How did you hear about picklenow?" is used only for aggregate analysis and improving outreach, and is not shown to other users. If you choose to add your Instagram username or Facebook profile URL, it is shown on your profile to signed-in users (not between users who have blocked each other). You can remove it from My Page at any time, and it is erased when you delete your account.
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.
Publishing videos on YouTube
We use YouTube API Services to upload videos we produce ourselves to our own YouTube channel (ピックルなう / picklenow). This only handles videos in the operator's own account; we do not collect, store or display YouTube data of app users or viewers. The parts that use the YouTube API are subject to the YouTube Terms of Service (https://www.youtube.com/t/terms) and the Google Privacy Policy (https://policies.google.com/privacy). The authorization credentials (access tokens) are kept only on the operator's own device, and you can revoke access at any time in your Google Account security settings (https://security.google.com/settings/security/permissions). Once revoked, the stored tokens stop working and we delete them. The only thing we store is the ID of each uploaded video. Please contact us through the support page with any questions.
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 club admin creates a club 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 club 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 Google's 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. Google may retain data for a limited period to monitor abuse. Do not put personal information in event or club names.
Website ad measurement (OpenAI)
Only after you consent on picklenow.life, we load the OpenAI measurement SDK and send page views, App Store button clicks, the ad click identifier (oppref), cookie identifiers, browser information and the IP address used for the connection to OpenAI (United States) to measure advertising effectiveness. We do not send user information such as names or email addresses and do not use automatic advanced matching. Clicks are not counted as installs. The __oppref attribution cookie lasts up to 30 days after being written; the __obref browser cookie lasts up to 365 days after creation. These cookie lifetimes do not describe retention of data already sent. Your choice is saved in browser local storage. The measurement SDK also stores the consent state in local storage and a cookie (__oaiq_consent, up to 30 days). If withdrawal cannot be saved and the old grant cannot be removed, we also store a non-identifying refusal flag in session storage and a refusal-only cookie (picklenow_ads_denied, up to 365 days), which takes precedence over that grant. If refusal storage is unavailable, cleared or expires, measurement may resume on a future visit; delete the browser site data in that case. You can use the site if you decline. Withdraw consent through the ad measurement settings at the bottom of the home page to stop future measurement and delete identifier cookies. Withdrawal does not retract data already sent. OpenAI uses and stores this information for ad measurement under OpenAI's Privacy Policy, including processing outside Japan such as in the United States. Existing cookieless PostHog website analytics operates separately.
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 club 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, chat text and attached images and videos are removed. Event likes and reports are deleted; questions and comments have their text erased and remain as "deleted comment" so replies stay in order. 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, likes, questions and comments, 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). Images and videos attached to chats are deleted 30 days after the event ends for participant chats and 30 days after posting for club chats, or immediately when the message is deleted. Unused images and videos 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. Event guide images and photos of past events are shown on the event page and the public event page (past-event photos appear on all of that organizer's events). Only images the organizer has agreed to are used in picklenow's ads and social posts. 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, along with the answer to "Was the level right?" and the good-point tags. Satisfaction, reactions and comments are visible to their sender and recipient; satisfaction totals are visible only to that event's organizer. The level answers and good-point tags are shown on that organizer's event pages only as anonymous shares and counts, and only once five or more answers have been collected for that 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.
Organizer track record
An organizer's event pages show how many events they have held, the share of players who came two or more times, the share of first-time players who came again, and the spread of players' levels. These figures are totals from event attendance and the level chosen in each profile, and never show who attended. Shares and the level spread are not shown when fewer than five people are counted.
Event likes, questions and comments
We store your likes on events, questions and comments (up to 200 characters), replies, and reports. Like counts and the text, nickname, profile image and time of questions and comments are visible to signed-in users who can see that event (not between users who have blocked each other). We do not show who liked an event. To count unique viewers, when you open event details while signed in we store your member ID, the event type and ID, and the first viewing time until account deletion. Other users see only the total number of viewers, never who viewed an event. Organizers and co-hosts can hide comments on their own events, and the operator reviews reports. Public comments cannot contain contact details such as phone numbers, email addresses or LINE IDs; once your participation is confirmed, use the participant chat to contact others.
Content checks
When you send a public comment or a participant chat message, our own servers automatically check the text against a fixed list of terms for contact details and inappropriate expressions. The text is not sent to external AI or other companies' services. Public comments containing contact details are not saved and you are told why. Public comments that may contain inappropriate expressions are visible only to you until the operator reviews them; participant chat messages are delivered and then reviewed by the operator. The results are used only to decide whether content is shown and whether to restrict use.
Profiles, clubs 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 club names, descriptions, images, messages (including attached images and videos) and polls; club 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 club 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 clubs, confirming scores, recording play, starting a sign-in and whether it succeeded along with the sign-in method, starting to use the app as a guest, opening the app for the first time, completing sign-up and profile setup, liking, posting questions or comments, saving, opening the share sheet, changing search conditions, sending chat messages, opening the app from a notification along with the notification type, and which part of the home screen you tapped and what kind of item it opened), 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 the usage data sent to PostHog for advertising or tracking across other companies' services (ad measurement is handled separately as described in "Ad measurement (Meta)"). 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), clicks on the App Store link, the device type (phone or computer) and whether the browser marks the visit as a user-initiated navigation 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).
Ad measurement (Meta)
To measure whether people who saw our Meta (Facebook, Instagram) ads installed the app and signed up, and to optimize ad delivery, the app includes the SDK of Meta Platforms, Inc. (United States). We send Meta app installs and launches, completed sign-ups and the sign-up method (LINE, Google or Apple), and device information the SDK attaches (model, OS, language, time zone, app version and an identifier the SDK creates on your device). Your IP address also reaches Meta when the data is sent. Only if you allow "Allow Apps to Request to Track" on iPhone do we also send your advertising ID (IDFA). If you do not allow it, we do not send the advertising ID. On Android we do not send the advertising ID. We do not send your name, email address, phone number, location, free text, sign-in credentials, internal user ID or the usage data sent to PostHog. Meta uses and stores this information for ad measurement and delivery optimization under Meta's Privacy Policy, including processing outside Japan such as in the United States. You can stop recording installs, launches and sign-ups and sending the advertising ID with "Ad measurement" in My page > Settings. Because of how the SDK works, even when it is off the SDK may contact Meta at app launch to fetch its settings and may send its own crash reports, and your OS and SDK versions and IP address reach Meta at that time. You can change iPhone tracking permission at any time in your device's Settings.
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
Contact: picklenow Support Office (picklenow運営事務局)
picklenow.support@gmail.com