This page covers Kogsy's public site at kogsy.tech, the pilot request form, the interactive sample and sign-in to Kogsy's own tools. How to write to us is on the contact page.
You can write to us at hello@kogsy.tech, or use the contact page.
When you ask for a pilot we record what you type: your name, email address, business name and website, what kind of business it is, roughly how many enquiries you get and how they arrive, any times you suggest for a call, and anything you add in the message box. We also record the time zone your browser reports, so the times you suggest can be read correctly. If you followed a link to reach the site, we record with your request the campaign labels in that link, the name of the website that linked to us, and the first page you opened here. That is held in your browser until you send the form and is sent only with it; we do not record it for visitors who never ask for a pilot. A hidden field catches automated submissions and is not kept for anyone real. We keep a salted hash of the network address to limit repeat submissions. The address itself is not stored.
The times you suggest are a request. Nothing is booked until we confirm a time with you by email. The same request sent twice on one day is stored once.
We use this to reply to you about a pilot. If a pilot goes ahead, the business name and your name and address are carried into the set-up so you are not asked for them again. Nothing else.
The sample on the demo page runs in your browser. The businesses and customers in it are invented, and nothing you type into it is sent to us or stored.
We count how many times the sample is started and how many times it is finished. Each count is the name of the step and the time, with a salted hash of the network address kept only so that one address cannot inflate the numbers. It records nothing about you and nothing you typed.
Kogsy may write to a business it thinks the enquiry responder could help. Before doing so we note the business name, its website, the public page where it invites contact, and what we saw on its public pages. We use only a contact route the business itself publishes, and we do not guess addresses.
Reply to say you do not want to hear from us and we stop, and keep only the note that says not to contact you again.
Some businesses use an enquiry form that Kogsy set up for them. That form runs in the business's own accounts, not in Kogsy's: the business stores what you send and is responsible for it, and the form says so. Kogsy does not hold those enquiries. To see, correct or remove one, ask the business.
Kogsy's own demonstration of that software takes invented sample enquiries only. Its customer form is closed, so nothing a member of the public writes is stored there.
A version hosted by Kogsy is planned and is not open. Before it opens, this page will be changed to say what Kogsy would then hold and for whom.
This describes the software as it runs for a client business, so that the business and its customers can see what happens. The business is the one holding the data; its own privacy notice is the one that applies.
What is stored: the name, email address and message a customer types into the form. Before anything is stored, digit runs that pass the card-number check and a word following "password", "passcode" or "pin" are removed. Other sensitive details a customer chooses to write are stored as written, which is why the form asks people not to send them. When the form is shown inside a page on the business's website, the address of that website, as the customer's browser reports it, is stored with the enquiry.
Who can read it: people the business has given a sign-in. One business's sign-in cannot read another's enquiries. During set-up Kogsy works in the business's accounts as a collaborator, at the business's invitation, and is removed at handover.
The model: to draft a reply, the enquiry and the business's own profile are sent to a language model through the business's own account with the model provider. The software calls Anthropic's API. The model is given no tools: it cannot send a message, change a setting or read another enquiry. It reads each enquiry at the moment it drafts. This software does not use enquiries to train a model. What the provider keeps is governed by the business's account with that provider.
Approval: no reply is sent without a person at the business approving it. Code checks each draft, and the edited text again at approval, against the business's own rules. A reply containing a phrase the business has blocked cannot be approved. There is no setting that sends without approval.
Sending: an approved reply is sent once, through the business's own mail account, to the person who wrote in and nobody else. Sending is switched off until the business turns it on.
Deletion: an enquiry is deleted when it is older than the period the business sets, 365 days unless changed. A daily clean-up does this, and it also runs whenever the queue is opened. The business can delete any enquiry sooner. The record of steps taken (approved, sent, deleted) is kept and holds identifiers and outcomes, not what the customer wrote.
Embedding: when the form is placed inside a page on the business's site it is a frame. No script from this software runs on the business's page, and only websites the business has listed can show the form in a frame.
The business: the enquiries it receives, its own privacy notice, who has a sign-in, what its profile and rules say, whether sending is on, and how long enquiries are kept.
Kogsy: the software, setting it up with the business, and the support agreed in writing for the pilot. Kogsy does not decide what a reply says and does not send replies.
The providers the business chooses for hosting, the database, the model and mail each operate their own service under the business's account with them.
If you are given a sign-in on kogsy.tech, we hold your name, your email address and, if you set one, a password. The password is stored as a salted hash and cannot be read back. When you choose a password, the first five characters of a hash of it are sent to the Pwned Passwords service to check it against known breaches; the password itself never leaves our server.
A workspace on kogsy.tech is a rehearsal space. It holds the business profile you write and invented sample enquiries. It does not take enquiries from your customers.
A Kogsy deployment is built from four services. The database is Postgres, run by a managed database provider (Neon). The site runs on Vercel. Replies are drafted through the model provider's API (Anthropic). Email is sent through Resend. For a client business each of these is the business's own account. For Kogsy's own site they are Kogsy's accounts, and pilot requests are stored in its database.
The database region is chosen when a deployment is created. This page will name the region for Kogsy's own site once it is fixed. Each provider operates its service; beyond that, only Kogsy can read what you sent.
A pilot request is kept while the conversation it started is live. Ask us to remove it and we do. Otherwise we review what we hold twelve months after the last contact and remove what is no longer needed.
A copy of each pilot request is sent to Kogsy by email through Resend, with your address as the reply-to so that we can answer you directly. If you are given a sign-in for Kogsy's own tools, the sign-in link is sent the same way. We keep a record of whether each of our own messages was accepted by the mail provider. That record holds the outcome and the time, not the recipient or the text.
The public site sets no cookies, uses no analytics service, and loads nothing from a third party: its type is served from kogsy.tech. The only counting is the count of sample runs described above, kept on our own server. Signing in to Kogsy's tools sets one session cookie, which is what keeps you signed in and nothing more.
Ask us what we hold about you, ask us to correct it, or ask us to remove it, using the contact page. No automated decision is made about anyone from the pilot request form.
The date at the top of this page changes when the page does.