Compliance docs generated from your actual code.
Connect a repository or upload a zip. Synlex drafts policies from the processors, data flows, and platforms it finds. You review every line before a signed release.
Templates go stale
A rescan marks accepted drafts stale when the plan changes
You guess the processor list
The scan names services the repo imports
A policy with no source
A versioned release signed over the accepted drafts
How it works
Five steps from a repository to a signed release.
- Connect, current
- Scan
- Review findings
- Fill the blanks
- Accept and sign release
1 of 5
Connect
Install the GitHub App on one repository, or upload a zip. Synlex stores the repository id and default branch. It does not store the files.
2 of 5
Scan
The worker reads manifests and a sample of source. It records dependency names, versions, and signals such as trackers, Prisma fields, and platform permissions. File text is discarded.
3 of 5
Review findings
Runtime services that receive data show up as processors. You confirm a finding or mark it not applicable. Libraries that do not receive data stay off the processor list.
4 of 5
Fill the blanks
The wizard asks for what the repository cannot show: legal name, retention, minimum age, refund rule, governing law, and the other answers a draft needs.
5 of 5
Accept and sign release
Nothing is stored as accepted until you accept it. An owner or compliance lead then signs a versioned release. The manifest is Ed25519-signed and the version must rise.
Product
What the scan can actually tell you.
Dependency and processor detection
npm, CocoaPods, Swift Package Manager, Gradle, and pip are matched to the vendor registry. A processor is a runtime service in a category that receives data.
Data-flow and platform mapping
Web storage and tracker calls, Prisma fields, iOS usage strings, and Android permissions are recorded. Platforms follow what the scan and your answers support.
Guided wizard
Taxonomy and commercial steps collect the facts a scan cannot prove. Accept stays blocked until the required answers exist.
Generated document set
Drafts are compiled from the plan. A privacy policy, cookie policy, and subprocessor list are included when the scan supports them, along with the other documents that evidence calls for.
Signed, versioned releases
The release binds the accepted drafts, the plan digest, and the scanned commit. The signature is Ed25519. The public key is published when a signing key is configured.
Rescans on push
A push to the connected default branch queues another scan. The diff shows what was added, removed, or changed. A new plan digest makes accepted drafts stale until you accept them again.
Teams and roles
Workspaces have owners, admins, compliance leads, developers, and viewers. Seats follow the plan meter. Only an owner or compliance lead can sign a release.
Drafts
A document set, with the scan lines marked.
Sample excerpt for a fictional app, Northwind Notes. It shows the shape of a draft. It is not your policy, and it is not legal advice.
Who we are. Northwind Notes provides a notes app to its customers.
Data we collect. Account email, and payment card details sent to the payment processor.
Stripe — payments. Named because the repository depends on Stripe.
From the scan
PostHog — product analytics. Named because the repository depends on PostHog.
From the scan
Sentry — error diagnostics. Named because the repository depends on Sentry.
From the scan
OpenAI — prompts sent to a model. Named because the repository depends on OpenAI.
From the scan
You review this draft and accept it before it can be released.
Security
What Synlex does with the code, and what it does not.
The scan reads. It does not write to your repo.
GitHub access is Contents read, Metadata read, Pull requests read, and Checks write. A scan uses a short-lived installation token. The token and the file text are not stored. Synlex does not commit or push. A zip upload is the path that does not install the app.
Workspace data is isolated in the database.
Each workspace’s rows are separated with row-level security. That is database-enforced isolation. It is not a claim of per-tenant encryption keys.
Releases are signed and versioned.
An owner or compliance lead signs after a fresh authenticator code or passkey. The manifest covers the version, the commit, the plan digest, and each document hash. The algorithm is Ed25519. The public keys, current and retired, each with the dates it was in use, are at /.well-known/synlex-keys.json when a signing key is configured.
You review everything before it ships.
Generate can preview a draft. Accept is what stores it, and only if the draft still names the plan’s evidence. A release is refused while an answer is missing or a document is unaccepted or stale.
Security notes, including what is not claimed. Public keys, when signing is configured: /.well-known/synlex-keys.json
Pricing
Plans from the billing catalog.
Free
$0 No charge
USD
- Monitored apps: 1
- Monthly scans: 25
- Seats: 2
- Active portals: 1
- AI-polished documents: 0
- Wizard autofills: 1
- Recommended
Growth
$49 / month
USD, tax exclusive
- Monitored apps: 5
- Monthly scans: 500
- Seats: 5
- Active portals: 5
- AI-polished documents: 7
- Wizard autofills: 20
Checkout opens from workspace billing after you sign up.
Scale
$199 / month
USD, tax exclusive
- Monitored apps: Unlimited
- Monthly scans: Unlimited
- Seats: Unlimited
- Active portals: Unlimited
- AI-polished documents: Unlimited
- Wizard autofills: Unlimited
Checkout opens from workspace billing after you sign up.
Enterprise
Custom
Contact sales
- Monitored apps: Unlimited
- Monthly scans: Unlimited
- Seats: Unlimited
- Active portals: Unlimited
- AI-polished documents: Unlimited
- Wizard autofills: Unlimited
Questions
Is this legal advice?
No. Synlex is not a law firm, and a draft is not legal advice. Drafts are grounded in your code and in the answers you enter. You review and accept them before a release. Do not describe the result as fully compliant.
Which languages and frameworks are supported?
Manifests: npm (package.json and lockfiles), CocoaPods, Swift Package Manager, Gradle, and pip (requirements.txt and pyproject.toml). Source signals use tree-sitter for JavaScript, TypeScript, TSX, and Swift. Prisma models, iOS Info.plist usage strings, and Android permissions are read. Python, Java, and Kotlin source grammars are not loaded. A Rails Gemfile is not treated as a finding.
What access does GitHub get?
The GitHub App asks for Contents read, Metadata read, Pull requests read, and Checks write. Each scan mints a short-lived installation token. That token is not stored, and file text is not stored. Synlex does not commit or push. You can upload a zip instead of connecting a repository. Pull-request check runs are not available yet.
What happens when the code changes?
A push to the connected default branch queues a scan. The scan records what was added, removed, or changed since the previous one. If the compliance plan changes, accepted documents are stale and have to be accepted again before the next release.
How do I cancel?
An owner opens the billing portal from workspace settings and cancels there. Plans are monthly. The plan config has no annual term and no cancellation fee. This page does not state a refund amount, because the plans do not define one.
Scan the repository you already have.
The draft names the processors in that code. You decide what ships.