Guidelines for KemitVPN, KemitPass, Kemnir, KemDoc, RoamVeil and the KemitSecurity parent brand — covering logos, colors, typography, and voice.
The umbrella identity for all products, communications, and company-level materials.
Speak plainly. Avoid jargon for its own sake. We explain our security in terms anyone can verify — not to show off, but because hiding behind complexity is exactly what we're fighting against.
Make strong claims and back them with evidence. Say "we don't log your traffic — ever" rather than "we try to minimise data collection." Hedge only when you must; own your promises.
Privacy matters deeply to us, but we don't moralize at users. We explain what a threat is, show how we solve it, and move on. Let the product speak louder than the ideology.
Use contractions, short sentences, and active voice. Write like you're talking to someone who's smart but busy — not a compliance document reviewer.
"We don't keep logs. Not because we're legally required not to — because we never wanted to."
"KemitSecurity is committed to leveraging best-in-class privacy solutions to empower our valued users."
Military-grade encryption, zero-log policy, 750+ servers. The VPN that takes no shortcuts.
"Your internet. Nobody else's business."
KemitVPN talks like a shield — steady, technical, and uncompromising. Lead with capability, follow with trust signals. Avoid vague promises; cite the spec (AES-256, WireGuard, no-log audit). The product is the argument.
Zero-knowledge password management. Your vault. Your keys. No exceptions.
"One vault. Only yours."
KemitPass speaks like a trusted vault keeper — calm, precise, and intimate. The tone is warmer than KemitVPN because password management is personal. Emphasize ownership and control. Avoid any language that implies KemitPass can see your data — because it can't.
Tunnels and relays. Reach anything you run, without opening a port.
Naming note: Kemnir is the one product that does not carry the Kemit prefix as a separate word — it is a single word, always written Kemnir, never KemNir or Kemit Nir. It sits in the family by colour and by mark, not by name.
"Without opening a port."
Kemnir talks like a competent friend who has already read the router manual — plain, unhyped, and willing to say what it can't do. The audience includes teenagers hosting Minecraft, so no enterprise vocabulary. Where KemitVPN cites the spec and KemitPass reassures, Kemnir admits the limits out loud — that candour is the differentiator against the incumbents, not a caveat to bury.
Kemnir carries two claim restrictions that override any copy brief. They exist because reputation in server-hosting communities is the entire asset, and a single unbacked claim spreads faster than any campaign.
Not on a page, an ad, or a social post — until the layer-7 filtering work is finished and tested. Permitted instead: "your home IP is never exposed" and "attacks hit our network, not your router." Both are architectural facts, true from day one.
No millisecond figures, no "lowest latency" claim, no comparison chart — the go/no-go latency test has not been run. Describe the mechanism (nearest-edge selection) rather than a result.
E-signature with a zero-knowledge vault. Sign it, seal it, and keep the keys.
KemDoc is the only Kemit product on a light ground, and that is deliberate. Every other product in the family sits on the near-black ink ramp. KemDoc sells documents, so its surface is paper: a warm off-white with faint horizontal rules, editorial serif headlines, and ruled rows in place of glow cards. If a future redesign "brings it in line with the family", the distinction is lost — the shared identity lives in the wordmark and the Kemit footer line, not in the background colour.
Newsreader (serif) for headlines, brand and row titles; Inter for body; JetBrains Mono for eyebrows, captions and stamps. KemDoc is the only product in the family using a serif — it reads as contract and record rather than console.
"Get it signed. Keep it private."
KemDoc speaks to a professional who is liable for what they send — an accountant, a solicitor, a clinician. Precise, unhurried, and specific about limits. Where KemitPass reassures, KemDoc documents: it states what is true, names what it cannot do, and never rounds a technical fact up into a slogan.
KemDoc makes cryptographic and legal claims, which is exactly where a marketing sentence turns into a liability. Two rules override any copy brief.
The honest answer to can Kemit read my documents is not at rest. Never write a flat "we can never see your files": metadata is always visible to us, and it has to be for a signature to mean anything. Say what is true and say why.
E-signature law differs by country and by instrument, and some documents cannot be executed electronically at all. Describe what KemDoc produces — a sealed document, a trusted timestamp, a completion certificate — and name specific standards only once assessed against them.
Encryption is never a paid feature, and the vault never locks for non-payment. Free accounts get the same vault, seal, timestamp and certificate as Business; a lapsed account keeps read, download and export access forever. These are brand constraints before they are commercial ones — a privacy company that sells security as an upgrade has conceded that its free users don't deserve it, and the community will say so within a day.
Privacy-first travel eSIM. Formerly KemitSIM — renamed July 2026.
Naming note: RoamVeil carries no Kemit prefix at all — one word, always RoamVeil, never Roam Veil or Roamveil. It belongs to the family by ownership and footer attribution, not by name.
RoamVeil moved off Kemit purple when it became standalone. The purple belongs to KemitSecurity and KemitPass, and borrowing it made a consumer travel product look like a security tool.
Text on the accent is dark ink (#1A0F0A), never white. White measures 2.82:1 on the coral and 2.15:1 on the amber — both fail WCAG AA. Dark ink measures 6.68 and 8.76. This is the one rule to not undo by eye.
"Travel, privately."
RoamVeil is the most consumer-facing brand in the family and should read that way: warm, plain, and free of security jargon. The buyer is an anxious traveller, not an engineer — no monospace tics, no "zero-trust", no threat modelling. Lead with the trip, land the privacy point second.
The country-to-region mapping behind the destination search is an approximation until the upstream vendor's coverage list is confirmed. Telling someone their eSIM works where it does not is the worst failure this product has — it strands a customer abroad.
A device list ages badly and cannot see a carrier lock or a China-market handset without eSIM hardware. Every compatibility claim must point at the *#06# EID check as the authority.
Three products no longer carry the Kemit prefix. That is a decision, not a drift — but it needs stating so the next one is chosen deliberately.
The odd one out: neither fully prefixed nor fully standalone. If consistency ever matters more than the existing domain, KemitDrop and KemitSend were the alternatives considered.
Both sell to audiences who have never heard of Kemit — gamers and travellers. A standalone name is an asset there, so long as the ownership is stated in the footer.
Prefix when the buyer is already a Kemit customer or is buying because it is a security company. Go standalone when the product competes in a category where "security company" is not the reason to buy. Don't split the difference again — that is how KemDoc ended up in the middle.