Privacy policy

Website visitors

When you read this site we receive the technical data any web server receives: your IP address, browser type, the page you asked for and the time. Cloudflare, which hosts the site, keeps this in short lived security logs. We do not build profiles from it and we keep no request logs of our own.

We measure traffic with Plausible, a privacy focused analytics service that uses no cookies and stores no personal data. It counts page views and the country a visit came from, nothing that identifies you.

Our forms are protected by Cloudflare Turnstile, which checks that a submission comes from a person without a puzzle and without tracking you across sites. If you write to us through the contact form we keep your message for 90 days so we can reply and follow up, then it expires.

This site sets no advertising or tracking cookies, which is why you did not see a cookie banner. If that ever changes we will update this page and ask first.

Businesses that sign up

To open a Usher Up account we ask for your business name, website, the services you offer with typical prices, your hours, a contact name and email, and where you want handoffs delivered (an email address, a webhook address, or a connection to your CRM). We use this to run the service, to generate the discovery snippet you place on your website, to send you handoffs, and to contact you about your account.

If you move to a paid plan, Stripe takes your payment. Your card number goes to Stripe and never to us; we keep only Stripe's identifiers for your customer record and subscription, the plan you chose and the date it is paid through. Stripe's own privacy policy covers what it holds.

Under the GDPR our legal basis is performance of our contract with you. For the occasional product update email our basis is our legitimate interest in keeping customers informed, and every such email has an unsubscribe link. We never sell this information.

We keep account data while your account is open and for 30 days after it closes, then delete it, except for records we must keep for tax or legal reasons, such as invoices.

Handoff data

