Privacy Policy
Effective October 22, 2026 · Last updated October 29, 2026
This policy explains what data Larkgrass collects, how we use it, who we share it with, and the choices you have. Larkgrass is operated by Hadungwra Brahma, who is the data controller for the Larkgrass service and this website.
Contact for privacy questions: [email protected]. Postal address: Kokrajhar, Assam 783370, India.
1. What we collect
| Data | Where it comes from | Why |
|---|---|---|
| Account: name, email, sign-in details, time zone | You, or Google when you sign in with Google | To create and secure your account |
| Your crew: agents, chats, files, routines, memory, rules, settings | You and your agents | To run the service you asked for |
| Connected app data (Gmail, Calendar, Drive, Slack, Notion and others) | The apps you connect | Only to do the tasks you give your agents |
| Usage: AI calls (model, provider and tokens, also on your own API keys, which never count toward your plan), computer time, plan, usage limit | The service | To apply your plan's weekly limit, keep the service running and understand how Larkgrass is used |
| Approximate country, and when you last used the app | Your IP address when you use the app (we keep only the country, not the address) | To understand where Larkgrass is used |
| Usage analytics: events about using the app (signing up and how you found us, such as the utm tags and referring site; signing in; agents created; runs completed or failed; routines; apps connected; billing steps; usage limit warnings; errors), and the minutes the app was open and visible | The service | To understand signing up and what people find useful, and keep the service reliable. You can turn it off (below). |
| Error reports: the kind of error and where in our code it happened, with ids, numbers and quoted text removed, and only your account id | Our servers, and the app in your browser | To find and fix problems |
| Billing: plan, payment status, customer ID, and a record of each payment, refund, dispute, plan change and trial charge | Dodo Payments | To know what you've paid for, keep billing accurate and keep accounts. We don't receive your full card details. |
| The paid first week: what you agreed to at checkout (the exact words shown, their version, whether you ticked the EU/EEA/UK box), your IP address, browser (User-Agent), billing country and the time | You, when you start the trial | To show what you agreed to, for example in a payment dispute or a consumer-law question |
| The paid first week: a random device ID (lg-device, below), and your payment card's network, last 4 digits and issuing country | Your browser, and Dodo Payments | To give each person, email address and device one trial. The card details are compared with other trials only to spot repeats; we never receive the full card number. |
| Technical: logs, IP address, browser type | Your browser and our servers | Security, debugging and abuse prevention |
| Visits to larkgrass.com: the page, the referring site, the country, the broad type of browser, system and device, the language and a visitor id that changes every day (below) | Your browser | To count visits and see how people find Larkgrass |
2. Cookies and similar storage
We use only the cookies and browser storage needed to sign you in, keep you secure and remember your settings. We don't use advertising or analytics cookies, or any third-party analytics or advertising trackers, so there's no cookie banner. We don't sell or share your data for advertising.
larkgrass.com
| Name | Type | Purpose | How long |
|---|---|---|---|
| lg-theme | Browser local storage | Remembers light or dark mode after you choose it | Until you clear it |
app.larkgrass.com
| Name | Type | Purpose | How long |
|---|---|---|---|
| sb-…-auth-token (may be split into .0, .1) | Cookie (Supabase Auth, for Larkgrass) | Keeps you signed in | Up to 400 days, or until you sign out |
| crew_sid | Cookie | Keeps you signed in when Larkgrass runs with local accounts (a self-hosted setup), instead of the cookie above | 30 days, or until you sign out |
| lg-terms-at | Local storage | Remembers when you agreed to the Terms and Privacy Policy on the sign-in screen, until it's saved to your account | Removed once saved |
| lg-drawer, lg-side | Local storage | Remember whether the side panel and sidebar are open or small | Until you clear it |
| lg-seen | Local storage | Remembers when you last looked at each chat, to show unread messages | Until you clear it |
| lg-seen-items | Local storage | Remembers when you last opened Tasks, Pages and each tracker, to mark what's new | Until you clear it |
| lg-tasks-view, lg-tracker-views, lg-ask-agent | Local storage | Remember the view you picked for Tasks and each tracker, and the agent you last asked | Until you clear it |
| lg-limit-hide-…, lg-upsell-hide-…, lg-storage-hide | Local storage | Remember which usage-limit, plan and storage notices you closed | Until you clear it |
| lg-device | Local storage | A random ID for this browser, sent only when you start the paid first week, so each device gets one trial. It doesn't identify you and isn't used for anything else | Until you clear it |
| lg-pick-plan | Session storage | Remembers the plan you picked on the pricing page while you sign up, so the app can show it | Until it's shown, or the tab is closed |
| larkgrass | IndexedDB (browser database) | A copy of your account as last shown (agents, chats, tasks), so the app opens at once, and changes waiting to be sent when you're offline | Removed when you sign out |
Security (both sites)
| Name | Type | Purpose | How long |
|---|---|---|---|
| __cf_bm | Cookie (Cloudflare) | Tells people apart from bots to protect the service | 30 minutes |
| cf_clearance | Cookie (Cloudflare) | Remembers that you passed a security check | Short, set by Cloudflare |
Bot check on sign-in. The app's sign-in page uses Cloudflare Turnstile to stop bots creating accounts. To do that, Cloudflare processes your IP address, your browser's TLS fingerprint and User-Agent, and which site the check is on. Cloudflare says these are used only to detect and block bots and to improve that detection, not to identify, profile or target anyone. See Cloudflare's Turnstile privacy addendum.
Usage analytics in the app. Our servers record events about using Larkgrass (for example signing up and how you found us, agents created, runs completed or failed, apps connected, billing steps and usage limit warnings) and the minutes the app was open and visible, linked to your account. They are kept in our own database (Supabase, Frankfurt, Germany). They never include your message text, file contents, email address, IP address or a browser fingerprint, and we use no cookies or browser storage for them. No outside analytics company receives them. Each day we send ourselves a summary email, and an alert email when something breaks (through Resend, our email provider). These contain counts, short account ids and error messages with email addresses, ids, numbers, quoted text and web addresses’ details removed; never your messages or files. We use them to understand signing up and what people find useful, and to keep the service reliable.
Turning it off. In the app, Settings → General → Share usage analytics. When it's off, we save no new events, sign-up source or active minutes for your account; we record only that you turned it off. Error reports, usage and cost records and billing records are still kept, because we need them to run the service and bill correctly.
Visitor stats on larkgrass.com. When a page on larkgrass.com loads, your browser sends us the page address (without any query), the referring site (its name only), and our server works out the country from your IP address and then discards the address. Visitors are counted with an id that is a one-way hash of your IP address, your browser and a random value that changes every day; that value is deleted after the day, so we can't recognise you from one day to the next, and no IP address is stored. We also keep the broad type of your browser, system and device (for example “Chrome, Android, mobile”) and the first language your browser asks for, never your browser’s full details. Bots and automated browsers are skipped. This uses no cookies and no browser storage, and no tracking cookies are set.
Payments happen on Dodo Payments' pages, which use their own cookies. See Dodo Payments' privacy policy.
Your choices. You can delete these in your browser settings at any time. Blocking the sign-in cookies stops you logging in. If we ever add optional cookies or outside analytics, we'll update this page first and, where the law requires it, ask your permission before using them.
3. How we use it, and our legal basis
- To provide Larkgrass (running your agents, storing your chats and files, applying your plan): this is needed to perform our contract with you.
- To keep it safe and working (security, fraud and abuse prevention, debugging): our legitimate interest in a secure service.
- To talk to you about your account, billing and important changes: contract and legitimate interest. Marketing emails only with your consent, and you can unsubscribe any time.
- To understand how Larkgrass is used and improve it (usage analytics in the app, and visitor stats on larkgrass.com): our legitimate interest in knowing how people find and use Larkgrass. You can turn off usage analytics for your account in Settings, or object by email.
- To meet legal duties such as tax and accounting, including payment records: contract and legal obligation.
We don't sell your personal information, we don't use it for advertising, and we don't use your content or connected app data to train AI models.
4. Data from Google
If you sign in with Google or connect Gmail, Google Calendar or Google Drive, Larkgrass receives the data you allow on Google's consent screen, such as your email messages, calendar events and files. Agents read and change that data only when a task you gave them needs it. Changes can wait for your approval, and you choose in Settings → Approvals which ones do. Auto-review lets a quick AI check allow low-risk ones, so check anything important.
Larkgrass's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In particular:
- We use Google user data only to provide and improve the features you use in Larkgrass.
- We don't transfer it to others, except to the processors listed below as needed to provide those features (for example an AI model provider that processes a request you made), for security, to comply with the law, or as part of a merger or sale with your consent.
- We don't use it for advertising, and we don't sell it.
- No person at Larkgrass reads it, unless you ask us to (for example in a support request), it's needed for security or to investigate abuse, it's required by law, or it's aggregated and anonymised.
- We don't use Google Workspace data (Gmail, Calendar, Drive) to develop, improve or train general AI or machine-learning models.
You can remove Larkgrass's access any time in Larkgrass (Connect apps) or in your Google Account under Security → Third-party connections.
5. Data from Slack
If you connect Slack, Larkgrass receives the workspace data you and your workspace allow, such as channels and messages, and uses it only to do the tasks you ask for. We don't use Slack data to train large language models or other AI models, we don't use one workspace's data for another, and we keep it only as long as a task needs it, except for messages and results your agents save in your Larkgrass chats and files. Your Slack workspace's administrators may also control which apps can be installed.
6. Who processes your data
We use these service providers (processors) to run Larkgrass. They may process your data only on our instructions and to provide their service to us.
| Provider | What for | Where |
|---|---|---|
| Supabase | Database and sign-in: your account, crew, chats, memory, settings and usage, and our own usage analytics | Frankfurt, Germany |
| OVH | The servers that run the app, your agents and the agents’ computer, and the files on it | Strasbourg, France |
| Cloudflare | Hosting this website, network security cookies, and the Turnstile bot check at sign-in | |
| Dodo Payments | Payments, as our merchant of record (it acts as the seller of record and controls the payment data it collects) | |
| Rapid Router | Routes each AI request to the company that runs the model you picked | Rapid Router is based in India; the model company may process the request in other countries, including the United States. |
| AI model companies, through Rapid Router (such as DeepSeek through DeepInfra, Z.ai, Anthropic, OpenAI and Google) | Process the messages, files and app data in each AI request your agents make, to produce the reply. Which one depends on the model you pick. | |
| Web search (DuckDuckGo, with Microsoft Bing as a fallback) | Answer the web searches your agents make. They get the search words only. | |
| Resend | Sending account emails (sign-in links and password resets), and a daily summary and alert emails to us with usage counts, short account ids and error messages with personal details removed | |
| Your own AI provider, if you add your own key | Requests on your key go straight to that provider, under your account with them |
If you add your own API key for a model, requests on that key go to that provider under your own account with them.
Site icons in the app are fetched by our server, so the icon service never sees your IP address.
7. Where your data is stored and processed
We store your account data with Supabase in Frankfurt, Germany, and run your agents and their computers on OVH servers in Strasbourg, France.
When an agent uses an AI model, the content that task needs (messages, files, app data) goes through Rapid Router to the company that runs that model, which may process it outside the European Union, including in the United States. Some other providers above (such as Cloudflare, Dodo Payments and Resend) may also process data in other countries.
Where the law requires, we rely on the safeguards in our providers' data processing terms, such as Standard Contractual Clauses.
8. How long we keep it
- Your crew, chats, files and settings: while your account is open, until you delete them.
- Connected app tokens: until you disconnect the app or delete your account.
- Usage and billing records: as long as tax and accounting laws require.
- Consent records from checkout (the terms you agreed to when you started a trial, a plan or a top-up, and when): kept after your account is deleted, as proof of what you agreed to, for as long as we may need them (for example for a payment dispute or a consumer-law question).
- A short note that your account was deleted (its ID and billing reference, so every part of Larkgrass finishes removing it): 30 days after the deletion is done.
- The email address, device ID and card details used to give one trial per person: for as long as we offer the paid first week, also after your account is deleted, so the same person can't start another trial. The device ID in your browser stays until you clear it.
- Usage analytics events, and the daily summaries of each account’s use worked out from them: 25 months. Minutes the app was open: 35 days. Error reports: 13 months after the error was last seen, and their daily counts 13 months. Our log of scheduled jobs: 90 days.
- Visits to larkgrass.com: 35 days; after that only daily totals, which don't identify anyone.
- Technical logs: up to 14 days.
- Backups: kept for up to 30 days, then deleted.
9. Deleting your account and data
You can delete any agent with its files from its Details, and remove any memory, chat files or connected app at any time.
You can delete your whole account yourself in Larkgrass: Settings → General → Delete account. It cancels your plan and deletes your account, crew, chats, files, memory, agent computers, saved sign-ins and connected app tokens from our live systems straight away. Copies in backups are gone within 30 days. We keep only what the law requires us to, or what we need as proof: billing records, and the consent records of what you agreed to at checkout. Your usage analytics are deleted with your account; payment amounts are kept for accounting without the link to you.
Or email [email protected] from your account's email address, and we'll delete it within 30 days.
10. Your rights
Depending on where you live (for example under the GDPR in the EU and UK, or the CCPA in California), you can ask to access, correct, delete or export your data, object to or restrict some uses, and withdraw consent. Email [email protected] and we'll answer within 30 days. You can also complain to your local data protection authority.
California residents: we don't sell or share personal information for cross-context advertising, and we don't use sensitive personal information beyond providing the service. We won't treat you differently for using your rights.
11. Security
We use encryption in transit, keep model API keys encrypted, limit who can access production systems, and isolate customers' data. No system is perfectly secure; if a breach affects your data we'll tell you as the law requires.
12. Children
Larkgrass isn't for children. You must be 18 or older to use it, and we don't knowingly collect data from children. If we learn an account belongs to someone under 18, we close it and delete its data.
13. Complaints and Grievance Officer
Grievance Officer: Hadungwra Brahma, [email protected]. Postal address: Kokrajhar, Assam 783370, India.
We acknowledge complaints within 24 hours and resolve them within 7 days. Requests to remove unlawful content are handled within 36 hours, and complaints about intimate images or impersonation of you within 2 hours. See how to make a complaint.
14. Changes
We'll post any changes here and update the date at the top. For significant changes we'll tell you by email or in the app first.
See also our Terms of Service and Refund policy.