Privacy Policy

Effective November 13, 2026

Plobert is a social app for sharing hangs with friends. It is operated independently by Nick Munck in the United States. This policy explains how personal information is handled in the Plobert app and on plobert.com. For privacy questions or requests, email muncknr@gmail.com.

Information Plobert uses

• Account and profile information. When you sign in with Google, Plobert receives your account identifier, email address and basic profile information supplied by Google. You choose a nickname and may upload a profile photo. Plobert does not receive your Google password. If another sign-in provider is offered, it supplies the information described in its sign-in screen. If you create an account with email and password, Supabase Auth processes your email, password and verification or reset codes. Passwords are handled by the authentication service and are not stored in Plobert's profile tables. Verification and password recovery use emailed one-time codes.
• Circles and hangs. Plobert stores circle names, ownership, memberships, invitations, requests, privacy preferences, blocks, hang details and your participation actions. It also stores hang history, estimated and detected participation time, attendance counts, peak attendance and badges.
• Selected contacts and phone numbers. The optional contact picker lets you choose a person and a phone number. The app does not upload your entire address book. It sends a selected number for permitted account matching; a name and a phone-number fingerprint may be retained for an invitation you create. Android may require contacts permission to read the selected record. Where phone verification is required for new accounts, you must confirm a number using a text-message code before using circles and hangs. Existing accounts may be eligible without this step. Your verified number is used to confirm account ownership, match permitted phone lookups and recover invitations intended for that number.
• Location and attendance. With your device permission, setting a hang location saves the host's chosen location label and precise location point. Authorized hang viewers can receive that location. When you join a hang and grant the needed permissions, the app uses your device location, including in the background, to detect arrival and departure and calculate participation time. Guest coordinates are processed on the device; attendance reports send timestamps, distance from the hang and accuracy information, rather than a raw guest location trail. The server stores attendance state, boundary classifications and timing information. Adding someone to a circle does not itself start location tracking or share their location.
• Notifications and activity. Plobert stores push tokens, notification preferences, delivery records and recent app-activity timestamps. These support relevant hang, circle, arrival, badge and inactivity notifications. Your phone may display notification content on its lock screen according to your device settings.
• Service operation. Limited events record use of the Add People and invitation flows, with account or circle identifiers, event types and timestamps. These events do not include contact names, raw phone numbers, search text or coordinates. Infrastructure providers may process IP addresses, device/browser information, request times and error or security logs when operating the service.

How information is used

Information is used to authenticate accounts, operate circles and hangs, match people according to their privacy choices, process invitations, provide attendance and statistics, deliver notifications, respond to requests, prevent misuse and understand whether invitation features are working. Google account information is used for sign-in, account management and security.

Plobert does not sell personal information, use Google account data for advertising or include advertising SDKs in the app. Plobert's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Who can receive information

• People you connect with. Authorized circle members and hang viewers can see the profile, hang location and participation information needed for those features. Circle owners can manage their circles and requests. Discovery settings control permitted name and phone lookups; raw phone numbers and sign-in email addresses are not displayed in search results. A person holding a valid invitation link may see the inviter's display name. Links you share through another app are also subject to that app's practices.
• Service providers. Supabase provides authentication, database, storage and backend functions. Expo provides app build and push services. Google and Apple provide relevant sign-in, operating system, app distribution and notification services. Cloudflare hosts and protects the website and its domain. Resend delivers account verification and password-reset emails, processing recipient addresses, message content and delivery records. Twilio Verify processes phone numbers, verification messages and delivery or verification records to confirm phone ownership. These providers process information needed for their services under their applicable terms and privacy policies.
• Legal and safety needs. Information may be disclosed where required by law or reasonably necessary to address fraud, security incidents, abuse or threats to people's safety or rights.

Information may be processed in the United States and other countries where the service providers operate. Privacy protections may differ between countries. Where required, applicable safeguards and rights apply to international processing.

Your choices and privacy rights

You can change your nickname and optional photo, manage discovery and addition preferences, block people, leave circles, cancel participation and end a hang you host. The Location switch stops attendance tracking on that device; turning it back on starts fresh location checks. The Notifications switch controls push registration on that device. Previously recorded history and notifications already accepted for delivery may remain. Your device settings also control location, contacts, photos and notification permissions. Revoking location access stops new usable location evidence, but previously recorded history may remain and the service may take time to reflect a permission change. Removing a permission does not delete your account.

Use the account-deletion control in your Plobert profile to request deletion. You may also email muncknr@gmail.com for access, correction, deletion or other privacy requests. Depending on applicable law, you may have rights to a copy of your information, portability, restriction, objection or withdrawal of consent, and to complain to a privacy regulator. Identity may need to be verified before a request is fulfilled. Your request will be handled according to applicable law.

Retention and deletion

Account, circle, hang-history and badge information is generally retained while needed to provide the service and your history. Precise host coordinates are cleared when a hang is closed; a location label may remain in saved preferences. Attendance boundary observations are configured for removal after seven days, and invitation-flow analytics events after 90 days, through scheduled cleanup. Invitation links normally expire after 14 days; expiration stops use of the link and does not by itself erase every related record.

Account deletion removes the account, profile photos and linked personal records through the deletion service. Other participants may keep their own minimal history and previously observed attendance counts without the deleted account's identity. Information already copied or shared by another user cannot be recalled. Backups, infrastructure logs and records needed for security, legal obligations or resolving a request may remain for their applicable retention periods; deletion is not a promise of immediate removal from every backup.

Device storage, website logs and security

The app stores authentication sessions, preferences and limited pending attendance evidence on your device so it can work across launches and brief connectivity gaps. The website's hosting provider may use essential security mechanisms, cookies and request logs. The Plobert website does not include advertising trackers. Plobert uses HTTPS and access controls to help protect information, but no service or device can guarantee complete security.

Age requirements

Plobert is intended for people aged 13 or older. Users below the age of legal adulthood must have a parent or guardian's permission. A higher minimum age or parental-consent requirement may apply under local law. Plobert is not directed to children under 13 and does not knowingly collect their personal information. Contact muncknr@gmail.com if you believe a child is using Plobert contrary to these requirements.

Changes and contact

This policy may be updated as Plobert changes. The effective date will be revised, and additional notice will be provided where required by law. Privacy and support requests can be sent to Nick Munck at muncknr@gmail.com.