Privacy Policy

Who is responsible

The owner of PINLIFE and controller of personal data is ФОП Михайлюк Світлана Михайлівна (sole proprietor Svitlana Mykhailiuk). Contact: pinlifeservis@gmail.com. This policy covers the PINLIFE app and pinlife.com.ua website. PINLIFE is intended for users aged 16 and over.

Data and purposes

• Email, account identifier and authentication data support sign-in, access recovery and account security.
• Name, optional biography, date of birth and avatar personalize your profile.
• Places, coordinates, addresses, countries, check-in times, photos and notes support maps, history and synchronization. Historical records may include previously entered ratings.
• Current location, with permission, helps find nearby places. The app does not request continuous background route tracking.
• Friendships, blocking, posts, likes and comments support interactions with confirmed friends.
• Installation identifier, platform, language, push token and preferences deliver notifications about check-ins, likes and comments. Delivery jobs also contain technical statuses.
• Local history, photo cache, preferences, session and pending changes support on-device use and synchronization.

Google Maps and Firebase SDKs also declare processing of identifiers, crash data, performance, product interactions and other technical diagnostics to operate and improve their services. These are third-party component data even though PINLIFE has no separate advertising analytics integration.

What friends can see

Friendship requires confirmation. New check-ins are shared with friends by default; choose “Only me” before saving a private entry. Older history is not automatically published.

A shared check-in includes your name, place, coordinates, time and any added note or photo. Likes and comments are visible to people who can access that post. Email and date of birth are not included in a friend’s profile card.

Unsharing a post, removing a friend and blocking restrict future access. They do not erase screenshots, other saved copies or notifications already delivered.

Service providers

Supabase provides authentication, database, photo storage and server functions. The main project is hosted in Frankfurt. Supabase privacy policy.

Google Maps and Places process map and search requests including search text, the area or coordinates and technical connection information. Google privacy policy.

Firebase Cloud Messaging and, on iOS, Apple Push Notification service deliver notifications. They process device tokens and message content. Notifications may appear on a locked screen. Firebase privacy · Apple privacy.

Provider infrastructure may process data in other countries. Their policies describe applicable safeguards and transfer mechanisms. PINLIFE does not include advertising integrations; this website does not use analytics or advertising trackers.

Permissions and control

Location helps find places; camera and photo selection are optional. You can revoke permissions in phone settings. This does not delete previously saved entries. Disable notifications in your profile or system settings. You can edit your profile, control post audiences, friendships, likes and comments, and delete your account.

Retention and deletion

Account data and history are retained while needed to operate your account or until you request deletion. Deletion markers may remain until account deletion to prevent another device from restoring removed entries during synchronization.

The updated app first removes cloud photos and the avatar through the storage service, then deletes the account and related records. If cleanup fails, the account is not deleted; retry or contact support. An older version may require an update.

The current Supabase Free plan does not include customer-accessible scheduled backups. API and database logs are available for one day under the plan terms. This does not mean the provider keeps no internal operational copies or security logs. Other technical data follows each provider’s policies; immediate erasure from all operational copies is not guaranteed.

Website and requests

This static site has no login forms, cookies, analytics or location requests. To deliver pages, its server receives your IP address and technical request information. Access logging is disabled; errors may be logged. Nginx retains up to 14 rotated nonempty error logs, so this is not a guaranteed 14-day limit. Email links open your mail app; this website does not send requests.

Contact pinlifeservis@gmail.com for access, correction, deletion or other questions about your data. We respond within 30 days and complete a verified deletion request within 30 days after account ownership is confirmed. We may need to verify ownership, but never ask for your password or a one-time code. Policy changes are published here with an updated date.

Social profiles and trips

Signed-in PINLIFE users can search by name, optional last name or place of residence. These fields are visible in search results. Avatars are visible by default; you can hide yours in social profile settings. Email and date of birth remain private.

A public social profile lets signed-in users see the titles and dates of saved named trips, including trips with no available visits, and routes from published check-ins. For a closed profile, details are available to confirmed friends and the owner; others see country summaries. Private and unpublished check-ins, notes and photos are excluded from social trip routes. A public profile can make published visit locations visible beyond confirmed friends.

Public community places

When you create a community place, its name, exact coordinates, category and optional city/country become visible to other signed-in PINLIFE users. They may check in at the same place. This also applies if you choose a home or garage. The creation screen explains this before saving.

Place visibility is separate from check-in visibility: selecting “Only me” does not hide a community place you created. Deleting the creator’s account removes its catalog entry. Other users may retain that place in their own historical check-ins.

Google and Apple sign-in

You can sign in using email, Google or Apple. The chosen provider shares the identity information needed to authenticate, such as an account identifier, email and name when available; this does not grant PINLIFE access to Gmail messages. Apple may provide a private relay address. Deleting an Apple-linked account on iPhone asks you to confirm with Apple so authorization can be revoked before account cleanup.

Notifications and editing

The in-app notification center retains notifications for up to 30 days. Push delivery may leave notifications on your device. Editing a check-in, including its photo, is available only for one hour after creation.

Photo checks and reports

New photos you make available to others, including visible avatars, are sent by the server to Google Cloud Vision to check for sexual or violent imagery. Until approved, a photo is hidden from others; its owner retains the original. Photos in “Only me” check-ins are not sent for this check. Photos already shared when checks were enabled on September 17, 2026 are not scanned retrospectively; replacing a file requires a new check.

Automated checks can be wrong. Contact support to appeal a restriction. You can report posts, comments, profiles and community places in the app and block users. Only authorized operators can read reports. We review reports daily and respond to harmful content within 24 hours. Sexual exploitation, threats, violence, harassment, hate, spam and sharing another person’s private information without permission are prohibited. Violations may lead to content removal from shared views or restrictions on social features.

According to Google’s documentation, synchronous Vision requests process image data in memory without writing it to disk and do not use it for model training. Google temporarily logs technical request metadata; this documentation does not specify a retention period. PINLIFE retains the decision and queue status, not Google’s full response.