Everything people ask. Missing something? Drop us a line.
Skub is for anyone whose inbox has become a daily source of stress — founders, freelancers, operators, small-business owners — who want to stop living in Gmail. Most of your email gets handled silently; only what actually needs you reaches your messaging app, as a decision you can make in two taps.
It's also for small teams with a shared inbox — support@, hello@, info@ — who need customer email handled without the overhead of a full helpdesk. Skub answers what it can from your knowledge base and pings a human on Telegram for the rest.
No — that's the point. Skub reads your mail, decides what needs you, and sends it to your Telegram. Everything else it handles in the background. If you never open the inbox again, Skub still works.
No. Skub starts handling your inbox the moment you connect Gmail and link Telegram. You teach it by reacting — every tap in Telegram (VIP, Ignore, Reply, Snooze) updates what the AI knows about you. A configuration page exists for granular control; most users never open it.
Yes — passively. Every tap is training signal: VIP teaches Skub a sender matters, Ignore teaches it to silence, Reply teaches it your voice (so drafts sharpen over time), Snooze teaches it your cadence. No separate training mode — it learns continuously from how you react.
Gmail today. Outlook and IMAP are on the way. You can connect multiple mailboxes on the paid plans — personal, work, side-project, all in one stream.
Only new mail arriving after you connect, and only briefly, in memory. Email content is never stored on our servers. Short summaries of what Skub decided for you (“skubs”) live in hidden labels inside your own Gmail — you can see them, delete them, take them with you.
Every skub arrives with buttons — Reply, Archive, Move, Ignore, VIP, Snooze. Tap once and Skub does it on your behalf in the real mailbox. Tap Reply and Skub drafts three replies in your voice for you to pick from.
You don't need to. Skub learns from every tap you make in Telegram — VIP, Ignore, Reply, Snooze — and adjusts what the AI knows about you. Most users never open the rules page. If you want explicit patterns (Pro/Business), you can: write *@newsletter.com → ignore or Invoice* → Finance in two clicks, or just tell Skub in chat: “always ignore @example.com”.
Two plans. Personal is €7/month — 2,000 skubs, up to 3 mailboxes, pattern rules, plain-English chat, priority support. Business is €15/month — 20,000 skubs, up to 100 mailboxes, auto-reply grounded in your own knowledge base (product catalogue, FAQs, support docs) for shared inboxes like support@ or info@, plus Admin API + MCP server.
No. Skub is €7/month for Personal, €15/month for Business. Cancel anytime from Settings → Billing — you keep paid features until the end of your billing period.
Yes. Cancel from Settings → Billing. You keep paid features until the end of your current billing period. Your learned data, rules, and skub history stay in your own Gmail — nothing is deleted when you cancel.
Yes, upgrade or downgrade anytime from Settings → Billing. Downgrading Business → Personal keeps every existing mailbox connected; you'll just hit the 3-mailbox cap on new connects until you upgrade again.
Yes, for regulated industries or internal-only deployments. Contact us for a self-hosted install in your environment with your own LLM keys and mail credentials — no customer data in our cloud.
You pick one of three tiers: Full (read + organize + send — recommended), Triage (read + organize), or Notify (read only). Lower tiers disable features. Permanent-delete is never requested in any tier.
You can change a mailbox's tier any time from Settings — Skub revokes the old token at Google and re-consents with narrower scopes. Not “trust us”; verifiable.
Yes. Every read, archive, label, move, send, draft, rule fire, OAuth consent, tier change, and disconnect is written to a per-user audit log visible on your Settings — with a “Why?” expander for Skub actions showing the rule that fired. Downloadable as CSV.
EU-hosted (Amsterdam), tokens in a dedicated key-management vault, every decryption audit-logged, no AI training on your data. We don't maintain a database of your email content or learned preferences — it stays under your control. Details on our security page. DPA + DPIA available on request.
We don't maintain a database of your emails, skubs, sender states, rules, or learned preferences. Everything Skub derives from your inbox lives in hidden labels inside your own Gmail — you own it, you can inspect it, and if you disconnect Skub, the data stays with you. Only operational state (your subscription, OAuth tokens in our vault) sits on our servers.
Yes — at connect time, advanced users can pick a different vault:
Honest caveat: in multi-tenant SaaS, Skub still holds a small credential to reach your external vault, so true “your keys, your infrastructure” only exists in a self-hosted install. At launch: Skub Vault default for SaaS; the others available in self-hosted today and on the SaaS roadmap. Details on the security page.
No. Zero-retention agreement with our AI provider, and we don't have a database of your data to train on ourselves.
Skub doesn't store your email content or learned history. A subpoena to Skub returns your OAuth token and subscription status. Subpoenas for your email go to Google.
Two lanes: message @skub_me_support_bot on Telegram for instant AI product help, or use the contact form for self-hosted, security, DPA, DPIA, or anything a human should see.
Provenance Tags ApS · Denmark