Privacy policy
Small data,
plainly stored.
This page lists everything this directory of Grok Bot templates actually collects, where it lives, and how to have it deleted — in plain English, matching what the site's code really does. Nothing here requires an account to read, and most of the site requires no account to use.
- Account to browse
- None
- Analytics cookies
- Zero
- Ads / data sales
- Never
- Effective
- 30 Aug 2026
The short version.
Grok Bot Templates is an independent, curated directory of public Grok Bot templates. It is not affiliated with xAI (now SpaceXAI) or Cursor. You can browse every listing, guide, and the link inspector without signing in. The only personal data we handle comes from three places: cookieless page-view analytics, Google sign-in if you choose to use it, and the templates you save or submit while signed in. We run no ads and we never sell personal data.
Browsing and analytics.
The site uses Vercel Web Analytics, a privacy-friendly, cookieless service. It collects aggregated page-view statistics — which pages are visited, the referrer, the country, and the device type — without setting cookies and without tracking you across other websites. We see traffic in aggregate; we cannot identify an individual visitor from it. There are no advertising trackers on this site.
Signing in with Google.
Sign-in is optional and uses Google, handled by Firebase Authentication (a Google service). When you sign in, we receive and store three things from your Google account in a member profile in Cloud Firestore, keyed to your account ID:
- NameYour Google display name, shown back to you on your account page.
- Email addressUsed to identify your account and attached to any listings you submit.
- Profile photo URLA link to your Google profile picture. We store the link, not the image.
Sign-in happens on Google's side — we never receive or store your Google password. Firebase keeps your sign-in state in your own browser; signing out clears it.
Saves and submissions.
Two account features write data to Cloud Firestore, always tied to your account ID:
- Saved templatesThe ID (slug) of each Grok Bot template you save to your shortlist, with a timestamp. Unsaving a template deletes that record immediately.
- SubmissionsWhat you type into the listing form — bot name, public x.ai share link, your X handle, category, and the one-sentence job description — plus your sign-in email and a review status.
Firestore security rules restrict access: your profile and shortlist are readable only by your own signed-in account, and a submission is readable only by the account that created it. Submissions stay private while in review; if approved, the listing details you wrote (name, link, handle, category, job) are published in the directory — that is the point of submitting — but your email address is not.
Public listing data.
The directory itself is built from public information: Grok Bot template share links published on x.ai, indexed from creator submissions and public community sources, always with creator attribution. We list the public bot name, the creator's public handle, the public share link, a category, and a description. We never copy or rehost bot configurations, and we hold no private data about creators. If a listing about you is wrong, or you want it removed, ask via the contact page and we will update or delist it.
What we never do.
No ads, no ad networks, no sale or rental of personal data, no sharing with data brokers, and no marketing emails — we do not send email at all right now. Your data sits with our two infrastructure providers, Firebase (Google) and Vercel, which process it to run the site and for nothing else on our behalf.
Deleting your data.
Email us via the contact page from the address you sign in with, and we will delete your member profile, your saved templates, and your submissions. Creators can likewise request that a published listing be corrected or removed. You can also unsave templates yourself at any time — each unsave deletes the record on the spot.
Changes to this policy.
If what the site stores changes, this page and its effective date change with it. This policy is effective as of 30 August 2026.
Anything unclear, or anything on this page that does not match what you see the site doing — tell us via the contact page and we will fix the code or the policy, whichever is wrong.