Terms

Getting an account

There is no sign-up form. Whoever runs this installation sets the addresses and domains allowed in, and an address outside that list is turned away at sign-in. One thing gets past it.

That thing is an invitation. An owner or an admin names your address, and signing in with Google at that address is what accepts it, so there is no link to click and no token to keep. Nothing is emailed either, so whoever invited you has to point you at the sign-in page themselves. An invitation expires if it goes unused.

Your workspace, and who can change it

Everything you add belongs to one workspace and stays inside it. There is no shared pool across workspaces, and nothing in the product moves a record from one to another.

Inside a workspace, five things are an owner's or an admin's: renaming it, inviting somebody, changing a colleague's role, setting up single sign-on, and turning on website tracking. Everyone else does the work and not those. The last owner cannot be demoted, so a workspace can't be left with nobody who can run it.

Connecting a mailbox

Connecting Gmail or Outlook gives Conversaya the permissions Google or Microsoft names on the consent screen, and none beyond them. The privacy policy lists each one with what it is for.

Two things belong here rather than there. Reading is all the app asks for at sign-in, so until somebody turns sending on it cannot send anything at all. And the permission is yours to withdraw from Settings whenever you like, without asking us first.

Sending from your address

Sending is a second decision, made in Settings, and Google asks you again before it takes effect. We show you the exact mailbox that will be able to send before you grant it. After that a message leaves from your own address, written by somebody on your team or approved by them under the policy that workspace set for the campaign.

A campaign message with no unsubscribe link in it is refused, when it is planned and again on the way out. A message a rep writes by hand passes, because a single letter is not a list.

Six things stop future email to somebody, and none of them needs us:

• Somebody clicks the unsubscribe link in a message.
• They reply instead, which ends the sequence they were in.
• The mail server bounces the address hard.
• A rep suppresses or deletes the contact.
• The campaign is paused or stopped.
• The mailbox is disconnected, which pauses every campaign pinned to it.

Each one writes a state rather than counting, so saying stop twice lands the same as saying it once. A suppressed address stays that way until somebody in the workspace lifts it by hand.

What the assistant may do

The assistant reads the messages filed against a contact and drafts from them. Whether a draft goes out on its own or waits for a person is the approval policy the workspace sets for that campaign, and it's the same policy for every message in it.

A model can be wrong about a person, which is why the approval step is the point rather than a formality. Nothing in the product fills an empty field with a plausible guess, and a value somebody typed is never overwritten by one the assistant found.

Reading a message means its text goes to a language model. The privacy policy names which model and how it gets there.

Money

Nothing here charges anybody. There is no plan to pick, no price and no payment code in the product, so these terms say nothing about fees, refunds or renewal. A page that set out billing rules for a thing that cannot bill you would be describing software we haven't written.

Ending it

The way out is two controls in Settings: disconnecting the mailbox, and deleting what we synced from it. The privacy policy is exact about what each one removes and what it leaves behind.

A whole workspace is the one thing you can't remove yourself, and the policy says why. Write to privacy@conversaya.com from the address on the account and we'll do it.

Getting in touch

Anything on this page, or something it doesn't answer: privacy@conversaya.com.