Privacy

This Privacy Policy explains how Edison Technologies LLC (“Edison,” “we,” “us”) collects, uses, and shares information when you use tryedison.com, app.tryedison.com, and our voice receptionist (together, the “Service”).

Questions or requests: hello@tryedison.com.

Who this covers

Two groups of people show up in our systems:

• Shop users — owners and staff who create an Edison account, confirm a listing, connect a number, or sign in.
• Callers — people who phone a shop that uses Edison. They usually do not have an Edison account. The shop is collecting their information through our Service.

Information we collect

Account. Email address, name, and sign-in method. Google sign-in requests email and profile only — not calendar access. You can also sign in with a magic link we send to your email. We store a session so you stay signed in across tryedison.com and app.tryedison.com.

Shop listing. When you search for and confirm a business, we collect listing details such as name, address, phone, hours, website, category, rating, and public reviews. We use a coarse location from your connection only to bias search results nearby. We do not store that location as a profile.

Website enrichment. If the listing has a public website, we may fetch public pages such as home, about, services, and contact so the receptionist knows the shop’s services, area, hours, and FAQs. That runs in the background and does not block go-live.

Voice and calls. For inbound calls we process live audio through our AI model partners so the receptionist can talk. We store the caller’s number, name, callback number, service address, job details, urgency, preferred times, a full transcript, and an AI-written summary. If a call goes to overflow voicemail, we may store that recording. We may look up line type (mobile, landline, VoIP) to route the call. We also provision and store the Edison number you publish and how you forward to it.

Memory. We keep shop facts, per-caller notes keyed to the caller’s phone number (name, address, equipment, access notes), and operational outcomes so repeat callers do not start from zero. Memory providers process that text for us.

Billing. Stripe handles cards. We store Stripe customer and subscription IDs, plan, trial dates, and credit balance. We do not store full card numbers.

Calendar (optional). After you are live, you may connect Google Calendar or Microsoft Outlook. See Calendar below.

Alerts and product events. After a real call we may email the shop a summary (caller name, callback, address, job). We also log internal events in our own database — trial start, number claimed, go-live, and similar. We use Google Analytics 4, Google Ads (gtag), and the Meta Pixel on tryedison.com and app.tryedison.com to see how people find the site and move through signup and checkout. Those tags receive the page URL, referrer, device, and approximate location. The Meta Pixel also receives hashed shop-user contact details when Automatic Advanced Matching is on, and conversion events (Lead on signup, Purchase when a card starts the free trial). We do not send caller audio, transcripts, or job content to Analytics, Google Ads, or Meta.

Support chat. We use Intercom on tryedison.com and app.tryedison.com. Visitors send the page URL and the device details the messenger collects. Signed-in shop users also send their email, name, shop name, and plan so we know who is writing. Intercom does not receive call audio, transcripts, or job content.

How we use it

We use this information to:

• Answer the phone, take messages, and book or pass jobs to the shop
• Send owner alerts and in-app notifications
• Bill the shop, track credits, and prevent abuse
• Improve the receptionist for that shop
• Provide support and meet legal or security obligations
• Measure site traffic and the path from listing to checkout

We do not sell personal information. We do not sell call recordings or transcripts. We do not use caller or job data for advertising. Shop-user site activity may be used to measure and improve Edison ads.

AI and voice processing

Edison is an AI receptionist. Live call audio, transcripts, and summaries are sent to our AI model partners so the receptionist can listen, speak, and write the call brief. Those partners process the audio and text to provide that service. We do not use caller audio to train a public model of our own.

The voice partner is xAI’s paid API (Grok Voice 2.0 for the live call; grok-4.6 for the written summary). That is not consumer Grok.com. xAI’s API terms say they do not train on API inputs or outputs without explicit permission. Voice audio is processed in real time and is not used to train their models. We do not turn on consumer “improve the model” sharing.

Shop and caller notes may also go to Mem0 so repeat callers do not start from zero. Mem0 does not receive raw Google Calendar API payloads or OAuth tokens. We do not use Mem0 to train a public Edison model.

We do not run self-hosted or offline foundation models. See Limited Use for how this applies to Google Workspace data.

Edison does not play a “this call is recorded” line today. The shop is responsible for any notice or consent their state requires. See our Terms.

Who we share it with

We share information with vendors who process it for us — not as a sale:

