Email, and a person replies

Get in touch — it goes to one person

There is no ticket system, no chat widget and no support queue, because Tessira is made by a one-person studio. Email is the whole of it. Pick the address that fits, and expect a reply within a few days rather than a few minutes.

Three routes

Where to send what

They all reach the same person. Using the right one means it gets read with the right context, and privacy requests get logged properly.

General

Feedback, feature requests, a template you wish existed, partnership or press enquiries, or telling us something on this site is wrong.

hello@cubicpixel.co

Best for: ideas, opinions and anything that is not urgent.

Support

Something is broken, an email did not arrive, a PDF will not render, an AI check failed, or you are locked out of your account.

support@cubicpixel.co

Best for: anything the help centre did not already answer.

Privacy & data

A copy of your data, deleting your account, questions about the AI review, or exercising a data-protection right.

privacy@cubicpixel.co

Best for: anything covered by the privacy policy.

What Tessira will never ask you for. Nobody will ever ask for your password, a reset code, or your card details — there is no card, because there is nothing to pay for. If a message claiming to be from Tessira asks for any of those, it is not from Tessira. Forward it to support@cubicpixel.co and delete it.
Reporting a bug

Six lines that turn a report into a fix

Most bug reports arrive as “the PDF is broken”, which starts a three-message conversation before anything can be investigated. This is what makes it one message instead.

Please do not attach your CV unless asked. Almost every bug can be reproduced without it, and there is no reason for your personal details to sit in an inbox. If the problem genuinely depends on your content, you will be asked, and you can send a JSON export with the details edited out.
  • What you were doingThe exact steps — “opened the Experience section, changed the To date to Present, clicked Download PDF”.
  • What you expected, and what happenedBoth halves. The gap between them is usually where the bug is.
  • The exact error textCopy it out or attach a screenshot. “It said an error” and the actual message lead to very different investigations.
  • Which CV and templateThe CV's name and which of the four templates it was using. The name alone is enough to find the record.
  • Browser and operating system“Safari 18 on macOS”, “Chrome on Windows 11”. Rendering bugs are very often specific to one engine.
  • Whether it happens every timeOnce, or reliably? A reproducible bug is usually fixed the same week; an intermittent one needs the timestamp of when it happened.
AI and privacy questions

Send these to the privacy address

They get treated as formal requests rather than general correspondence, and they are answered specifically rather than with a link to a policy.

Your data

Ask for a copy of everything held for your account, ask for your account and its contents to be deleted, or ask for something to be corrected. Email from the address the account is registered under, or the request cannot be tied to you safely.

Individual CVs you can export yourself at any time from the editor sidebar — no request needed.

The AI review

Questions about what is transmitted when you run a check are answered precisely, because the answer is defined in code rather than in a policy. An anonymised copy of your CV goes to DeepSeek, an external AI provider, and only when you click Run — nothing is sent while you are writing.

The help centre lists exactly what is removed, what is replaced with a label, and what is never sent at all.

One thing worth stating plainly. Your CVs are encrypted at rest, and Tessira holds the key — deliberately, so that a password reset can restore your data rather than destroy it. That means it is not end-to-end encrypted, and you will not be told otherwise. If that trade-off matters to your situation, ask and it will be explained in full.
Before you write

Quick answers to what usually gets asked

How quickly will I get a reply?

Usually within a few days. There is no service-level agreement to quote, and inventing one that a single person cannot honour would be worse than telling you the truth. Account lockouts and anything preventing you from getting a CV out are looked at first.

Is there a phone number or a live chat?

No. There is no phone line, no chat widget and no postal enquiries desk — a studio of one cannot staff any of them, so none are advertised. Email is the only route, and it genuinely reaches the person who built the app.

Can you look at my CV and tell me if it is any good?

That is what the AI review inside the app is for, and it will be more thorough than a quick opinion over email — it measures your CV, quotes the specific lines that are weak and suggests rewrites. The CV writing guide covers the judgement calls no tool should make for you.

I have an idea for a feature or a template.

Send it to hello@cubicpixel.co and say what you were trying to do when you wanted it — the problem is far more useful than the proposed solution. Requests from people who are actually applying for jobs are the only product research this thing has.

I think I have found a security issue.

Please report it to privacy@cubicpixel.co with enough detail to reproduce it, and please give it a reasonable window before disclosing it anywhere public. There is no bug bounty to offer, but a genuine report will be taken seriously, acted on and credited if you want to be.

Are you hiring?

Not at the moment — there are no open roles, and the careers page says so plainly rather than keeping a vacancy board warm. It also explains what a speculative message would need to contain to be worth sending.

Most questions are already answered

The help centre covers accounts, the editor, templates, PDFs, the AI checks, privacy and the things that commonly go wrong. Worth a look before you write.