Viktor

Description Features Permissions Security & Compliance

Most AI gives each person a private assistant. Viktor is different. He's one AI employee your whole team shares, working in the Slack channels you invite him to.Multiplayer by design. Add Viktor to the channels you want him in, and anyone on the team can put him to work. He builds on shared context, so nobody has to re-explain the company to a fresh chatbot every time.
And he does the actual work. Viktor connects to 3,200+ tools you already use (Stripe, HubSpot, Meta Ads, Notion, GitHub, and more) and delivers finished output: a board-ready PDF from last month's ad spend, a live dashboard built and deployed from a single message, a Monday report that runs itself every week.What that looks like:
- One shared employee for the whole workspace, not one-assistant-per-seat.
- Shared memory: Viktor remembers your company's context, not just one person's chat history.
- Proactive: he notices the work your team repeats and offers to take it over.
- You stay in control: you choose the channels and tools Viktor can access, and he asks before anything sensitive or hard to undo.
- Real deliverables across your stack: reports, dashboards, web apps, code, and pull requests.Start free with $100 in credits per workspace. No credit card, no sales call. Paid plans from $50/month. Enterprise plans available. https://viktor.com/pricingGet Started for Free: https://viktor.comAI Disclaimer: Viktor uses AI to generate responses and perform tasks. While we strive for accuracy, AI-generated content may occasionally contain errors or inaccuracies. Review important outputs before acting on them.

Viktor will be able to view:

Viktor will be able to do:

Review the details to better understand this app’s security practices. To learn more about assessing apps for your workspace visit our Help Center.

General

Privacy & data governance

Data retention policy

We retain Customer Data for Viktor (including connection credentials, basic workspace/user identifiers, workspace settings, files stored in Viktor, conversations and outputs generated in Viktor, scheduled tasks, approval decisions, and service logs) only as long as needed to provide the Service, meet contractual obligations, and comply with law. When an account is closed or we receive a validated deletion request, we delete Customer Data from active production systems typically within ~30 days; remaining copies are removed as encrypted backups age out on their normal rotation (currently ~35 days). Viktor may store Slack messages and channel history from conversations it is authorized to access to maintain context and provide search and requested work. Slack content is subject to workspace access controls and our retention/deletion policies. We do not use Customer Data for advertising, and we do not train our own or third-party foundation models on Customer Data.

Data archiving and removal policy

We maintain documented retention and disposal procedures for production systems, logs, and backups. Customer-initiated deletions (e.g., account closure or DSR requests) trigger account removal, deletion/anonymization of associated Customer Data, and de-provisioning of access credentials (including OAuth tokens). Backups are encrypted, used only for business continuity, and are automatically overwritten or purged at the end of their retention period. Where legally permitted, customers may request an export prior to deletion.

Data storage policy

Customer Data is stored in encrypted databases (AWS RDS PostgreSQL) and encrypted object storage (Cloudflare R2) in US regions. Data is encrypted in transit (TLS 1.2+/1.3) and at rest (AES-256 with cloud-provider key management). Access is restricted via private networking, RBAC, MFA, and logging.

Data center location(s)

United States

Data hosting details

Viktor is a cloud-hosted, multi-tenant SaaS using managed compute, databases, and storage services. Application compute and isolated workspace sandboxes run on Modal, the frontend is hosted on Vercel, and managed storage includes PlanetScale, ClickHouse, Modal volumes, and Cloudflare R2. Access to customer data is restricted to authorized services and personnel.

Data hosting company

PlanetScale, ClickHouse, Modal, Cloudflare, Vercel, Amazon Web Services, and Google Cloud Platform

App/service has sub-processors

yes

Guidelines for sub-processors

https://get-viktor.notion.site/subprocessors

App/service uses large language models (LLM)

yes

LLM model(s) used

Anthropic Claude, OpenAI GPT, and Google Gemini, with additional optional models depending on workspace settings. Current AI-provider details: https://viktor.com/legal/privacy (section 4.B).

LLM retention settings

Within Viktor, LLM prompts and outputs are stored only as long as needed to provide product functionality (e.g., to show previous drafts or conversation context) and are governed by our general data-retention policy described below.

LLM data tenancy policy

LLM processing is performed on enterprise, multi-tenant model endpoints operated by our AI providers; customer prompts and outputs are logically segregated by authentication scopes and customer identifiers.

LLM data residency policy

AI providers process data in the United States or other regions used by those providers under their enterprise/API terms. Our current residency and transfer policies are described in https://viktor.com/legal/privacy and our Data Processing Agreement.

Certifications & compliance

Security