Two addresses, and what to put in them
Two addresses. support@cuvy.io for anything to do with a run, an address, an invoice or an account. sales@cuvy.io for volume, seats, procurement and security review. There is no contact form, because the site is static and a form that posts nowhere helps nobody. Both are read on working days from Toronto; no plan buys a response time.
- Support
- support@cuvy.io
- Sales and procurement
- sales@cuvy.io
- Contact form
- None — the site is static
- Read on
- Working days
50 addresses free every month · no card
One inbox for the product, one for the paperwork
Both are read by people who can look at the thing you are asking about. Sending to the wrong one costs a forward, not a day.
support@cuvy.io
Something did not work, an address looks wrong, a run stopped, a charge needs explaining, or you want your details out of the corpus. Also the address for anything with a legal or privacy heading on it.
sales@cuvy.io
Volume above the published plans, extra seats, purchase orders and invoicing, security questionnaires, a DPA to sign, and anything your procurement process needs in writing before a card can be used.
What can be put in writing, and what cannot
Security questionnaires are answered. So are vendor risk forms, and the data-protection sections that ask what is held, where it goes and how long it stays. A data processing agreement is available to sign, and the privacy policy and the trust centre already contain most of what a questionnaire asks for, in the same words we would use in the reply.
What cannot be produced is a certificate. Cuvy has completed no third-party security audit and holds no certificate against an information-security standard, and no audit is being represented as under way. If your process has a hard gate on either, that is a genuine no rather than something to be negotiated later, and it is better read on this page than discovered halfway through an evaluation.
The other thing worth saying early: pricing is monthly and published. There is no annual prepayment, so a discount for committing to a year is not a thing that can be offered, and anyone in procurement expecting one should know that before the second call.
Four lines that turn a sales email into an answer
Each one removes a round trip. A first message containing all four usually gets a decision rather than a questionnaire back.
- How many people a month, roughly
- Not seats and not searches — people you expect to have an address handed over for, since that is the only thing that consumes credits. A range is fine. It is the number that decides whether a published plan already covers you.
- How many people need to log in
- Seats and credits are separate: a seat that looks nobody up costs nothing extra, and everybody draws from one balance. Say how many logins you need and whether some of them should be prevented from spending.
- What your buying process needs that a card cannot do
- Purchase order numbers, a signed order form, a specific invoice format, tax details, a supplier onboarding portal. List them. Some are straightforward and some are not, and it is quicker to find out which is which in the first reply.
- The date you actually need an answer by
- If a security review has a deadline, say what it is. Where the honest answer is that we cannot meet it, you will be told that rather than kept warm through it.
How long a reply takes, without a promise attached
Both inboxes are worked through during Toronto business hours, Monday to Friday. Most messages get an answer the same day or the next one. That is a description of what usually happens and not a commitment: no plan on the pricing page includes a response-time guarantee, and nothing here should be read into a contract as one.
Scale lists priority support among its features. What that means precisely is position in the queue — a Scale message is picked up before others waiting — and it does not convert into a number of hours. Where somebody needs a contractual response time, say so in the first email and you will get a straight answer about whether it is possible.
Questionnaires and legal review take longer than product questions, usually several working days, because they are answered carefully rather than by pattern-matching to the last one. If yours has a deadline, put the date in the first line.
What people ask before writing in
Why is there no contact form?
Because this site is static files with no server behind them, and a form that posts nowhere is worse than no form at all. Wiring one to a third-party endpoint would add a script and another company handling your details to every page on the site, in exchange for a text box that writes an email you can write yourself.
Can we pay by invoice or bank transfer instead of a card?
Checkout, receipts and cancellations run through Stripe, and every plan is billed monthly — there is no annual price to prepay. If your finance process cannot use a card, write to sales@cuvy.io describing what it does need and you will get a yes or a no, not a maybe.
Will you complete our security questionnaire?
Yes, and it will be answered accurately, including the lines where the answer is unfavourable. Cuvy has no completed third-party audit report and no certificate against an information-security standard, so a questionnaire treating one of those as mandatory will fail at that question. Better to discover it in week one than in week six; the posture behind every other answer is set out on the trust centre.
Can I book a demo call?
There is no booking link on this site yet. Write to sales@cuvy.io with two or three times that suit you and what you want to see, and it will be arranged by email. Most questions that a demo would answer are answered faster by running the free plan on one of your own searches.
Who do I write to about volume above the published plans?
sales@cuvy.io. Scale at $99 a month is the largest plan on the pricing page, at 15,000 addresses and 5 seats. Above that there is no secret tier waiting — there is a conversation about what the number would have to be, and it starts with your monthly volume.
Where do I send a legal notice or a data request?
support@cuvy.io, with the subject line saying which it is. Requests to have contact details removed are handled within 30 days whether or not the person asking is a customer, and the route is described in full on the trust centre.
50 addresses free every month · no card