Andru Platform Privacy Policy

Last Updated: November 5, 2026
Effective Date: November 16, 2026


Plain Language Summary

What you need to know about your data:

We built Andru for technical founders who value authenticity and transparency. This Privacy Policy reflects those values by being honest about what data we collect, why we collect it, and how we protect it.

The essentials:

  • We collect what we need: Assessment responses, business context, and usage data to provide personalized recommendations
  • Your data stays yours: We never sell your individual business data to anyone, period
  • AI providers don't train on your data: Our primary AI provider (Anthropic) does not use API data for model training. Your product intelligence stays yours.
  • Security matters: Row-level database isolation, encrypted at rest and in transit, prompt injection defenses, and automated security monitoring
  • You have control: Access, export, or delete your data at any time. Deletion is permanent and cascades across all tables.
  • Transparency commitment: If our practices change materially, we'll tell you clearly and directly

Our values-driven approach:

Unlike platforms that monetize user data, we make money by actually helping you succeed. Your transformation is our business model, not your data.


1. Introduction

1.1 Who We Are

This Privacy Policy is provided by Humus & Shore, DBA Andru ("H&S," "we," "us," or "our"), the company behind the Andru revenue acceleration platform ("Platform").

Our Commitment:

We built the Platform with Empathy as a core value—people before profits. This extends to data practices. We collect only what serves your success, protect it carefully, and never make money from it: Andru is paid only for the work it does, from your prepaid wallet.

1.2 Scope of This Policy

This Privacy Policy applies to:

  • Information collected through the Andru Platform (web-based interface at platform.andru-ai.com)
  • Information collected through the Andru CLI (andru-intel npm package)
  • Information collected through the Andru MCP Server (Claude Desktop, Cursor, and other MCP clients)
  • Information collected when an AI agent calls Andru directly (A2A)
  • Information collected through the Andru Chrome Extension
  • Information collected through related communications (email, support)
  • Information processed when you use Platform features (assessments, recommendations, intelligence tools)

1.3 Your Consent

By using the Platform, you consent to the data practices described in this Privacy Policy. If you do not agree, please do not use the Platform.


2. Information We Collect

2.1 Information You Provide Directly

Account Information:

  • Name and email address
  • Company name and website
  • Job title and role
  • Payment information (processed by third-party payment processor)
  • Contact preferences

Company and Goals:

  • What you sell: your product's name, description and category, what sets it apart, and what your customers get
  • Your funding stage (for example, bootstrapping or seed)
  • Your next business milestone, and the biggest sales obstacle in its way, in your words or chosen from a list

You give these when you sign up, or later in chat or through an AI agent connected to Andru. We may draft the product answers from your website or an earlier assessment you took on andru-ai.com; they're used as yours only after you confirm or edit them.

Assessment Responses:

  • Revenue readiness evaluation answers
  • ICP (Ideal Customer Profile) definition data
  • Buyer persona information
  • Sales strategy details
  • Financial data (ARR, pricing, customer metrics)
  • Product capability descriptions
  • Market positioning information

2.2 Information Collected Automatically

Usage Data:

On andru-ai.com, for every page view: the page, how long it stayed open, how far you scrolled, which sections you read, the site that sent you, any campaign or link tags in the page's address (such as utm_source or src), the country your request came from (as our network provider reports it), and your browser and device type. We also record the buttons you click and their text, and the links you follow off our site (the site and page, never the rest of the address). When you copy text from a page, we record which section it came from and how much you copied, never the text itself. We never record what you type into a form. If you're signed in to Andru, the page sends us your sign-in so we can leave our own team's visits out of our counts. We check it and keep only whether the visit was ours.

On the diagnostics (such as the revenue intelligence and portfolio diagnostics), we record each step you start, answer and finish, with your answer's score, under a random ID that lasts until you close the tab. This happens with either cookie choice, and it isn't linked to your other visits.

