GrubClique Privacy Policy

Effective date: August 22, 2026

GrubClique helps groups compare restaurant preferences and find shared matches. This policy describes the current Android app and will be updated before any new data practice is released.

Accounts and profile information

You may create or access a GrubClique account using email and password or by continuing with Google. Account data can include your email address, unique user ID, username, display name, authentication provider, and session information. Supabase provides GrubClique’s authentication and account-data hosting. Google processes information when you choose Google sign-in. GrubClique does not receive or store your plaintext password.

Information we use

GrubClique uses account and profile information, clique codes and memberships, friend connections, restaurant preferences and swipe choices, matches, and chat content to provide account access, group matching, and communication. It does not display advertising and does not use advertising SDKs.

Contacts and profile choices

If you choose “Find friends from contacts,” GrubClique requests access to your contacts. Valid phone numbers are normalized to the international E.164 format and converted to one-way hashes before contact matching; raw address-book entries are not uploaded. During a compatibility period, valid +1 numbers also produce a legacy last-ten-digit hash so users on an earlier app version can continue to match. If you save a phone number for discovery, another signed-in user can find your profile by entering an exact matching number, which is normalized and hashed on that user’s device before lookup. Signed-in users can also find a profile by entering its exact username or account email address. Contact discovery is optional and can be disabled by revoking Contacts permission in Android settings or removing the saved discovery number. A profile image selected in the current app is stored as a device-local reference unless the app clearly tells you that an upload feature has been enabled.

Location

GrubClique may request access to your approximate and precise device location while you use the app. Location is used to determine your general area and retrieve nearby restaurant results. Location access is optional: you may deny the permission or revoke it later in Android settings, although nearby restaurant features may not work correctly without it.

When you use nearby search, location may be transmitted over an encrypted connection to service providers that return restaurant results. GrubClique processes location only as needed to complete the nearby-search request. It is not used for advertising, sold, or retained in your GrubClique profile or clique records.

Issue reports and diagnostics

If you submit an issue report in the Android app or on the public website, GrubClique processes the category, title, description, optional reproduction steps, optional contact email and follow-up choice, and any optional screenshot you select. Android reports also include the app version and code, device manufacturer and model, Android version, report source, and submission timestamp. The report does not automatically include your location, chat contents, credentials, or authentication tokens.

Issue-report text and receipt metadata, delivery status, and abuse-prevention records are processed through Supabase. Resend delivers the report to the GrubClique support mailbox. A selected screenshot is passed directly to the email service and is not saved in Supabase Storage. Public website reports use Cloudflare Turnstile and limited network information to identify automated abuse; authenticated app reports are throttled by a protected representation of the account identifier.

How information is shared and retained

GrubClique does not sell personal information. Information is used to provide account and clique features and is visible only where needed for the group experience. Contracted service providers, including Supabase, Resend, Cloudflare, and restaurant-search providers, may process data to authenticate users, host app data, deliver chat messages and issue reports, prevent abuse, and return restaurant results. Account, profile, friendship, clique, preference, match, and chat information may be retained while your account is active and as needed to operate the group experience. Location is handled as described above and is not retained as part of those records.

Issue-report metadata stored in Supabase is deleted after 180 days, and rate-limit records are deleted after 24 hours. Copies delivered to the receiving Gmail mailbox, including screenshots, are retained according to the mailbox owner’s support and deletion practices.

Children’s privacy

GrubClique is intended for adults and is not directed to children under 13. We do not knowingly collect personal information from children.

Security and choices

Data transmitted by GrubClique is sent over encrypted connections. Keep clique codes private and share them only with people you trust. You can manage location and contacts access at any time in Android settings.

Account and data deletion

You may request deletion of your GrubClique account and associated data through the account-deletion page or the Delete account control in the Android app. After verifying account ownership, we will delete or anonymize associated account, profile, contact-discovery, friendship, clique, swipe, match, and chat data unless limited retention is necessary for security, fraud prevention, legal compliance, or resolving an active request. Deleting a GrubClique account created with Google does not delete your Google account.

Changes

We will update this policy when data practices, third-party services, or app functionality change. The effective date above identifies the latest revision.

Contact

Questions about this policy can be sent to redxjak@gmail.com. Product problems and suggestions can also be submitted through the GrubClique issue-report form.