This is the core of the service and the part that deserves the most care. A handoff is not ordinary website data: it is a piece of a private conversation you had with an AI assistant, passed to a business you chose. When that happens, the assistant (or you, on a business's hosted contact page) sends us:

• your name and an email address or phone number,
• the message you want to pass on,
• a short summary of your conversation with the assistant,
• the products or services you discussed, the kind of request (a quote, a callback, or a support question) and how urgent it is,
• a record that you agreed to share this with that business, with the time, and
• the name of the assistant that sent it.

We process this only to check it, package it, deliver it to the business you chose, and let that business look it up later. We do not use handoff data for anything else: no analytics on its content, no training of any model, no marketing.

Before a handoff is sent

On a business's hosted contact page you type the message yourself, see every field that will be sent, and tick a box agreeing that your name, contact details and message go to that business. Nothing is sent until you do.

When an AI assistant sends the handoff, we cannot see your conversation and cannot watch what the assistant showed you. So we set rules for assistants instead, published in our assistant policy: before calling us, the assistant must tell you exactly what will be shared (your name, contact details and a summary of the conversation), name the business that will receive it, and get a clear yes from you. It may include health, legal or financial details only when they matter to your request, and must tell you it is doing so. Every request has to carry that confirmation; we reject any request without it and store nothing from it. An assistant that fabricates consent or sends what it was not asked to send loses access.

What we record for every handoff: the fact that you agreed, the moment we received it, the business it went to, and the exact content that was sent. The business sees the same record, so there is no version of your request that you did not agree to.

Two things you should know. First, we can only act on what the assistant tells us; if an assistant gets this wrong, tell us and we will delete our copy and raise it with the assistant's maker. Second, once a handoff is delivered, the business has its own copy. We can delete ours at any time; we cannot reach into theirs. Send only what the business needs to help you.

Who is responsible for your handoff

The business you contacted decides why it needs your information and how it uses it: it is the controller. We process the handoff on its documented instructions, under our data processing agreement: we are its processor, and under California law its service provider. The business is responsible for the privacy notice that covers its own use of your request and for requests about copies it holds. We are responsible for what we do with it: checking, delivery, storage for the period below, and deletion.

For questions about a request already delivered to a business, the business is the fastest route. You can also ask us; we will tell you which business holds it, delete our copy, and pass your request on.

How long we keep handoffs, and what deletion covers

We keep each handoff for 90 days from the moment we receive it, whether it was delivered at once or held for a business on the free plan. At 90 days the record expires from our store automatically; there is no manual step to forget. We make no backup copies of handoffs, so the expiry is the end of our copy.

Deletion from Usher Up covers what we control: the stored handoff, its index entry and its hold record. It does not reach copies that already left us:

• the email we delivered to the business sits in the business's mailbox, under the business's own retention;
• a copy sent to a business's webhook or CRM, such as HubSpot, is held by that system under the business's instructions;
• our email provider, Resend, keeps delivery logs and message content under its own retention policy, typically 12 months (see our sub-processors page).

You can ask us to delete a handoff before the 90 days are up. Use the contact form with the reference number from the business's reply if you have it, or the name and contact details you gave. We confirm the request matches those details, delete our copy within 30 days (usually the same week), forward your request to the business, and tell you when it is done. If delivery to a business failed, the record is still kept for the same 90 days so the business can retrieve it, and the same deletion route applies.

Sensitive details in a conversation

A conversation summary can contain whatever you chose to discuss, which for some businesses means health, legal or financial matters. We treat this in four ways.

• Less goes in. Assistants must send only what the business needs to respond, and must tell you when a sensitive detail is included. On the hosted contact page you write the message yourself.
• We do not read it. We do not scan, filter or classify the content of handoffs. That means we also cannot promise to catch something that should not have been sent; if you notice it, tell us and we delete it.
• Few can see it. Stored handoffs can be read only with an administrative token held by the people who run Usher Up, and by the business it was sent to through its own account page.
• Encrypted and short lived. In transit and at rest, and gone after 90 days.

Businesses such as lawyers, clinics or advisers may have confidentiality duties of their own that apply the moment they receive your request. Those duties are theirs and are not changed by the handoff passing through us.

Who we share data with

There are two kinds of recipients, and the difference matters.

Our providers help us run the service and act on our instructions. The current list, what each does and where it is located is on our sub-processors page. In short: Cloudflare hosts the service and stores handoffs, Resend delivers email, Stripe handles payments, Migadu hosts our own mailbox, and Plausible counts visits.

Destinations a business chooses receive handoffs on that business's instruction: its mailbox, a webhook on its own systems, or its CRM such as HubSpot. Those are the business's providers, not ours. Once a handoff reaches them it is outside our control and covered by the business's own policies.

We will disclose data if the law requires it, for example a valid court order, and we will tell the affected business unless we are legally barred from doing so. If Aliso LLC is ever sold or merged, data may transfer to the new owner under this same policy.

Where data is stored

Aliso LLC is in the United States. Personal data is processed in the United States and in the other jurisdictions where our providers operate: Migadu is in Switzerland and Plausible in the European Union; the rest are in the United States. Where a business customer needs a transfer mechanism for data from the European Economic Area, the United Kingdom or Switzerland, such as the EU standard contractual clauses or the UK international data transfer addendum, it is addressed through an executed data processing agreement.

Security

All traffic uses HTTPS. Stored data is encrypted at rest by Cloudflare. Reading a stored handoff requires an administrative token held only by the people who run Usher Up, and the Cloudflare account that hosts the service is protected by two factor authentication. Webhook deliveries are signed so the receiver can verify they came from us. We keep no request logs of our own beyond Cloudflare's short lived security logs. Our security page has more detail.

No system is perfect. If we learn of a breach that affects you we will tell you without undue delay, and we will tell affected business customers within 72 hours as our data processing agreement requires, so they can tell the people whose requests they hold.

Your rights

Wherever you live you can ask us what we hold about you, ask us to correct it, ask us to delete it, or object to how we use it. Use our contact form. We respond within 30 days; if a request needs more time we tell you why and when.

How we check it is you. For a handoff, we match the reference number or the name and contact details on the record with what you tell us. For a business account, we reply to the account's contact email. We never ask for more than we need to make that match, and an agent acting for you can use the same route with your written permission.

If you were handed off to a business: the business is the controller of your handoff, so asking it directly is fastest. If you ask us instead, we delete our copy, forward your request to the business within five business days, and tell you which business it was so you can follow up.

California residents. Aliso LLC is the business responsible for the personal information described in this policy, and our processing is scoped to applicable U.S. state privacy laws, including the California Consumer Privacy Act and the California Privacy Rights Act. The categories of personal information we collect are identifiers (name, email, phone, IP address), commercial information (the services you asked a business about, your plan and payment status), and the content of your message and conversation summary, which may include sensitive personal information you chose to share. We collect it from you, from the AI assistant acting for you, and from the business that signs up. We use it for the purposes in this policy and no others, and we keep it for the periods in this policy. We do not sell personal information, we do not share it for cross context behavioural advertising, and we do not use sensitive personal information to infer anything about you, so there is nothing to opt out of or limit. You have the right to know, delete and correct, and the right not to be treated differently for exercising those rights. For handoffs we act as a service provider to the business you contacted.

Residents of the EEA, UK and Switzerland. Usher Up does not intentionally target individuals in the European Union or the United Kingdom. If you are there and use the service anyway, Aliso LLC is the controller of the information described in this policy unless an executed data processing agreement provides otherwise, and you also have the right to data portability, to withdraw consent where we rely on it, and to complain to your data protection authority. We would appreciate the chance to resolve a concern first.

Children

Usher Up is for businesses and for adults contacting them. We do not knowingly collect information from anyone under 16. If you believe a child's information reached us, tell us through the contact form: we delete our copy and tell the business that received it so it can delete its own.

Changes to this policy

When we change this policy we update the date at the top. For changes that matter we email business customers at least 14 days before they take effect, and we keep earlier versions, available on request. If you reached us through an AI assistant you have no account with us, so the date at the top is your signal: the version in force when we received your handoff is the one that governs it, and a later version never widens what we may do with a handoff we already hold.

Aliso LLC
Sacramento, California, United States
Contact form