On the platform, when you're signed in, we record each action you take (which page or feature, never what you typed), when you were last active (at most once every 5 minutes), the pages you open and the errors you run into. We keep this for 180 days, and deleting your account deletes it.

Technical Information:

  • IP address
  • Browser type and version
  • Operating system
  • Device type (desktop, tablet, mobile)

If you create an account, the pages you read on our sites before signing up are linked to it.

When you create an account, we keep where you came from with it. That's the site that sent you, the first and last times you arrived on our sites from somewhere else in the 30 days before (the page and the time), the page whose sign-up link you clicked, and any campaign or link tags in those addresses, such as utm_source or src. If you signed up through an AI app or agent, we also keep its name, as it names itself, and its answer if it told us how it found Andru. With “Necessary only”, this covers only the visit you signed up in. We keep this so we know which pages and links help people decide. We keep the site's name and the page, never the full address, and we don't use your IP address for it. Deleting your account deletes it.

When you create an account, our team may see the visits and automated fetches that anyone made to our sites in the 2 hours before, listed by time next to your email address in our internal chat: the page or file, the site that sent it, any link tag and the program's name as it reports it. These may not be yours. We don't use IP addresses for this. It isn't saved with your account, and deleting your account doesn't remove the chat message.

2.3 Cookies

We set one cookie of our own, andru_visitor_id, to recognise a returning browser across andru-ai.com and platform.andru-ai.com. We set it only if you choose “Accept all”, and it lasts one year.

With “Necessary only” we still count page views, time on page, how far you scroll and which sections you read. We don't connect one visit to the next, except that our team may see visits from the 2 hours before a signup next to that account, as described in section 2.2.

We also record which choice you made, so we know how many visitors accept.

andru-ai.com also uses PostHog, a product-analytics service, only if you choose “Accept all”. PostHog records the pages you view, how long you stay, the site that sent you, and on the diagnostics, when you start and finish and each answer's score. It also records where people click and scroll on a page, shown to us as a heat map, and a replay of how the page changed while you used it, with everything you type hidden. With these come your browser and device, technical details such as load times and errors, and your IP address, which PostHog uses to estimate your city and country. PostHog keeps this for 1 year, and replays for 30 days.

To check our own visitor counts, we also read and keep PostHog's daily count of visits to each page. These are counts only, with no names, IDs or devices, so they don't identify anyone. We keep them for 90 days.

To change your choice, clear this site's cookies and choose again.

2.4 IP Addresses

We record the IP address of each page view, each automated fetch of our pages, and each call to our API. We use it to spot and investigate attacks, scraping and fake sign-ups, and to check that a visit claiming to come from a known bot really does. We keep it for 30 days, then delete it. We don't use it to connect your visits. When a new API key makes its first call, we also check whether the same IP fetched our agent card or setup files in the 24 hours before, and how many IPs a program with the same name fetched them from in the last 7 days, so we can see how AI agents find Andru. We keep which of our files were fetched and when, never the IP.

For automated fetches by crawlers, AI assistants and other programs, we also record the page fetched, the program's name as it reports it, the site named in its Referer header, the country the request came from, whether the request was signed and by which agent, and what the fetch was for (search, training, or a person's request), so we can see how search engines and AI tools find and read our site. These records carry no cookie and aren't linked to anyone's visits, except as described above for an API key's first call, and except that our team may see those from the 2 hours before a signup next to that account, by time only (section 2.2).

If you choose “Accept all” on andru-ai.com, PostHog also keeps your IP address, as described in section 2.3.

2.5 Error Monitoring

The platform uses Sentry to tell us when something breaks. When an error happens, Sentry receives what went wrong, the page it happened on, your browser and device, and the platform's own log messages from your browser. Sentry doesn't keep your IP address.

Sentry also records a replay of how the platform's screens changed: in 1 of every 10 visits, and in every visit where an error happens. All text and everything you type is masked in the replay, and images are blocked, so the replay shows layout and clicks, not your content. We use replays only to find and fix problems. Sentry keeps errors and replays for 30 days.

