# Billing & Subscription Source: https://echo-docs.beau.to/billing ## Free trial Every new account starts with a **7-day free trial**. No payment is required to get started, but you'll need to enter a card when signing up. At the end of the trial, \$39/month is charged automatically. You can cancel any time before the trial ends to avoid being charged. ## Paid plan — \$39/month Your subscription renews automatically every month on your billing date. It includes: * 1,000 datapoints/month * Real-time dashboard updates * All built-in Rule templates * 24-hour data history (extendable) ## 30-day money-back guarantee If Echo isn't working for you, email [i@beau.to](mailto:i@beau.to) within 30 days of your first charge and we'll refund you in full — no questions asked. This applies once per account and doesn't apply to renewals. ## Cancellation You can cancel at any time from account Settings. Your subscription stays active until the end of the current billing period. After that: * Echo stops processing new emails * Your dashboard is no longer updated * **All extracted datapoints are deleted immediately** If you reconnect later, Echo will start fresh — historical datapoints are not recoverable. ## Payment Payments are processed by Stripe. Echo never stores your card number or CVV. You can update your payment method at any time from account Settings. ## Questions or billing issues Contact the Echo team at [i@beau.to](mailto:i@beau.to) — we aim to respond within 5 business days. # Datapoints & Limits Source: https://echo-docs.beau.to/datapoints-and-limits A datapoint is one piece of actionable information extracted from an email. Each time Echo finds something worth surfacing — an amount, a deadline, a promo code, a status — that's a datapoint. ## How datapoints are counted One email can produce multiple datapoints depending on how much structured data it contains. | Email | Datapoints | | ------------------------------------------------------ | ---------- | | Invoice #2024-0415 → \$2,340 due Apr 18 | 3 | | Slack renewal → annual plan, \$156/year, expires Dec 1 | 3 | | Office lease reminder → deadline Aug 31 | 1 | | Promo code email → XMAS26 for 25% off | 2 | Most emails generate between 1 and 5 datapoints. Emails with no relevant data don't count toward your limit. ## Monthly limit Each plan includes **1,000 datapoints per month**. This is enough for roughly 300–500 relevant emails analyzed. The limit resets at the start of each billing cycle. ## What happens when you hit the limit Once you reach 1,000 datapoints, Echo stops processing new emails for the rest of the month. Emails that arrive after the limit is reached are not analyzed and won't appear on your dashboard — even retroactively once the limit resets. > If you're approaching your limit, consider reviewing your Rules. A Rule that's too broad may be extracting datapoints from emails you don't actually care about. ## How to stay within your limit * **Use specific Rules.** The more precise your prompt, the fewer irrelevant emails get processed. * **Monitor your usage.** You can see how many datapoints you've used this month in your account settings. * **Delete unused Rules.** Rules you no longer need keep consuming datapoints on every matching email. ## Need more? If 1,000 datapoints/month isn't enough for your inbox volume, contact the Echo team at [i@beau.to](mailto:i@beau.to) to discuss options. # Flights Source: https://echo-docs.beau.to/flights ```markdown expandable theme={null} You are a flight dashboard renderer. You receive pre-extracted schema.org JSON from an email and your job is to produce a clean, human-readable flight itinerary table with alert flags. ## INPUT Schema.org JSON array extracted from an email. ## STEP 1 — DETERMINE IF FLIGHT-RELATED This email is flight-related if it contains ANY of: - Flight booking confirmation or e-ticket - Boarding pass or check-in reminder - Flight status update (delay, cancellation, gate change) - Itinerary from airline or travel agency (Expedia, Booking.com, Google Flights, etc.) - Frequent flyer / miles notification related to a specific flight - Upgrade confirmation or offer tied to a booking - Visa or travel document reminder tied to a flight If NOT flight-related, return exactly: NOT_FLIGHT ## STEP 2 — RENDER THE TABLE If flight-related, output a table with these columns: | Flight | Route | Departure | Arrival | Terminal / Gate | Booking Ref | Status | Alerts | |--------|-------|-----------|---------|-----------------|-------------|--------|--------| Rules per column: **Flight**: Airline name + flight number. E.g. "United UA 452". If codeshare, show both. If unknown, write "—". **Route**: "JFK → LAX". Use IATA codes where possible. If layover, show full chain: "JFK → LHR → BKK". **Departure**: Format as "MMM DD, HH:MM (timezone)". E.g. "Mar 15, 06:45 (EST)". If timezone unknown, omit it. **Arrival**: Same format as Departure. If next-day arrival, add "+1". E.g. "Mar 16, 08:20 (GMT) +1". **Terminal / Gate**: "T2 / G14". If not yet assigned, write "TBA". If unknown, write "—". **Booking Ref**: Confirmation / PNR code exactly as written. E.g. "XJ49KL". If none found, write "—". **Status**: - ✅ Confirmed - 🟡 Check-in open - 🛫 Departed - 🛬 Arrived - 🔴 Cancelled - ⚠ Delayed - ❓ Unknown Determine automatically. If departure time is in the past → Departed or Arrived. If cancellation mentioned → Cancelled. If delay mentioned → Delayed. If check-in window is open based on today's date → Check-in open (typically 24hrs before departure). **Alerts**: Short flags. One per line. Examples: - ⏰ Check-in opens Mar 14 at 06:45 - 🚪 Gate closes 30 min before departure - 🔄 Connecting flight: 1h 20m layover at LHR - ⚠ Short layover: under 60 min - 🧳 Baggage: 1 checked bag included (23kg) - 💺 Seat: 14A (window) - ✈ Operated by: Lufthansa (codeshare) - 📋 Visa required for transit through UK - 🔔 Flight delayed 45 min (inferred from update email) Leave blank if no alerts apply. Omit any field that is not present in the source data. Do not invent values. If a field is inferred (not explicitly stated), add "(inferred)" after the value. ## RULES - No preamble, no explanation, no JSON. - If multiple flights in one email (round trip, multi-city, group booking), render each flight segment as a separate row + separate detail card. - Never invent data. If a value is missing, use "—" in the table and omit the field in the detail card. - Dates use the email's received date as "today" for all relative calculations. - For layovers under 60 minutes, always add a ⚠ short layover alert. - Always preserve booking reference / PNR exactly as written including capitalization. - If multiple passengers on one booking, list all names in the detail card. ``` # Getting Started Source: https://echo-docs.beau.to/getting-started Echo is a Chrome extension that turns your Gmail into a live dashboard — visible every time you open a new tab. No need to check your inbox manually: invoices, deadlines, flight details, promo codes, and anything else you care about are always in front of you. ## Install the extension Download Echo from the [Chrome Web Store](https://chromewebstore.google.com/detail/echo-gmail-inbox-insights/bdgklmihpalglaamaaonceocgjijhgab?authuser=0\&hl=en) and install it in one click. Once installed, every new tab in Chrome will show your Echo dashboard instead of the default page. ## Set up your account After installing, you'll be redirected to [echo.beau.to/login](https://echo.beau.to/login) to create an account and [connect your Gmail](/welcome). From there, follow the steps to create your first Rule and start seeing data. > **Note:** Echo is currently in closed beta and not yet verified by Google. When connecting Gmail, you may see a warning screen — click "Advanced" → "Go to Echo (unsafe)" to proceed. This is normal for apps awaiting Google verification. # How Rules Work Source: https://echo-docs.beau.to/how-rules-work A Rule is a plain-English prompt that tells Echo what to extract from your emails. Every time a new email arrives, Echo runs it through each of your active Rules and pulls out the relevant data — amounts, dates, names, statuses — and surfaces them on your dashboard. ## The basic flow 1. A new email lands in your Gmail inbox 2. Echo sends it to each of your active Rules 3. Each Rule's prompt is applied to the email by LLM 4. If something relevant is found, the extracted datapoints appear on your dashboard 5. If nothing matches, the email is silently skipped ## One Rule, one job Each Rule is focused on a single type of data. You might have one Rule for invoices, another for flight confirmations, and another for promo codes — all running in parallel on every incoming email. There's no limit to how many Rules you can have active at the same time. ## What a Rule looks like A Rule is just a prompt. You describe what you're looking for, and Echo handles the rest. You can use one of Echo's built-in templates (Invoices, Flights, Taxes, Offers, etc.) or write your own from scratch. Custom Rules follow the same format — describe what the email looks like, what data to extract, and how to display it. ## What Rules don't do (yet) Rules currently apply to **all incoming emails**. There are no sender, subject, or date filters — the prompt itself is how Echo decides whether an email is relevant. If the email doesn't match, Echo returns nothing and moves on. > **Note:** Rules only process new emails from the moment they're created. Emails already in your inbox before a Rule was set up are not scanned retroactively. ## Tips for writing good Rules * **Be specific about what you want.** "Extract the invoice amount, due date, and vendor name" works better than "find payment info." * **Tell Echo what to do when data is missing.** For example: "If no due date is found, write —." * **Use the built-in templates as a starting point.** They're designed to handle the most common cases out of the box. # Invoices Source: https://echo-docs.beau.to/invoices ```markdown expandable theme={null} You are an invoice dashboard renderer. You receive pre-extracted schema.org JSON from an email and your job is to produce a clean, human-readable invoice table with alert flags. ## INPUT Schema.org JSON array extracted from an email. ## STEP 1 — DETERMINE IF INVOICE-RELATED This email is invoice-related if it contains ANY of: - A payment request with an amount - Invoice / bill / receipt / statement - "Amount due", "balance due", "total due", "please pay" - Invoice number tied to a payment - Payment confirmation or receipt - Overdue notice, reminder, late fee warning - Subscription renewal charge ## IF INVOICE-RELATED: STEP 2 — RENDER THE TABLE If invoice-related, output a table with these columns: | Vendor | Invoice # | Amount | Due Date | Status | Alerts | |--------|-----------|--------|----------|--------|--------| Rules per column: **Vendor**: Company or person name. If unknown, use sender email domain (e.g. "acme.com") **Invoice #**: Invoice / order / bill number. If none found, write "—" **Amount**: Format as currency symbol + amount. E.g. "$1,200.00". If multiple line items, show total. If unknown, write "?" **Due Date**: Format as "MMM DD, YYYY". If already past, add ⚠ before the date. If unknown, write "—" **Status**: - ✅ Paid - 🔴 Overdue - 🟡 Due soon (within 7 days) - ⚪ Unpaid - ❓ Unknown Determine status automatically from available data. If payment confirmation is present → Paid. If due date is in the past → Overdue. If due date is within 7 days → Due soon. **Alerts**: Short, specific, plain-English flags. One per line. Examples: - ⚠ Late fee: 2%/month after Apr 18 - 🔁 Recurring: charges monthly on the 1st - 📎 PDF attached - 💳 Auto-charge: card ending 4242 - ❗ No due date found Leave blank if no alerts apply. Omit any field that is not present in the source data. Do not invent values. If a field is inferred (not explicitly stated), add "(inferred)" after the value. ## RULES - No preamble, no explanation, no JSON. - If multiple invoices are found in one email (e.g. forwarded thread), render each as a separate row. - Never invent data. If a value is missing, use "—" in the table and omit the field in the detail card. - Dates use the email's received date as "today" for all relative calculations. ``` # Offers & Discounts Source: https://echo-docs.beau.to/offers ```markdown expandable theme={null} You are a discounts and offers dashboard renderer. You receive pre-extracted schema.org JSON from an email and your job is to produce a clean, human-readable summary of promotions, deals, and savings opportunities. ## INPUT Schema.org JSON array extracted from an email. ## STEP 1 — DETERMINE IF DISCOUNT/OFFER-RELATED This email is offer-related if it contains ANY of: - Promotional or discount codes (promo, coupon, voucher) - Limited-time sales, flash deals, or seasonal offers - Loyalty rewards, cashback, or points expiring/available - Free trial extensions or upgrade offers - Early bird pricing or renewal discounts - Credits, gift cards, or store balance notifications - Bundle deals or referral bonuses - Price drop alerts on previously viewed/purchased items If NOT offer-related, return exactly: NOT_OFFER ## STEP 2 — RENDER THE OFFERS For each offer found, output a row in this table: | Sender | Offer | Code | Value | Expires | Status | Alerts | |--------|-------|------|-------|---------|--------|--------| Rules per column: **Sender**: Brand or company name. E.g. "Adobe Creative Cloud", "AWS", "Slack Pro". If unknown, use the email sender domain. **Offer**: One-line plain English description of what's being offered. E.g. "25% off annual renewal", "$2,000 in promotional credits", "Free 3-month extension". Keep it under 12 words. **Code**: Promo/coupon/voucher code exactly as written, preserving capitalization. E.g. "XMAS26", "SAVE30". If no code needed, write "Auto-applied". If none, write "—". **Value**: Quantified savings if determinable. E.g. "$50 off", "25%", "3 months free", "2,000 credits". If unclear, write "Variable". **Expires**: Date or relative deadline. Format as "MMM DD, YYYY" if explicit. If relative ("ends this week"), infer from email received date. If no expiry found, write "—". If expiry is within 72 hours, flag as "⚠ MMM DD". **Status**: - 🟢 Active — offer is valid and not yet claimed - 🟡 Expiring soon — expires within 72 hours - 🔴 Expired — expiry date has passed (based on today's date) - 🔵 Claimed — confirmation that offer was already used - ❓ Unknown — no expiry or status info Determine automatically using the email's received date as "today". **Alerts**: Short flags, one per line. Examples: - ⏰ Expires in 2 days — act before Mar 18 - 🔁 Renewal offer — applies only on annual plan upgrade - 💳 No code neede ``` # Open Source & Transparency Source: https://echo-docs.beau.to/open-source **Echo is built in the open.** We welcome contributions from the community. * Want to modify a rule template? Add a new integration? Build your own features? Fork the repo and make it yours. * You can inspect exactly how Echo processes your emails. No black boxes, no hidden data collection. * Security researchers and developers worldwide can audit our code, report vulnerabilities, and suggest improvements. **Community-Driven (coming soon)** * Submit pull requests to improve extraction algorithms * Share custom rule templates with other users * Contribute plugins for new data sources (Slack, calendar, CRM) * Localize the interface to your language **Self-Hosting (coming soon)** * Run echo on your own infrastructure if your company has strict data policies. Full control, zero compromises. OWN LLMS? ## Get Involved * **GitHub:** [https://github.com/beau-to/echo](https://github.com/beau-to/echo) — Star the repo, open issues, contribute code * [**\[Roadmap: echo.beau.to/roadmap — Vote on features, suggest ideas\]**](https://echo.beau.to/roadmap) **Open source means you're not locked in.** If you don't like how we handle something, you can change it. If we shut down tomorrow, you can keep using Echo. This is your data, your tool. # Parcels Source: https://echo-docs.beau.to/parcels # Pricing Source: https://echo-docs.beau.to/pricing ### Pricing is based on value extracted, not emails processed. Discount price for beta access: \$39/month (7-day free trial, 100 datapoints limit) **What you get:** * 1,000 datapoints/month (\~300-500 relevant emails analyzed) * Real-time dashboard updates ## Why is beta paid? Echo processes every email through large language models to extract structured data. Unlike traditional email filters, we analyze context, relationships, and meaning which requires significant AI compute. Token costs scale with your inbox volume, so we need to cover infrastructure costs even during beta testing. # What's a datapoint? A datapoint is one actionable insight from your inbox. Examples: * Invoice #2024-0415 → \$2,340 due Apr 18 = 3 datapoints * Slack renewal notice → annual plan, \$156/year, expires Dec 1 = 3 datapoints * Office lease reminder → Aug 31 deadline = 1 datapoint * Promo code email → XMAS26 for 25% off = 2 datapoints Most emails generate 1-5 datapoints. Only the ones with actual data matter. *** # Privacy & Security Source: https://echo-docs.beau.to/privacy-and-security **⚠️ Echo is in closed beta for 100 first users and not yet verified by Google.** This means when you connect Gmail, you'll see a warning screen from Google. This is normal for apps in development. **What this means for you:** * Google hasn't completed their verification process yet (we're in queue) * You'll need to click "Advanced" → "Go to Echo (unsafe)" during setup * Echo still uses Google's OAuth security standards **What Echo can and cannot do:** ✅ **Echo CAN:** * Read your emails (to extract datapoints) * Access email metadata (sender, date, subject) ❌ **Echo CANNOT:** * Send emails on your behalf * Delete or modify your emails * Share your data with third parties * Access anything outside Gmail **Where is your data stored?** * ???BODY??? PREVIEW ONLY FOR UI FEATURE Email content: Never stored. Processed in memory, discarded immediately. * Extracted datapoints: Stored on our servers (AWS US-East). * Your Gmail credentials: Never stored. Only OAuth tokens (revocable anytime). **How to revoke access:** Go to [Google Account → Security → Third-party access](https://myaccount.google.com/permissions) and remove Echo. Your dashboard will stop updating, but we'll keep your extracted datapoints for 30 days in case you reconnect. # Privacy Policy Source: https://echo-docs.beau.to/privacy-policy **Beaux, Inc.** | Effective: January 22, 2026 | Last Updated: March 3, 2026 *** Echo is an email intelligence Chrome Extension operated by Beaux, Inc. It reads your Gmail inbox, extracts key datapoints using AI, and displays them as a live dashboard on your new tab page. This Privacy Policy explains exactly what data we collect, how it is processed, and the rights you have over it. By installing the Echo Chrome Extension and connecting your Gmail account, you agree to the practices described below. *** ## 1. What Echo Does Echo replaces your Chrome new tab page with a live inbox dashboard. It continuously reads incoming Gmail emails, extracts structured datapoints (amounts, dates, names, statuses), and surfaces them in real time — without you opening a single thread. The extension communicates exclusively with Echo's own servers. It does not interact with any other website you visit and does not inject scripts into third-party pages. *** ## 2. Information We Collect ### 2.1 Information You Provide * **Email address** — for account creation and authentication * **Payment information** — processed by Stripe; we never store full card numbers or CVV codes * **Gmail OAuth token** — used to access your inbox with read-only permissions; revocable at any time ### 2.2 Information We Process Automatically * **Email content** — full email bodies are sent to our AI pipeline to extract datapoints. Raw email content is never stored after processing is complete; it is processed in memory and discarded immediately * **Email metadata** — sender, recipient, subject line, date, and Gmail labels * **Extracted datapoints** — dates, amounts, names, statuses, and other structured data derived from your emails; these are stored and power your dashboard * **Usage data** — dashboard views, Rules created, sync events, and feature interactions * **Technical data** — browser type, IP address, and operating system, collected via Google Analytics ### 2.3 What We Do NOT Collect * We do not store raw email content * We do not collect your browsing history outside of Echo * We do not track the websites you visit * We do not collect keystrokes, mouse movements, or screen activity *** ## 3. How We Use Your Information * **Provide the Service** — process emails, extract datapoints, and generate your live dashboard * **Process payments** — manage billing and subscriptions via Stripe * **Improve accuracy** — analyze anonymized usage patterns to improve AI extraction quality; no email content is used for this purpose * **Communicate with you** — account notifications, product updates, and support responses * **Ensure security** — detect and prevent fraud, abuse, or unauthorized access *** ## 4. AI Processing & Data Handling ### 4.1 How It Works When you create a Rule — a prompt that defines what data to extract — Echo reads the relevant emails from your Gmail and sends full email content to our AI provider for processing. Only the resulting structured datapoints are stored. Raw email content is processed in memory and discarded immediately after extraction completes. ### 4.2 Our AI Provider * **Provider:** Anthropic (Claude API) * **What is sent:** Full email content for emails matching your active Rules * **Anthropic data retention:** Anthropic does not train models on API customer data. Email content is not retained by Anthropic beyond the duration of the API call * **Encryption in transit:** All data sent to Anthropic is encrypted via HTTPS/TLS ### 4.3 Third-Party Service Providers We share limited data with trusted vendors solely to operate Echo: | Vendor | Purpose | Receives email data? | | -------------------- | --------------------------------------- | ---------------------- | | **Anthropic** | AI extraction via Claude API | Yes, transiently | | **Stripe** | Payment processing | No | | **AWS (US-East)** | Infrastructure and database hosting | Yes, encrypted at rest | | **Google Analytics** | Aggregated, anonymized usage statistics | No | We never sell your data to third parties, share email content with advertisers, or use your information for any purpose beyond Echo's core functionality. *** ## 5. Chrome Extension Specifics ### 5.1 Permissions Used | Permission | Why it's needed | | ------------------------ | ------------------------------------------------------ | | `identity` / Gmail OAuth | To access your Gmail inbox with read-only permissions | | `storage` | To cache your dashboard data locally in Chrome Storage | | `tabs` / `newtab` | To display the Echo dashboard on every new tab | No permissions beyond those listed above are requested. We do not request access to your browsing history, bookmarks, or any other Chrome data. ### 5.2 Local Chrome Storage The extension stores your dashboard cache locally in Chrome Storage only. This data never leaves your device except to sync with Echo's own servers. It is not accessible to other extensions or websites. ### 5.3 Remote Code Echo makes API calls to Anthropic's Claude API and Echo's own backend to process emails and retrieve dashboard data. No executable code is loaded remotely into the extension itself; all extension logic is bundled in the published package. ### 5.4 New Tab Override Echo replaces your Chrome new tab page with your inbox dashboard. This is the extension's sole interaction with your browser UI. It does not modify any other browser behavior. *** ## 6. Data Storage & Security ### 6.1 What We Store * **Extracted datapoints** — stored encrypted in PostgreSQL on AWS (US-East) * **Email content** — not stored; processed in memory and discarded after extraction * **OAuth tokens** — stored encrypted; never logged in plain text * **Account data** — email address, billing history, and settings * **Cache data** — temporary session and job data stored in Redis; automatically expires and is never written to long-term storage ### 6.2 Security Measures * All data in transit is encrypted via HTTPS/TLS * Data at rest is encrypted at the database level on AWS * Access to production systems is limited to authorized personnel and fully logged * Gmail access is strictly read-only — Echo cannot send, delete, or modify your emails ### 6.3 Data Retention * **Active accounts:** Data retained as long as your account is active * **Deleted accounts:** All data permanently removed from production systems within 30 days of deletion * **Backups:** Retained for 30 days for disaster recovery, then permanently deleted * **Server logs:** Retained for 90 days for security and debugging purposes *** ## 7. Your Rights & Choices ### 7.1 Access & Control You can: * View all extracted datapoints in your Echo dashboard * Revoke Gmail access at any time via [Google Account Security Settings](https://myaccount.google.com/permissions) or Echo Settings — this immediately stops all inbox processing * Delete your account in Echo Settings; all data is permanently removed within 30 days To request a copy of your data, contact [i@beau.to](mailto:i@beau.to). ### 7.2 GDPR Rights (EU Users) If you are in the European Union, you have the right to: * Access your personal data * Correct inaccurate data * Request erasure ("right to be forgotten") * Restrict or object to processing * Receive your data in a portable format * Withdraw consent at any time Contact [i@beau.to](mailto:i@beau.to) to exercise any of these rights. We will respond within 30 days. **Legal basis for processing:** * **Consent** — you authorize Gmail access when connecting your account * **Contractual necessity** — to deliver the Echo service you have signed up for * **Legitimate interests** — to improve service quality, ensure security, and prevent fraud ### 7.3 CCPA Rights (California Users) If you are a California resident, you have the right to know what personal information we collect and how it is used, to request deletion, and to opt out of data sales. We do not sell your personal information. Contact [i@beau.to](mailto:i@beau.to) to exercise these rights. We will respond within 45 days. *** ## 8. Google API Services Compliance Echo's use of Gmail data adheres to the [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy), including all Limited Use requirements: * Echo uses Gmail data exclusively to provide the email intelligence features you have requested * Gmail data is not transferred to third parties except to Anthropic for AI extraction, which is necessary to provide the service * Gmail data is never used for advertising purposes * No Echo employee reads your Gmail data, except to investigate a specific security or compliance issue, or with your explicit consent *** ## 9. Cookies & Tracking We use essential cookies for authentication and session management — these cannot be disabled without breaking core functionality. We also use Google Analytics cookies to understand aggregate usage patterns; you can block these via your browser settings without affecting Echo's core features. *** ## 10. Children's Privacy Echo is not intended for users under 13 years of age (or 16 years in jurisdictions where a higher minimum age applies). We do not knowingly collect personal information from children. If you believe a child has provided information to Echo, contact [i@beau.to](mailto:i@beau.to) and we will delete it immediately. *** ## 11. International Data Transfers Echo is operated from the United States and data is stored on AWS infrastructure in the US-East region. If you access Echo from outside the United States, your data will be transferred to and processed in the United States. We ensure appropriate safeguards are in place for international transfers, including for users in the EU and UK. *** ## 12. Data Breach Notification In the event of a data breach affecting your personal information, we will: * Notify affected users within 72 hours * Report to relevant authorities as required by applicable law * Provide clear guidance on how to protect your account *** ## 13. Open-Source Notice Echo's core engine is open-source and available on GitHub. This Privacy Policy applies to the hosted Chrome Extension version of Echo. If you choose to self-host Echo using the open-source codebase, you are responsible for your own data handling practices and this policy does not apply to your self-hosted instance. *** ## 14. Changes to This Policy We may update this Privacy Policy from time to time. If changes are material, we will notify you by email at least 30 days before they take effect and post a prominent notice in the extension. Continued use of Echo after changes take effect constitutes acceptance of the updated policy. *** ## 15. Contact Us **Email:** [i@beau.to](mailto:i@beau.to) **Address:** Beaux, Inc., 2261 Market Street #4410, San Francisco, CA 94114 **Response time:** We aim to respond within 5 business days *** ## Appendix: Sub-Processors | Sub-Processor | Location | Purpose | | ------------------- | ----------------------- | ------------------------------------- | | Anthropic, PBC | United States | AI datapoint extraction | | Amazon Web Services | United States (US-East) | Infrastructure, database, and storage | | Stripe, Inc. | United States | Payment processing | | Google LLC | United States | Analytics (anonymized) | *** *Version 1.0 | Last reviewed: March 3, 2026* # Supported Data Types Source: https://echo-docs.beau.to/supported-data-types Echo extracts structured data from your emails and PDF attachments. Anything written in plain text can be picked up — if it's in the email body or an attached PDF, Echo can read it. ## What Echo extracts Echo pulls out the types of data that naturally appear in emails: things like amounts, dates, names, and statuses. More specifically, Echo works with data that maps to standard schema.org types — a widely used vocabulary for describing real-world information. In practice, this means Echo can extract: * Amounts & prices — invoice totals, subscription fees, refund amounts * Dates & deadlines — due dates, expiry dates, flight times, tax deadlines * Names & organizations — vendors, senders, airlines, tax authorities * Reference numbers — invoice numbers, booking codes, PNR, tracking IDs * Statuses — paid, overdue, confirmed, delayed, cancelled * Promo codes & offers — discount codes, expiry, savings value * Addresses — billing addresses, delivery addresses * URLs & links — payment links, tracking pages * and more If a value appears as readable text in an email, there's a good chance Echo can extract it. ## PDF attachments Echo reads text from PDF attachments automatically, no setup needed. This includes invoices, receipts, boarding passes, and tax notices sent as attached files. > Images and scanned documents are not supported. Echo can only extract text it can read directly, not content embedded in photos or non-searchable PDFs. ## What Echo doesn't extract * **Images** — logos, photos, banners, and image-based content are ignored * **Scanned PDFs** — if the PDF is a photo of a document (non-searchable), Echo can't read it * **Data outside the email** — Echo only reads what's in the email body and its attachments, nothing else ## A note on accuracy Echo uses AI to interpret context, not just copy text. This means it can infer a status ("this invoice is overdue") or normalize a format ("€1.200,00" → "\$1,200.00") — but it can also make mistakes. Always verify critical data against the original email. # Taxes Source: https://echo-docs.beau.to/taxes ```markdown expandable theme={null} You are a tax deadline dashboard renderer. You receive pre-extracted schema.org JSON from an email and your job is to produce a clean, human-readable tax deadline table with alert flags. ## INPUT Schema.org JSON array extracted from an email. ## STEP 1 — DETERMINE IF TAX-RELATED This email is tax-related if it contains ANY of: - Tax filing deadline or due date (income tax, VAT, sales tax, corporate tax, estimated tax) - Payment request from a tax authority or accountant - Tax return status update (accepted, rejected, processing) - Notice from IRS, HMRC, or any national/local tax authority - Estimated tax payment reminder (quarterly payments) - Tax refund notification - Penalty or interest notice related to taxes - Request for documents (W-2, 1099, receipts) for tax purposes - Tax extension confirmation or deadline - VAT registration, filing, or payment notice ## STEP 2 — RENDER THE TABLE If tax-related, output a table with these columns: | Authority / Sender | Tax Type | Amount Due | Deadline | Status | Alerts | |--------------------|----------|------------|----------|--------|--------| Rules per column: **Authority / Sender**: Tax authority or accountant name. E.g. "IRS", "HMRC", "State of California FTB", "Deloitte (accountant)". If unknown, use sender email domain. **Tax Type**: E.g. "Federal Income Tax", "Q2 Estimated Tax", "VAT Return", "Corporate Tax", "Sales Tax", "Tax Extension". If unclear, write "Tax Filing". **Amount Due**: Format as currency symbol + amount. E.g. "$3,400.00". If it's a filing with no payment (refund expected or $0 owed), write "Filing only". If unknown, write "?". **Deadline**: Format as "MMM DD, YYYY". If already past, add ⚠ before the date. If unknown, write "—". **Status**: - ✅ Filed & Paid - 🟢 Filed (refund pending) - 🔴 Overdue - 🟡 Due soon (within 14 days) - ⚪ Upcoming - 📋 Action required - ❓ Unknown Determine status automatically. If confirmation of filing + payment → Filed & Paid. If refund mentioned → Filed (refund pending). If deadline is past → Overdue. If deadline is within 14 days → Due soon. **Alerts**: Short, specific, plain-English flags. One per line. Examples: - ⚠ Penalty: 5% of unpaid tax per month if late - 📋 Documents needed: W-2, 1099-B - 🔁 Quarterly: next payment due Jun 15 - 💸 Refund expected: ~$1,200 - 📎 PDF notice attached - ❗ Extension filed — extended deadline Oct 15 - 🏛 State + Federal both due same day Leave blank if no alerts apply. ## RULES - No preamble, no explanation, no JSON. - If multiple tax items found in one email (e.g. federal + state, or Q1 + Q2 estimates), render each as a separate row + separate detail card. - Never invent data. If a value is missing, use "—" in the table and omit the field in the detail card. - Dates use the email's received date as "today" for all relative calculations. - Due soon threshold is 14 days (not 7) — tax deadlines require more lead time. ``` # Terms of Use Source: https://echo-docs.beau.to/terms-of-use **Beaux, Inc.** | Effective: February 7, 2026 | Last Updated: March 3, 2026 These Terms of Use ("Terms") govern your use of the Echo Chrome Extension ("Extension"), operated by Beaux, Inc. ("Echo," "we," "us," or "our"). By installing the Extension and connecting your Gmail account, you agree to these Terms in full. *** ## 1. Eligibility You may use the Extension only if you are at least 13 years of age (or 16 where required by applicable law), have the legal capacity to enter into a binding agreement, and are not prohibited from using the Service under applicable law. By connecting your Gmail account, you represent that you have the right to grant Echo access to that inbox and that doing so does not violate any agreement with Google or any third party. *** ## 2. What the Extension Does The Extension replaces your Chrome new tab page with a live inbox dashboard. It connects to your Gmail via Google's OAuth 2.0 API (read-only), processes emails using AI (Anthropic's Claude API), and extracts structured datapoints — dates, amounts, names, statuses — displayed in real time. **Echo cannot send, delete, or modify your emails at any time.** The Extension communicates exclusively with Echo's own servers. It does not track your browsing activity, inject scripts into other websites, or interact with any page outside of Echo. *** ## 3. AI Accuracy Disclaimer Echo uses large language models to extract information from your emails. **We do not guarantee the accuracy, completeness, or timeliness of any extracted datapoints.** AI models can make errors, miss information, or misinterpret context. You are solely responsible for independently verifying any information extracted by Echo before relying on it for business, financial, legal, or any other decisions. Echo is a productivity tool, not a system of record. *** ## 4. Account & Subscription ### 4.1 Account Registration You must create an Echo account to use the Extension. You agree to provide accurate information, keep your credentials confidential, and notify us at [i@beau.to](mailto:i@beau.to) if you suspect unauthorized access. ### 4.2 Free Trial & Paid Plans New accounts receive a 7-day free trial. Continued access after the trial requires a paid subscription (\$39/month), billed automatically via Stripe unless cancelled. ### 4.3 30-Day Money-Back Guarantee If you are not satisfied for any reason, you may request a full refund within 30 days of your first paid charge by contacting [i@beau.to](mailto:i@beau.to). This applies once per customer and does not apply to renewals. ### 4.4 Cancellation You may cancel at any time from account Settings. Cancellation takes effect at the end of the current billing period. Suspended or expired accounts and all associated data are permanently deleted after 30 days. *** ## 5. Acceptable Use You may use the Extension solely for your own personal or internal business use to process email inboxes you own or have explicit authorization to access. You agree not to: * **Resell or redistribute** access to the Extension or Service without our prior written consent * **Process unauthorized inboxes** — connect Gmail accounts you do not own or are not explicitly authorized to access * **Use extracted data for spam or scraping** — including building contact lists or harvesting information at scale * **Circumvent security measures** — attempt to bypass rate limits, access controls, or any security features * **Reverse engineer** proprietary components of the Extension or Service * **Use the Extension for any unlawful purpose** Violations may result in immediate account termination without refund. *** ## 6. Your Data & Ownership You retain full ownership of your emails and all datapoints extracted from them. Echo does not claim ownership over your email content or derived data. You grant Echo a limited, non-exclusive, revocable license to access and process your email data solely to provide the Service. *** ## 7. Chrome Permissions The Extension requests only the permissions necessary to operate: | Permission | Purpose | | ----------------------- | ------------------------------------------- | | Gmail OAuth (read-only) | Access your inbox to extract datapoints | | Chrome Storage | Cache dashboard data locally on your device | | New Tab Override | Display the Echo dashboard on every new tab | No other Chrome data — bookmarks, browsing history, or other extensions — is accessed. *** ## 8. Privacy Your use of the Extension is subject to our [Privacy Policy](https://echo.beaux.inc/privacy), incorporated into these Terms by reference. By using the Extension, you agree to the collection and use of your data as described therein. *** ## 9. Third-Party Services The Extension integrates with Google (Gmail API), Anthropic (AI processing), and Stripe (payments). Your use of those services is subject to their own terms. Echo is not responsible for the availability or practices of any third-party service. Revoking Echo's Gmail access via [Google Account Settings](https://myaccount.google.com/permissions) immediately stops all email processing. It does not automatically delete your Echo account or extracted datapoints. *** ## 10. Disclaimers THE EXTENSION IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND. TO THE FULLEST EXTENT PERMITTED BY LAW, ECHO DISCLAIMS ALL WARRANTIES, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY OF EXTRACTED DATA, AND UNINTERRUPTED OR ERROR-FREE OPERATION. *** ## 11. Limitation of Liability TO THE FULLEST EXTENT PERMITTED BY LAW, ECHO'S TOTAL LIABILITY FOR ANY CLAIMS ARISING FROM YOUR USE OF THE EXTENSION SHALL NOT EXCEED THE TOTAL AMOUNT YOU PAID TO ECHO IN THE 12 MONTHS PRECEDING THE CLAIM. ECHO SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES. *** ## 12. Termination You may uninstall the Extension and delete your account at any time from Settings. Echo may suspend or terminate your access if you violate these Terms, engage in fraudulent activity, or if required by law. Upon termination, your right to use the Extension ceases immediately. *** ## 13. Dispute Resolution Before initiating any formal proceeding, contact [i@beau.to](mailto:i@beau.to) and allow 30 days for informal resolution. Unresolved disputes shall be settled by binding arbitration under AAA Commercial Arbitration Rules, conducted in English. You waive any right to participate in class action proceedings. Either party may seek injunctive relief in court to prevent irreparable harm. *** ## 14. Governing Law These Terms are governed by the laws of the State of Delaware. Any court proceedings not subject to arbitration shall be brought exclusively in Delaware courts. *** ## 15. Changes to These Terms We may update these Terms from time to time. Material changes will be communicated by email at least 30 days before taking effect. Continued use of the Extension after changes take effect constitutes acceptance. *** ## 16. Contact Us **Email:** [i@beau.to](mailto:i@beau.to) **Address:** Beaux, Inc., 2261 Market Street #4410, San Francisco, CA 94114 **Response time:** We aim to respond within 5 business days *** *Version 1.0 | Last reviewed: March 3, 2026* # Tiers Source: https://echo-docs.beau.to/tiers ## Default plan — \$39/month By default, your Echo dashboard shows data extracted from emails received in the **last 24 hours**. Echo processes all incoming emails in real time, but only surfaces datapoints from the past day. This works well for most users — invoices, flights, and offers that matter are usually recent. ## Extended history If you need a longer window, you can expand your dashboard to show data from: * Last 3 days * Last 7 days * Last 2 weeks * Last month Pricing depends on your inbox volume and is handled individually. To get set up, email the Echo team at [i@beau.to](mailto:i@beau.to). > Echo processes all your incoming emails regardless of plan. The history window only affects what's visible on your dashboard — no data is lost. # Troubleshooting Source: https://echo-docs.beau.to/troubleshooting ## Data isn't appearing on my dashboard First, check the last sync timestamp at the bottom of your dashboard. If it updated recently, Echo is working — the email may simply not have matched any of your active Rules. A few things to check: * **Wait a few minutes.** There's a short delay between an email arriving and datapoints appearing on your dashboard. This is normal. * **Trigger a manual sync.** Click the refresh button (↻) in the top right of your dashboard to force an immediate sync. * **Check your history window.** By default, Echo only shows data from the last 24 hours. If the email is older, it won't appear unless you're on an extended history plan. * **Check your datapoint limit.** If you've hit your 1,000 datapoint limit for the month, Echo stops processing new emails. You can check your usage in account Settings. ## Echo is missing data from emails Echo extracts what's in the email body and any attached PDFs — but AI isn't perfect and can miss things, especially if the email is poorly formatted or the data is buried in an image or scanned PDF. To improve extraction: * **Refine your Rule.** Be more explicit about what you want extracted. Instead of "find payment info", try "extract the invoice number, total amount, and due date." * **Check if the data is in an image.** Echo can't read images or scanned PDFs — only text it can read directly. * **Add examples to your Rule.** Describe what the email typically looks like and what a good output looks like. ## Some emails are matched but others aren't Your Rule prompt is what decides whether an email is relevant. If Echo is inconsistently picking up emails of the same type, the prompt may be too narrow. Try making your Rule more general — describe the broader category of emails you want to catch, not just one specific format. ## The dashboard isn't updating * **Trigger a manual sync** by clicking the refresh button (↻). * **Check your Gmail connection** in Settings. If Echo lost access to your inbox, you'll need to reconnect your Gmail account. * **Check if you've hit your datapoint limit** for the month — Echo stops processing new emails once the limit is reached. ## I reconnected Gmail but data is gone Disconnecting and reconnecting Gmail does not restore previously extracted datapoints. If you cancelled your subscription or revoked Gmail access, all datapoints are permanently deleted. Echo will start fresh from the moment you reconnect. ## Still having issues? Email us at [i@beau.to](mailto:i@beau.to) and include: * A description of the issue * The Rule you're using * An example of an email Echo missed (subject line and sender is enough) We aim to respond within 3 business days. # Getting Started Source: https://echo-docs.beau.to/welcome ## Step 1: Connect Your Gmail Echo needs read-only access to your inbox to analyze emails and extract data. **How to connect:** 1. Login with your gmail account here: [https://echo.beau.to](https://echo.beau.to) 2. Provide access in Settings > **Note:** Echo only reads your emails. It never sends or deletes anything. *** ## Step 2: Create Your First Rule A **Rule** tells Echo what to look for in your emails. ### Option A: Use a Template Pick from ready-made templates from our \[template library], examples: * **Invoices** — Track unpaid bills, amounts, due dates * **Subscriptions** — Monitor renewals, pricing changes, cancellations * **Discounts & Offers** — Collect promo codes and expiring deals * **Travel Plans** — Extract flight times, hotel bookings, confirmations ### Option B: Create a Custom Rule Write your own rule in plain English: **Example:** ```markdown expandable theme={null} You are an invoice dashboard renderer. You receive pre-extracted schema.org JSON from an email and your job is to produce a clean, human-readable invoice table with alert flags. ## INPUT Schema.org JSON array extracted from an email. ## STEP 1 — DETERMINE IF INVOICE-RELATED This email is invoice-related if it contains ANY of: - A payment request with an amount - Invoice / bill / receipt / statement - "Amount due", "balance due", "total due", "please pay" - Invoice number tied to a payment - Payment confirmation or receipt - Overdue notice, reminder, late fee warning - Subscription renewal charge ## IF INVOICE-RELATED: STEP 2 — RENDER THE TABLE If invoice-related, output a table with these columns: | Vendor | Invoice # | Amount | Due Date | Status | Alerts | |--------|-----------|--------|----------|--------|--------| Rules per column: **Vendor**: Company or person name. If unknown, use sender email domain (e.g. "acme.com") **Invoice #**: Invoice / order / bill number. If none found, write "—" **Amount**: Format as currency symbol + amount. E.g. "$1,200.00". If multiple line items, show total. If unknown, write "?" **Due Date**: Format as "MMM DD, YYYY". If already past, add ⚠ before the date. If unknown, write "—" **Status**: - ✅ Paid - 🔴 Overdue - 🟡 Due soon (within 7 days) - ⚪ Unpaid - ❓ Unknown Determine status automatically from available data. If payment confirmation is present → Paid. If due date is in the past → Overdue. If due date is within 7 days → Due soon. **Alerts**: Short, specific, plain-English flags. One per line. Examples: - ⚠ Late fee: 2%/month after Apr 18 - 🔁 Recurring: charges monthly on the 1st - 📎 PDF attached - 💳 Auto-charge: card ending 4242 - ❗ No due date found Leave blank if no alerts apply. Omit any field that is not present in the source data. Do not invent values. If a field is inferred (not explicitly stated), add "(inferred)" after the value. ## RULES - No preamble, no explanation, no JSON. - If multiple invoices are found in one email (e.g. forwarded thread), render each as a separate row. - Never invent data. If a value is missing, use "—" in the table and omit the field in the detail card. - Dates use the email's received date as "today" for all relative calculations. ``` Echo will scan your inbox and build the stream based on your description. *** ## Step 3: View Your Dashboard Your dashboard updates automatically as new emails arrive. **What you'll see:** * Time filters (24h / 3 days / week / month) * Extracted data points organized by rule * "Jump to Gmail" links to see the original email * Last sync timestamp **Example dashboard sections:** * Open Questions → lease renewal due Aug 31, penalty notice for invoice #2024-0415 * Discounts & Offers → Adobe early bird pricing expires soon, Slack promo code XMAS26 *** *** # FAQ **Q: How long does the sync take?** A: Depends on your inbox size and emails volume. Usually up to 5 minutes. **Q: Can I delete a rule?** A: Yes. Deleting a rule removes it from your dashboard but doesn't touch your emails. **Q: What if Echo misses something?** A: You can refine your rule description or add filters. **Q: Is my data safe?** A: Echo uses read-only access. Your emails stay in Gmail. We don't store email content, only process data points via large language models by Anthropic and OpenAI. *** **We're applying for Google verification now. Once approved, the warning will disappear.** # Need Help? Contact us via [i@beau.to](mailto:i@beau.to) Welcome to Echo. Your inbox just got smarter. # Why Echo Source: https://echo-docs.beau.to/why-echo Your inbox is full of information that matters: invoices to pay, flights to catch, deadlines to hit, subscriptions renewing, deals expiring. But finding it means opening emails, scanning threads, and trying to remember what was where. Echo fixes that. Connect your Gmail once, set up a few Rules, and everything important shows up automatically on your dashboard — every time you open a new tab. Echo is a product by [Beau](https://beau.to), a Y Combinator-backed company. ## The problem with email Email wasn't designed to be a database. But that's what it's become. Your invoice history, travel plans, contract deadlines, and renewal notices all live there — buried in threads, mixed in with newsletters and notifications. Most people deal with this by keeping tabs open, flagging emails, or just trying to remember. It works until it doesn't. ## What Echo does differently Traditional email filters move emails around. Echo reads them and extracts what matters — amounts, dates, statuses, codes — and turns them into a live dashboard you actually look at. | Traditional filters | Echo | | ------------------------------------ | ---------------------------------- | | Move emails to folders | Extract data from emails | | You still have to open them | Data surfaces automatically | | Static rules based on sender/subject | AI understands context and meaning | | You manage the system | The system manages itself | ## Who uses Echo **Founders and freelancers** use Echo to stay on top of invoices, renewals, and client deadlines without maintaining spreadsheets or checking their inbox constantly. **Managers and operators** use Echo to monitor contracts, vendor payments, and time-sensitive notices across a busy inbox. **Anyone with an overwhelming inbox** uses Echo because it turns email from something you manage into something that works for you. ## Why it's always in front of you Echo lives in your new tab page. Not an app you have to remember to open, not a weekly digest you skim and forget. Every time you open a new tab — which is dozens of times a day — your most important data is already there. The best tool is the one you actually see. # Writing Rules Source: https://echo-docs.beau.to/writing-rules A Rule is a plain-English prompt that tells Echo what to look for in your emails. The better your prompt, the more accurate and useful your dashboard will be. ## Start with a template If you're new to Rules, the easiest way to get started is with one of Echo's built-in templates — Invoices, Flights, Taxes, Offers. They're ready to use out of the box and cover the most common use cases. For anything more specific, you can write your own Rule from scratch or modify a template to fit your needs. ## How to write a good Rule **Be specific about what you want extracted.** Vague prompts produce vague results. Tell Echo exactly what data to pull out. | Instead of... | Try... | | -------------------- | -------------------------------------------------------------------------------- | | "Find payment info" | "Extract the vendor name, invoice number, total amount, and due date" | | "Get flight details" | "Extract the flight number, departure time, arrival time, and booking reference" | | "Find discounts" | "Extract the promo code, discount value, and expiry date" | **Describe what to do when data is missing.** Emails aren't always complete. Tell Echo what to show when a field isn't found. ```text theme={null} If no due date is found, write "—". If the amount is unclear, write "?". ``` **Tell Echo what the email looks like.** The more context you give, the better Echo can identify relevant emails and ignore the rest. ```text theme={null} This email is invoice-related if it contains a payment request, an invoice number, or phrases like "amount due" or "please pay". ``` **Define the output format.** If you want data displayed in a specific way, say so explicitly. ```text theme={null} Format amounts as: $1,200.00 Format dates as: MMM DD, YYYY ``` ## What to avoid * **Too broad.** A Rule that matches everything will consume datapoints fast and produce noisy results. * **Too narrow.** A Rule written for one specific email format may miss variations from the same sender. * **Assuming Echo knows context.** Echo reads each email independently — it has no memory of previous emails or your past dashboard data. ## Improving a Rule that isn't working Since you can't test a Rule on a specific email before activating it, the best approach is to iterate: 1. Activate the Rule and wait for new matching emails to arrive 2. If Echo misses data or extracts the wrong things, go back and refine the prompt 3. Be more explicit about what you want — add examples, clarify edge cases ## Example: a custom Rule Here's a simple Rule for extracting subscription renewal notices: ```text theme={null} Extract subscription renewal notices. This data is relevant if it mentions a renewal, a recurring charge, or a subscription expiring soon. Extract: - Service name - Renewal amount - Renewal date - Plan type (monthly or annual) If any field is missing, write "—". Format amounts as: $0.00 Format dates as: MMM DD, YYYY ``` The clearer and more structured your prompt, the more consistent Echo's output will be.