Drytis only works if founders trust us with the thing they're building. This page says plainly what we do with your code and data — and what we don't.
When you build with Drytis, your project's code and the data you paste into our tools are processed to run the service: AI models generate code, our engineers review and finish builds, and our support tooling needs enough context to help you. [PLACEHOLDER — this summary must be reviewed against actual data-handling practices before publishing: exact storage duration, which subprocessors (model providers, hosting) see customer code, encryption at rest and in transit, and deletion-on-request policy are all pending confirmation from whoever owns data operations.]
One concrete commitment we can make today: any snippet you submit for review runs once, is sent to the review model for analysis, and is not stored.
Everything Drytis builds — AI output and engineer work alike — is delivered to you and is yours. We don't reuse your code, train on it, or resell it.
Submitted snippets are analyzed and thrown away. No storage, no retention, no reuse.
Vetted Drytis engineers are assigned to your build and work on your code to complete it. Access is scoped to the work. [PLACEHOLDER — offboarding/revocation specifics pending confirmation.]
[PLACEHOLDER — list of subprocessors (model providers, infrastructure) pending confirmation before publishing.]
If you've found a security issue or have a question about how we handle data, reach the team at [SECURITY CONTACT — pending]. [PLACEHOLDER — confirm the dedicated security address or route before publishing; a real mailbox must exist before this goes live.]
See pricing ↗