Privacy
In one paragraph
UniqueFarm runs inside your own browser. Your OpenAI key, your settings, your reply history and the memory of which posts it already commented on stay on your device. The only things that leave your machine are (1) the requests you make to OpenAI with your own key, (2) a small license check so your access key keeps working, and (3) any integration you switch on yourself (Google Sheets, your own Supabase). We never see your X password, your OpenAI key or the text of the replies you post.
What stays on your device
- Your OpenAI API key and every setting (model, voice, timing, cost caps). Stored in Chrome's local extension storage, never sent to Unique Labz.
- Reply history (the post text snippet, the reply, model, time) so you can search what was written. Optional; clear it any time in Settings.
- Dedup memory: the ids of posts and comments already handled, so nothing is answered twice. Also kept in x.com's local storage so it survives a reinstall. Wipe it from Settings → Danger zone.
- Diagnostics: a rolling log of the last few hundred steps for the Bug finder. It never includes your key.
What the license check sends
To validate your access key the extension contacts Unique Labz's license service (hosted on Supabase) when the panel opens, roughly every 90 seconds while it is open, and after each reply it posts. Each call includes:
- your access key and a random device id created on install (so one key is bound to one device);
- your X handle as shown in your logged-in X tab, and the extension version;
- your public IP address, fetched from
api.ipify.organd cached for six hours (shown to the team on the device dashboard); - a usage counter per tool (comment, reply guy, engage, home) so the dashboard can show activity: the count only, never the post or reply text;
- when something fails, a short error line with keys and tokens scrubbed out and no comment text, rate-limited to a handful per session, so versions can be improved.
This is what lets the team suspend a key, move it to a new device, or push an announcement into the panel. It is not used for advertising and not sold to anyone.
What goes to OpenAI
To write a reply the extension sends the post's text, the author's handle, small previews of attached images and any linked article excerpt, together with your voice instructions, directly from your browser to api.openai.com using your key. Usage is billed to your OpenAI account and governed by OpenAI's own terms and data policies. Unique Labz has no access to these requests.
Optional integrations you control
- Google Sheets: if you paste an Apps Script webhook URL, session summaries and handled-post ids are posted to your sheet.
- Supabase sync: if you enter your own project URL and key, the dedup memory is mirrored to your project.
Both are off by default and can be disconnected in Settings.
Permissions, in plain words
- x.com / twitter.com: to read posts and type into the reply box in your own tabs.
- api.openai.com: to generate replies with your key. youtube.com: to read a linked video's title for context.
- sheets.googleapis.com / script.google.com: only for the optional Sheets integration. *.supabase.co: the license service and your optional sync project.
- tabs / scripting / alarms / storage / sidePanel / unlimitedStorage: open and close the working tabs, keep a long run alive, store settings and memory, show the side panel.
This website
farm.uniquelabs.org is a static site hosted on Vercel. It sets no cookies and runs no analytics scripts; Vercel may keep standard, short-lived server logs. Fonts are loaded from Google Fonts.
Deleting your data
Remove the extension from Chrome to delete everything stored locally (use Settings → Danger zone → Total wipe first if you also want the x.com-side memory gone). To have your key, device and usage records removed from the license dashboard, message @abrarthecrypto on Telegram.