Our backend also sends its own errors to Sentry.


3. How We Use Your Information

3.1 Primary Uses: Providing Platform Services

We use your information to:

Personalize Your Experience:

  • Generate customized recommendations based on your business context
  • Tailor framework guidance to your funding stage and growth trajectory
  • Point what we build for you at your next milestone and the sales obstacle in its way
  • Prioritize relevant content and resources
  • Create business cases and analysis specific to your situation

Operate Core Platform Features:

  • Process assessments and calculate scores
  • Provide comparative benchmarking (using anonymized aggregate data)
  • Generate reports and visualizations
  • Enable export and integration functionality

3.2 Aggregated and Anonymized Data

We may use aggregated, anonymized data to:

  • Create industry benchmarks (e.g., "Companies at your stage typically have X")
  • Develop case studies and success patterns (with all identifying information removed)
  • Produce research reports on revenue strategy trends
  • Improve AI/ML recommendation algorithms

What "anonymized" means:

Data is stripped of all identifying information—company names, individual names, specific financial figures, unique circumstances—making it impossible to trace back to you.


4. How We Share Your Information

4.1 We Do NOT Sell Your Data

Clear commitment: We do not and will never sell your individual business data to third parties. Period.

Andru is paid for the work it does, from your prepaid wallet, never by selling or monetizing your information.

4.2 Service Providers and Processors

We share information with trusted third-party service providers who help us operate the Platform:

  • AI Providers: Anthropic (primary), Google, Mistral, Groq and Fireworks (fallbacks). Your data is sent to these providers to generate intelligence (ICP profiles, competitive positioning, meeting briefs). Anthropic does not train on API data — your product intelligence is not used for model improvement. Fallback providers are used only when the primary provider is unavailable.
  • Database: Supabase (PostgreSQL on AWS, US region). All persistent customer data is stored here with row-level security.
  • Application Hosting: Render (US region). Backend API, agent platform, and MCP server hosting.
  • Payment Processing: Stripe for wallet top-ups and card payments
  • Email: Resend for transactional emails (account notifications, deletion confirmations)
  • Team chat: Slack, where our team gets internal notices about the service, including new accounts and what's described in section 2.2.
  • Frontend Hosting: Netlify hosts our websites and handles every request to them, including its IP address.
  • Error Monitoring: Sentry receives error reports and screen replays from the platform, as described in section 2.5.
  • Product Analytics: PostHog receives page views, click and scroll heat maps, and screen replays from andru-ai.com, only if you choose “Accept all” (section 2.3).

All service providers:

  • Are contractually obligated to protect your data
  • May only use data to provide services to us
  • Must comply with applicable privacy laws
  • Do not use your data for model training or their own purposes

For detailed information about our data processing practices, including sub-processor list and data transfer mechanisms, see our Data Processing Agreement available upon request at geter@andru-ai.com.


5. Data Security

5.1 Our Security Approach

Given that you entrust us with confidential business information, we implement comprehensive security measures:

Encryption:

  • Data in transit: TLS 1.2+ for all connections
  • Data at rest: AES-256 encryption (Supabase PostgreSQL on AWS)
  • Database encryption: All customer data encrypted at the storage layer

Data Isolation:

  • Row-Level Security (RLS) policies enforce tenant isolation — you can only access your own data
  • API-key-scoped sessions for CLI and MCP access — no shared state between customers
  • Each AI call is independent — your data never appears in another customer's prompt
  • Customer-supplied text in AI prompts is wrapped in structural boundaries to prevent prompt injection

Automated Security Monitoring:

  • SIEM event pipeline with real-time detection and automated containment
  • Daily database security audits (row-level security verification)
  • Dependency vulnerability scanning on every code change
  • Secret scanning to prevent accidental credential exposure
  • 15-minute uptime monitoring with automated incident response

