https://app.slancha.ai/assets/Privacy-DVkRPsNF.js

1import{j as e}from"./app-DeursVD0.js";import{L as n}from"./LegalPage-DYHyjCeQ.js";import"./react-vendor-CkgV0jl3.js";import"./supabase-J7ITh-P0.js";import"./index-CAEiRUxS.js";const o=`# Privacy Policy
2
3Effective date: [DATE]
4
5This policy covers Slancha as we host it: the console at \`app.slancha.ai\` and its API. Slancha, Inc. runs it. [LAWYER: confirm the registered address: [ADDRESS].]
6
7Slancha also runs on your own machines. A self-hosted deployment sends us nothing, and this policy does not describe it.
8
9**By using Slancha you agree to this policy.** Creating an account, signing in, connecting an agent, tracing tool or other system to Slancha, or uploading or otherwise submitting data to it means you agree to this policy and to the [Terms of Service](/terms), for yourself and for the organization you act for, and that you have the right to share that data with us.
10
11## 1. What we hold
12
13**Account.** Your email, and your name and profile picture if you sign in with Google. Supabase stores the account and the password. We never see a password.
14
15**Organization.** The organization name, its member list with each member's email and role, and the audit trail of who approved, rejected, or rolled back what.
16

17**Machines.** A machine name, a fingerprint the machine sends at enrollment, the hash of its token, its capabilities, and when it was last seen. We store the hash, never the token.
18
19**Provider keys.** The OpenAI API key you supply, and any key for another provider saved before the hosted service moved to OpenAI, until you delete it. Each is sealed with AES-GCM, per organization, under a key held outside the database. We never return a key value and never log one.
20
21**Skills you upload.** The exact bytes of the package, its review findings, its versions, and the snapshots we keep so you can roll back.
22
23**Episodes you upload.** Transcript projections from your agent sessions. Your machine scrubs them before they leave it, and it sends a projection, not the raw transcript: completed prompts, final answers, the skills that were loaded, timings, token counts, and error counts. It excludes reasoning, attachments, tool arguments and results, and subagent threads. Even so, a prompt can hold anything someone pasted into it. Treat what you upload as sensitive and scrub before you send.
24
25**Reports and logs.** Audit reports, coverage reports, publication receipts, and the log of each job you run, including its cost estimate.
26
27**Web analytics.** The console pages load Plausible and, when configured, PostHog. PostHog records page views and interactions and stores analytics state in your browser's local storage. After sign-in, Slancha identifies your PostHog profile with your account ID and email domain. Anonymous visitors are not assigned person profiles by this configuration. PostHog is configured to respect Do Not Track.
28
29**Support.** Anything you send us by email.
30
31## 2. Why we hold it
32
33To run the service you asked for: sign you in, keep your organizations apart, run the jobs you start, show you the evidence, and serve your approved library to your machines. To keep the service secure and to investigate abuse. To answer your support mail. To tell you about changes to the service.
34
35We do not sell your data. We do not use your content to train models. We never use one organization's content to serve another. We do not advertise to you and we run no ad trackers.
36
37## 3. Where it goes
38
39We use third-party service providers to operate Slancha, including providers of cloud hosting, databases and storage, content delivery, authentication, email, trace storage and observability, analytics, payments, AI model inference, and evaluation and classification. We share the information described in this policy with them to the extent needed to provide, secure, evaluate, support and improve the service. They process it on our behalf under their own terms and security practices, in the United States and in other countries, and we may add, remove or replace providers at any time. [LAWYER: full subprocessor list with each one's role and location, published and kept current. The list above is what the stack uses today and is not a legal disclosure.]
40
41Beyond those providers, we share information only when the law requires it, to protect Slancha, its users or others, in a merger, financing or sale of the business, or when you ask us to.
42
43## 4. What leaves for model providers
44
45Running a job sends prompts, answers and the skill content it works on to OpenAI. Hosted jobs call OpenAI directly with the key your organization supplied, on OpenAI's flex tier, with response storage turned off (\`store=false\`). OpenAI's own terms and retention apply to what it receives.
46
47To write or improve a skill from traces, a job sends scrubbed excerpts of your organization's agent sessions to that same model provider, on your organization's own key. An org admin acknowledges this each time.
48
49Two parts of Slancha's privacy posture hold on a self-hosted install and **do not hold here**. O

49n your own machine Slancha sends no telemetry and binds to localhost only, so nothing leaves except the model call; a self-hosted install may route that call through OpenRouter, asking it for zero-data-retention routing with \`data_collection: deny\`. In the hosted service we store what you upload, what your connected tools send, what your jobs write, and the reports and logs above, with the service providers described in section 3.
50
51## 5. Browser storage
52
53The console uses Supabase's browser session storage to keep you signed in. Where browser local storage is available, Supabase stores the session there. PostHog also uses local storage for analytics state. The app does not configure PostHog cookie persistence. We use no advertising cookies.
54
55## 6. How long we keep it
56
57Retention periods and deletion procedures are not finalized in this draft. It does not establish a deletion deadline or a backup-retention period. Snapshots of superseded skill versions are stored so you can roll back. [LAWYER: establish and verify retention periods and deletion procedures for account data, sessions, job logs, audit trails, skill versions and backups against the deployed service.]
58
59## 7. Your rights
60
61Depending on where you live you can ask us to show you the personal data we hold about you, correct it, delete it, export it, or stop processing it. You can withdraw consent where consent is the basis.
62
63The console lets authorized members remove a member, revoke their own personal tokens, and delete a provider key. Contact [email protected] for account or organization deletion requests; this draft does not establish a completion deadline.
64
65Write to [email protected] and we will answer. [LAWYER: response deadlines, identity verification, and the appeal path under GDPR, UK GDPR, CCPA, and any other regime the customer base reaches. Also name the legal basis for each processing purpose.]
66
67## 8. Where your data is processed
68
69We process data in the United States. [LAWYER: international transfer mechanism for EEA and UK customers, standard contractual clauses, and a transfer impact assessment.]
70
71## 9. Security
72
73What the system does today:
74
75- HTTPS everywhere, enforced at the edge.
76- Every path in the service is keyed to the organization bound to the request. An unbound request cannot read anything.
77- Provider keys sealed with AES-GCM, a fresh nonce per write, the master key outside the database. One process ever decrypts one, and only into the job you started.
78- Machine tokens compared by hash, in constant time, and revocable at once.
79- Roles gate every write. A machine token resolves as a viewer and is refused by every gate above it.
80- State-changing requests carry an origin check, and the API refuses a host header it was not configured for.
81- The audit trail records token digests, never tokens.
82- Approval is the only path to the served library, and every publication is a receipt you can read back.
83
84No system is perfectly secure. If a breach affects you, we will tell you. [LAWYER: breach-notification deadline and to whom, per jurisdiction.]
85
86## 10. Children
87
88Slancha is a tool for engineering teams. It is not for anyone under 18, and we do not knowingly collect data from children. [LAWYER: children's-data obligations and the right age floor.]
89
90## 11. Automated decisions
91
92Hosted Slancha does not score the quality of candidate skills. It scans changes for security problems and can propose changes from sessions. It never activates a proposal on its own; a person approves it. [LAWYER: review the automated-processing disclosure and whether any processing falls under GDPR Article 22.]
93
94## 12. Changes
95
96We may update this policy. We will tell you about a material change by email or in the console before it takes effect.
97
98## 13. Contact
99
100Write to [email protected].
101`;function d(){return e.jsx(n,{markdown:o,title:"Privacy Policy",description:"What Slancha holds when we host it, where it goes, how long we keep it, and your rights over it. Draft under legal review.",path:"/privacy"})}export{d as default};