• Stripe — payments and the billing portal
• Twilio — phone numbers and call transport
• Google — sign-in, business listing search, optional Calendar, and Analytics
• Microsoft — optional Outlook calendar
• Pipedream — Calendar OAuth token storage and refresh
• Hosting, database, and authentication providers
• Email delivery providers
• Intercom — support chat
• Website enrichment providers
• Memory and personalization providers
• AI model partners — live voice, transcripts, and summaries

We may also share information if the law requires it, to protect the Service or someone’s safety, or as part of a sale or reorganization of the company, with notice where we can give it.

The shop can see its own calls, transcripts, summaries, memories, and alerts in the dashboard. That is the point of the product.

Cookies

We use essential cookies to keep you signed in and to carry a listing from the marketing site into the app. In production those cookies are set on .tryedison.com so both hosts can use the same session. They are HTTP-only and SameSite=Lax. Google Analytics also sets first-party _ga cookies so we can tell a new visit from a return visit across tryedison.com and app.tryedison.com. We also set a first-party cookie that records whether someone arrived from an ad, search, a referral, or directly. We do not use third-party advertising cookies or Google ads personalization. Intercom sets its own cookies on tryedison.com and app.tryedison.com so a support conversation stays with that browser.

Calendar and Google Workspace

Calendar is optional and happens after you go live — not at sign-up. Google sign-in for the account is email and profile only. If you later connect Google Calendar, Pipedream’s Google Calendar app requests calendar.events, calendar.readonly, and calendar.settings.readonly. We use those to (1) see whether a proposed time is busy on the primary calendar, (2) create, update, or delete the booking event for that call, and (3) store the connected address in Settings. We do not request the full Calendar scope. We do not read unrelated events to train a model. We do not use that access for ads or resale.

The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements. The full statement is on our Limited Use page.

During a live call the voice model may receive derived tool results — open slot times and an event id — so it can offer a real time and confirm the book. It does not receive your full calendar, attendee lists, or refresh tokens. That transfer is only to provide the booking feature. It is not for training generalized models. Stripe, Twilio, and Firecrawl do not receive Calendar tokens. Pipedream does, only to store and refresh those tokens for booking.

Pipedream stores and refreshes Calendar OAuth tokens for the booking feature only. Pipedream does not use those tokens for AI, model training, or ads. We store a Pipedream account id, the provider, and the connected email on the shop. Tokens never go to the browser or to the voice model. You can disconnect Calendar in Settings. Email hello@tryedison.com to delete the account and the stored tokens.

How we protect sensitive data

We use TLS (HTTPS) in transit. Shop data and call records sit in Supabase Postgres, which encrypts data at rest. Calendar refresh and access tokens are stored and refreshed by Pipedream for booking only. We keep an account id on the shop row and send calendar requests through Pipedream, which attaches the access token. Tokens never go to the browser. Session cookies are HTTP-only and SameSite=Lax on .tryedison.com. Access to a shop’s data is limited to that shop’s owner and Edison staff doing support.

How long we keep it

We keep account, listing, call, and billing data while the shop is active and for a reasonable period after cancel so we can handle billing, disputes, and legal requests. If you delete a memory item in the product, we remove it from our systems and from our memory providers. If you ask us to delete an account, we delete or de-identify what we can after we finish any required retention.

Your rights

You can ask us to access, correct, or delete your information. There is not a self-serve delete-account button yet. Email hello@tryedison.com from the address on the account. We may need to verify it is you. Canceling billing in Stripe stops new charges. It does not by itself wipe call history.

You can delete individual memory items in the product. You can disconnect calendar access in Settings.

Caller rights

If you called a shop and want your name, number, address, transcript, or notes removed, email hello@tryedison.com with the number you called from and the shop you reached. We will work with that shop. We may not be able to delete information the shop is required to keep, or a record that a call happened.

US state privacy rights

If a US state privacy law applies to you, you may have rights to know, access, correct, or delete personal information, and to appeal a denial. We do not sell personal information and we do not share it for cross-context behavioral advertising. To exercise a right, email hello@tryedison.com. We will not discriminate against you for asking.

Children

Edison is for trade businesses, not for children. We do not knowingly collect personal information from anyone under 13. If you think we have, email us and we will delete it.

Changes

We may update this policy. The “Last updated” date at the top will change. For a material change we will post the new policy on this page. Keep using the Service after that date and you accept the updated policy.

Contact

Edison Technologies LLC
A Wyoming limited liability company
hello@tryedison.com