Access Controls:

  • Role-based access: Team members access only data necessary for their role
  • API responses scanned for accidentally exposed secrets before delivery

6. Your Privacy Rights and Choices

6.1 Access Your Data

You have the right to:

  • Request a copy of all data we hold about you
  • Review your assessment responses and account information
  • Receive data in portable format (JSON, CSV)

6.2 Delete Your Data

You have the right to:

  • Delete your account at any time
  • Request deletion of specific assessment or pipeline data
  • Have your data permanently removed from all our systems

How deletion works:

  • Go to Settings → Account → Delete Account
  • You get a 3-day grace period — cancel by logging back in
  • After 3 days: permanent deletion cascade removes your data from every table in our database — profiles, assessments, ICP data, pipeline runs, generated resources, API keys, usage logs, and all AI-generated intelligence
  • Connected integrations (OAuth tokens) are revoked
  • Any wallet balance is forfeited and isn't refunded. Once your account is deleted, Andru stops all charges, including automatic top-ups, and a saved card is deleted at Stripe, our payment processor.
  • Authentication credentials are permanently removed
  • Transient cache data (Redis) expires automatically via TTL
  • Local MCP cache (on your device) is your responsibility to clear

Or contact geter@andru-ai.com to request deletion.


7. Contact Us About Privacy

Privacy & Data Inquiries: geter@andru-ai.com

Data Processing Agreement: Available upon request at geter@andru-ai.com


8. CLI and MCP Server Data Practices

The andru-intel CLI and mcp-server-andru-intelligence MCP server provide buyer intelligence tools in your terminal and AI coding tools (Claude Desktop, Cursor).

8.1 What Data Is Processed

  • Product descriptions, company names, and ICP criteria you provide as tool arguments
  • This data is sent to the Andru backend API for intelligence generation
  • AI calls are scoped to your API key — your data is never mixed with other customers' data

8.2 What We Record When You Use the CLI or MCP Server

Each call records which tool ran, whether it worked, what it cost, how long it took, which app made it (such as Claude Desktop or Cursor, as the app names itself) and the names of the inputs used. What you typed isn't part of this record. We use it to run and price the service, to fix problems, and to count how Andru is used (for example, which tools people come back to) so we can make it better. We keep this record for 180 days, and deleting your account deletes it.

When your app connects, the MCP server tells Andru once, so we can see connections that never call a tool. There are no other check-ins.

The request's IP address is kept for 30 days for security, as described in section 2.4.

The CLI and MCP server don't read files on your machine beyond the offline cache in 8.3.

8.3 Offline Cache

The MCP server may store recent results in a local SQLite cache on your machine for offline access. This data stays on your device and is your responsibility to manage. Clear it by deleting the cache file or reinstalling the package.

8.4 Calls from AI agents (A2A)

When an AI agent calls Andru over A2A, including to sign you up, we record each call: what it asked for, what Andru replied, which app made the call and whether it worked. Unlike the CLI and MCP record, this includes what the agent sent and what Andru sent back, such as company names and product details. API keys, sign-in codes and payment details are masked before anything is saved.

We use this record to run the service, to fix problems, and to count how Andru is used. We look at what was asked and replied only to investigate a specific problem on a specific account. The request and reply are deleted after 90 days. The rest of the record (which skill, whether it worked) is kept for 13 months. The IP address is kept for 30 days, as described in section 2.4. Deleting your account deletes these records.


9. Chrome Extension Data Practices

The Andru Chrome extension works on LinkedIn, in Gmail and on the page you have open. It sends something to Andru only when you ask it to, with three exceptions, described below: LinkedIn profiles, Andru in Gmail, and which of its features you use.

9.1 What the Extension Sends to Andru

LinkedIn profile read (automatically, when you open a LinkedIn profile while the extension is connected): the person's name, headline, current title, and the Experience and About sections of that profile. Andru uses them to suggest the person's likely role in your buying group. The read is saved in your account, so you can see it again and the same profile isn't read twice within 7 days. Andru doesn't read their posts, skills or recommendations.

