The short version: We collect your email to notify you about Valkr. If you're a customer, we store your company's documents to power your bot — they're yours, they're isolated, and we never use them to train AI models. We don't sell data. Ever.
1. Who we are

Valkr is an AI-powered Slack bot service operated from Florida, United States. We help companies answer internal questions using their own documentation. Questions about this policy can be directed to [email protected].

2. What we collect

We collect only what we need to provide the service:

  • Email addresses — submitted via our waitlist or signup form, used to notify you about Valkr and manage your account.
  • Account information — your name, company name, and email when you create a dashboard account.
  • Slack workspace data — your Slack team ID, team name, and an encrypted bot token when you connect your workspace via OAuth. We do not store Slack message history beyond what is needed to answer a query and log it.
  • Documents you upload — the files you upload to power your bot (PDFs, Word docs, Markdown). These are stored in isolated tenant storage in Supabase.
  • Query logs — questions asked to your bot, answers given, confidence scores, and whether questions were escalated. These are stored per-tenant and used to improve your knowledge base.
  • Usage events — query counts used for plan limit enforcement and billing.
3. How we use your data
  • To operate the Valkr service — answering questions, escalating to admins, logging gaps.
  • To send you product updates and launch notifications if you joined the waitlist.
  • To enforce plan limits and process billing via Stripe.
  • To improve service reliability through error monitoring via Sentry.

We do not use your documents or query logs to train AI models. We do not sell your data to third parties. We do not use your data for advertising.

4. Data isolation and security

Every customer's data is isolated at the database level using row-level security. Your documents are stored in a tenant-scoped storage bucket that no other customer can access. Slack tokens are encrypted at rest using AES-256-GCM.

Documents are uploaded directly from your browser to isolated storage via presigned URLs — they never transit our application servers.

5. Sub-processors

We use the following third-party services to operate Valkr:

  • Supabase — database, vector storage, and file storage (US region).
  • OpenAI — document embedding and AI query responses. Queries are processed under OpenAI's API terms; data is not used for model training under our usage tier.
  • Stripe — payment processing and subscription billing.
  • Formspree — email capture form submissions on our marketing site.
  • Sentry — error monitoring and performance tracking.
  • Railway — application hosting.
  • Cloudflare — DNS, CDN, and DDoS protection for our marketing site.
6. Data retention

We retain your data for as long as your account is active. If you cancel your subscription, your data is scheduled for deletion after a 30-day grace period. You can request immediate deletion by emailing [email protected].

Waitlist email addresses are retained until you unsubscribe or request removal.

7. Your rights

You have the right to:

  • Access the data we hold about you.
  • Request correction of inaccurate data.
  • Request deletion of your data.
  • Export your data in a portable format.
  • Withdraw consent for email communications at any time.

To exercise any of these rights, email [email protected].

8. Cookies

Our marketing site (valkr.ai) does not use tracking cookies or third-party analytics. The dashboard (app.valkr.ai) uses a session cookie from Supabase Auth to keep you logged in. No advertising cookies are used anywhere.

9. Changes to this policy

We may update this policy from time to time. Material changes will be communicated via email to active customers with at least 14 days notice. The date at the top of this page reflects the most recent update.

10. Contact

Questions, requests, or concerns about this privacy policy should be directed to [email protected].