Privacy Policy
LiveCrew works by reading what you write and sending it to AI models to generate a reply. That makes what we do with your data the central question about the product, not a footnote. This page answers it specifically rather than generically.
1. Who is responsible
LiveCrew is operated by Shamil Bedru, trading as LiveCrew, who decides how and why your data is used and is therefore the data controller.
Data questions and requests: privacy@livecrew.tech.
2. What this covers
The LiveCrew web app and the API behind it. It does not cover other companies’ sites we link to, including the ones listed in section 5, which have their own policies.
3. What we collect
| Category | What it is | Where it comes from |
|---|---|---|
| Account | Email address, a hashed password if you set one, the display name you choose, and the times you signed up and confirmed your email | You at sign-up, or your Google profile if you sign in with Google |
| Billing | Your subscription status, trial and billing period dates, the monthly price locked in when you subscribed, and Paddle’s identifiers for your customer record and subscription. Never your card number: that goes to Paddle and does not reach us | Paddle, as you check out and as your subscription changes |
| Workspace content | The startups you create, your messages, the agents’ replies, documents they write and their revision history, action items, meeting recaps, and your company profile | You and the agents, as you use the product |
| Derived memory | Rolling conversation summaries, extracted facts the agents use to remember context, and numerical embeddings of your content used for search and recall | Generated from your workspace content |
| Usage | Counts of messages and tokens against your plan limits, and per-response cost records | Measured as you use the product |
| Safety | When an automated check blocks a message: the reason, the rule or classifier label, and an excerpt of the message of up to 280 characters | The abuse screen described in section 6 |
| Technical | Server logs of each request: the method, the path, the response status, how long it took, and your user id. No IP addresses and no message content are written to logs | Automatically, as your browser makes requests |
| Product analytics | A small set of named events, such as an account being created or a message being sent, with the user id and a timestamp. The event records the fact, never the content | Recorded by our own server, in our own database |
| Web analytics | For each page view: which page, with any identifiers stripped out of it first, the site you arrived from, the country, region and city your network places you in, and your browser and device type. No cookie, no identifier that survives the day, and nothing joined to your account | Recorded by Vercel, our web host, as you browse |
| Feedback | What you type into the in-app feedback widget: the kind of feedback, your message, and which page you sent it from | You, only if you use the widget |
We do not ask for, and have no use for, your date of birth, your phone number, or where you are. The coarse location in the row above is inferred by our host from the network your request arrives on, the same way any web server can, and we never ask your browser for a precise position. Your card details go to Paddle, our payment provider, and never touch our servers. There is no advertising or cross-site tracking code anywhere in the app. Two third-party scripts run in your browser: Vercel’s page-view counter, which sets no cookie and cannot recognise you on a later visit, and Paddle’s, on the checkout page alone, because it is what takes your payment.
4. Why we use it, and on what basis
| Purpose | Data used | Lawful basis |
|---|---|---|
| Run the product you signed up for | Account, workspace content, derived memory | Performance of our contract with you |
| Sign you in and keep your account secure | Account, technical | Performance of our contract with you |
| Charge for the subscription, and honour your locked price | Account, billing | Performance of our contract with you |
| Enforce plan limits and keep costs survivable | Usage, billing | Our legitimate interest in a viable service |
| Detect and review abuse of the service | Safety, technical | Our legitimate interest in protecting the service |
| Understand which features are used, in aggregate | Product analytics | Our legitimate interest in improving the product |
| Count visits and see which pages people arrive on | Web analytics | Our legitimate interest in knowing whether anyone is finding us |
| Read and act on feedback you send us | Feedback | Our legitimate interest in improving the product |
| Send account emails: verification, sign-in, password reset | Account | Performance of our contract with you |
| Comply with the law, and respond to lawful requests | Whatever the obligation requires | Legal obligation |
We do not send marketing email, and we do not sell, rent, or trade your data.
5. Who else processes it
Running LiveCrew means passing data to other companies. These are all of them:
| Provider | What they do | What they receive |
|---|---|---|
| Supabase | Authentication, the database, and the account emails we send | Everything stored: account data and all workspace content |
| Moonshot AI | Generates the agents’ replies, meeting recaps, summaries, and extracted facts | Your messages and the surrounding conversation context needed to answer |
| OpenAI | Produces the embeddings behind search and memory recall, and handles some tool-heavy work | The text being indexed or worked on |
| Tavily | Web search, when an agent needs current information | The search query the agent forms, not your conversation |
| Paddle | Takes your payment as our merchant of record, and sends the receipts | Your email address, your card details, and what your browser sends to its checkout, such as your IP address |
| Vercel | Serves the web app, and counts page views for us | Request metadata such as IP address and browser, as any web host receives, plus the stripped-down page views described in section 3 |
| DigitalOcean | Hosts the API server | The same request metadata |
Each of them acts on our instructions for the purpose described, and each has its own terms and privacy policy governing what it does with what it receives. Paddle is the exception to the first half of that: as merchant of record it is the seller of the subscription and handles your payment data under its own responsibility, not on our instructions. We will update this table before adding a provider that receives your content.
One more party appears only if you choose it: signing in with Google tells Google that you use LiveCrew, and Google gives us the name and email address on your Google account. That exchange happens when you click the button, never before.
6. What the AI providers actually see
This is the part most privacy policies leave vague, so to be explicit. When you send a message, what goes to the model provider is: your message, recent messages in that conversation, summaries of older ones, facts the agents have extracted to remember context, the details of the startup you set up, and the instructions that give the agent its role.
Your email address, your password, and your session are never part of that. Nor is content from a different workspace, or anyone else’s account.
Before a message reaches a model, it is screened automatically for a narrow set of abuses, chiefly prompt injection and attempts to extract system instructions. Most of that screening is a local pattern check; genuinely ambiguous cases are sent to a small classifier model. If a message is blocked, we store the reason and an excerpt of up to 280 characters so we can review whether the block was correct. Those records are visible to the operator and to nobody else.
We do not train models on your content. We do not control what our providers do under their own terms, so we cannot make that promise on their behalf, only on ours.
7. Cookies
LiveCrew sets cookies for exactly three jobs, all strictly necessary, and none used for analytics or advertising:
- Session cookies set by Supabase, which keep you signed in, including the short-lived markers a Google sign-in needs to complete its round trip.
- A short-lived password-recovery marker, set only when you follow a password-reset link and cleared as soon as you set a new password or sign out.
- Paddle’s checkout cookies, set by its payment script on the subscribe page only, used to run the checkout and catch payment fraud, and governed by Paddle’s own policy.
The cookies we set ourselves are marked HttpOnly, so page scripts cannot read them, and SameSite=Lax, so another site cannot make your browser send them, and they are Secure in production. Paddle’s are set and read by its own script, which is why it appears here at all.
There is no advertising, cross-site tracking, or analytics cookie, and no consent banner, because every cookie here exists to sign you in or take your payment. Counting page views is done without one: that script stores nothing on your device and reads nothing from it, which is the thing a cookie banner exists to ask you about. Web fonts are bundled with the app rather than fetched from Google, so loading a page does not tell anyone else that you did.
8. How long we keep it
- Account data: while your account exists, and until deletion is completed after that.
- Workspace content: until you delete it. Deleting a workspace marks it deleted and hides it from the app, so an accident is recoverable; the underlying rows are removed when you ask us to delete your account or that content specifically.
- Server logs: short-lived, rotated by the host, and kept only for diagnosing faults.
- Safety records: kept while they are useful for abuse review, and removed with your account.
- Usage counters: kept for the current and preceding billing periods so limits can be enforced correctly.
- Billing records: our subscription mirror is removed with your account. Paddle keeps its own transaction records for as long as payment and tax law requires it to; that retention is theirs, not ours.
- Feedback: kept while it is useful for improving the product, and removed with your account.
- Web analytics: Vercel keeps the page-view counts. The marker that ties one visit’s pages together is discarded after 24 hours, so what remains is a count with nobody attached to it.
9. Your rights
You can ask us to:
- give you a copy of the data we hold about you
- send you your workspace content in a machine-readable form, which we will do on request
- correct anything inaccurate
- delete your account and its content, which we will complete within 30 days of confirming the request
- restrict or object to processing we do on the basis of legitimate interest
Email privacy@livecrew.tech from the address on your account. We may ask you to confirm it is you before acting, because acting on a forged deletion request would be worse than the delay.
Some of this you can do yourself: edit your display name, change your password, and delete workspaces, all in Settings. Account deletion is currently handled by email rather than a button.
If you think we have handled your data badly, tell us first. You also have the right to complain to the data protection authority in the country where you live.
10. Security
- All traffic runs over TLS.
- Passwords are hashed by Supabase Auth. We never see or store a password we could read.
- Session cookies are HttpOnly, so a scripting vulnerability cannot steal a session that outlives the page.
- Every user-facing database query runs under row-level security, so one account’s query cannot reach another account’s rows even if the application code is wrong.
- Access tokens are verified against the auth provider’s public keys on every API request.
- Changing your password signs out every other device.
No system is perfect. If we discover a breach affecting your data, we will tell you and the relevant authority as required, and we will tell you what we know rather than waiting until we know everything.
11. Age
LiveCrew is for adults, 18 and over. We do not knowingly collect data from anyone younger. If you believe a child has an account, email privacy@livecrew.tech and we will delete it.
12. Where processing happens
Our database and API server are hosted in Europe. The providers in section 5 operate internationally, so your data, including the content of your conversations, may be processed outside the country you are in. Where the law requires safeguards for those transfers, we rely on the contractual terms our providers offer.
If where your conversation content is processed matters to you, email privacy@livecrew.tech and we will tell you plainly, provider by provider, before you commit anything sensitive to the product.
13. Changes
When this policy changes materially, we will email account holders before it takes effect. The date at the top always reflects the current version.
14. Contact
Privacy questions, access requests, export requests, and deletion requests: privacy@livecrew.tech. Anything else: hello@livecrew.tech. The Terms of Service cover the rest of the agreement.