First message (when you click “Write it”): the same profile details and the read. Saved in your account.

Tell Andru more: if you set someone's role, the role and the reasons you tick are saved in your account until you change them or delete your account.

Pre-meeting brief and account plan (when you click them): the company name, any contact name you enter, the site's domain, and a short summary of the page you have open (its title, description, main heading and up to 1,500 characters of its text). The extension never reads the text of a Gmail page. What you sent and the result are saved in your account.

Company fit score (right-click → “Score this company with Andru”, the toolbar button or the side panel): the company's domain and a short summary of that page. The score is saved in your account and reused for 30 days so the same company isn't scored twice. The page summary is not saved.

Andru in Gmail: Andru is off in each new email until you turn it on with its button. Once it's on, the text you are writing (not quoted earlier messages or your signature) is sent to Andru when you pause, to suggest changes. It is not saved. To count your free and paid emails, Andru keeps a random ID for each coached email, never its text. For a work address, Andru also uses the recipient's company domain for context.

To tailor suggestions, Andru also uses the recipient's name as Gmail shows it, people you've looked up with the extension, and anyone you've told Andru about. Who you tell Andru about is saved in your account until you change or delete it.

While Andru is off for an email, the extension compares the recipient's email domain with companies you've looked at in Andru, inside your browser, and if one matches, asks whether to turn Andru on. The address isn't sent to Andru unless you do.

9.2 Who Processes It

Everything is sent over HTTPS to the Andru API (api.andru-ai.com). To write reads, first messages, briefs, plans and email suggestions, Andru sends that content to the AI providers listed in section 4.2. They process it to produce the result and don't use it to train models. Nothing from the extension is sold or used for advertising.

9.3 Extension Permissions

  • storage: keeps your sign-in token, preferences and a short offline cache in your browser
  • activeTab and scripting: read the page you have open, only when you open the side panel, click the toolbar button or use the right-click menu
  • sidePanel: shows Andru beside the page
  • contextMenus: adds “Open Andru for this page” and “Score this company with Andru”
  • linkedin.com and mail.google.com: read the LinkedIn profile you open and show the Andru tab on it; show Andru in Gmail compose windows
  • platform.andru-ai.com: completes the Connect sign-in
  • api.andru-ai.com: the Andru API

9.4 Retention and Deletion

Reads, first messages, roles you set, briefs, plans and fit scores stay in your account until you delete your account, which removes them (section 6.2). Gmail text is not kept. Install records hold no browsing data; deleting your account deletes the ones linked to it. To clear what the extension stores in your browser, uninstall it or clear its data in Chrome settings.

9.5 Install and Usage Counts

When you install or update the extension, it sends Andru a random install ID and the version number. When you connect your account, that ID is linked to it. If you remove the extension, Chrome opens an Andru page that records the removal. Nothing about your browsing is included.

The extension records which of its features you use (for example, that a profile tab was shown or an email was sent with Andru on), never the text, addresses or pages involved. We keep these feature records for 180 days, and deleting your account deletes them.


Final Note: Privacy as Partnership

Privacy isn't just about compliance—it's about respect.

We built this platform to help technical founders transform their revenue processes through systematic, authentic approaches. That same authenticity extends to how we handle your data.

You're trusting us with:

  • Confidential business information
  • Strategic plans and roadmaps
  • Financial performance metrics
  • Competitive positioning details

We honor that trust by:

  • Protecting your data as if it were our own
  • Being transparent about our practices and limitations
  • Giving you control over your information
  • Never exploiting your data for purposes beyond serving you

If you have questions, concerns, or suggestions about our privacy practices, please reach out. We genuinely want to hear from you.


This Privacy Policy is drafted to balance legal compliance with H&S's values of Transparency and Empathy.