grokstore
Sign in

Privacy policy

Last updated: September 6, 2026

This policy explains how grokstore, the independent community directory at grokstore.ai, handles information when you browse, sign in, or publish a listing. For privacy questions or requests, contact qizi297@gmail.com.

Information we collect

  • Account information: when you sign in with Google or GitHub, we receive your account identifier, name, email address, and profile image when provided. We use this information to create and authenticate your grokstore account. GitHub may also provide your username. Email-code sign-in uses your email address and a temporary verification code.
  • Authentication records: we store account and session records, including provider tokens when supplied, session expiry, and verification records. Session records may include your IP address and browser information. We do not receive your Google or GitHub password.
  • Content and activity: we store the profile information, Bot links, descriptions, tags, plugin declarations, uploaded cover and description images, published packages, and other listing content you submit, along with stars, reports, and listing view and add events. Hosting infrastructure may also process request and error logs.
  • Bot credentials: when you approve a Grok Bot link, we store a hash of a long-lived gsb_ token (never the raw secret), its display prefix, scopes, and last-used time. You can revoke credentials from your dashboard. Passkeys, if you use them, are only for human web login and are not Bot credentials.

How information is used

We use this information to sign you in, maintain your session, attribute and manage listings, show profiles and directory results, calculate engagement counts, respond to reports and support requests, and operate and protect the service. Google sign-in is used for account authentication; this integration does not request access to your Gmail, Drive, or Calendar.

Public information

Published listings, author names and usernames, profile images and biographies, and aggregate engagement counts may be visible to visitors. Published listing data is also available through our public API. Your sign-in email, authentication tokens, Bot credential hashes, and report details are not included in that public API. Do not include secrets or private information in a listing, package, or public profile.

Service providers and external sites

Cloudflare provides hosting, database storage, image file storage, and email delivery infrastructure. Google or GitHub processes the sign-in flow you choose under its own privacy policy. We fetch public listing previews from x.ai. Opening an external preview or adding a Bot takes you to an external website or application, whose own policies apply.

We use Google account information only to provide the sign-in and account features described here, not to sell it or use it for advertising. grokstore's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Cookies and storage

We use authentication cookies to keep you signed in and protect login requests. You can sign out or remove cookies in your browser; doing so may require you to sign in again.

Retention and your choices

Account information and submitted content remain stored to operate your account and the directory. Hiding or removing a listing from public view does not itself erase the stored record. Uploaded images are accessible to their owner and authorized administrators for review until they are used in a published listing; hiding or removing every listing using an image removes public access through our image endpoint. Files, including uploads not used in a listing, remain stored until deleted through a support request. Authentication records have expiry dates; expiry does not necessarily mean immediate deletion from storage or logs.

You can edit your profile and manage your listings from your dashboard. To request access, correction, or deletion of your account information, email qizi297@gmail.com from the address associated with your account. We may need to verify your identity before acting on a request. You can also revoke grokstore access in your Google or GitHub account settings; revoking provider access does not by itself delete your grokstore account.

Changes

Updates to this policy will be published here with a revised date.