Starter terms.
Effective May 16, 2026. These launch terms are written for early access and should be replaced or reviewed by counsel before broad public launch.
Service
DevReadr provides codebase mapping, module positioning, best-practice suggestions, dependency notes, risk notes, and approval-gated correction-loop drafts. Starter access is early access and may change as the product matures.
No Raw Source Retention By Default
Starter is designed to connect to selected live repositories for scoped read/indexing without retaining raw source code by default. DevReadr may retain account details, billing references, repo or integration metadata, derived maps, summaries, citations, risk notes, and customer-approved artifacts needed to operate the service. Any enterprise workflow that stores raw source code must be agreed in writing.
Customer Responsibilities
Customers are responsible for having the right to connect or submit any repository, schema, document, or artifact. Customers should not submit secrets, credentials, regulated data, personal data, or third-party code they are not authorized to use.
AI Output And Review
AI-generated output can be incomplete, incorrect, insecure, outdated, or unsuitable for a customer environment. DevReadr output is decision support only. Customers are responsible for human review, testing, license review, security review, and production approval before using any suggestion.
No Professional Advice
Best-practice notes, risk notes, code suggestions, security observations, legal-adjacent notes, and compliance-adjacent notes are not legal, security, financial, compliance, or professional advice. Customers should use qualified professionals where appropriate.
Approval-Gated Actions
DevReadr may prepare draft patches, pull request plans, migration notes, deploy checklists, and workflow candidates. External actions such as pushing code, changing Supabase, deploying to Netlify, sending messages, or changing third-party systems require explicit customer approval or a customer-configured Mimi auto-push policy with provider-specific permissions.
Billing
Subscriptions are billed through Stripe. Stripe processes payment details under Stripe terms and privacy practices. Plan details, pricing, and availability can change for future customers; active customer terms are governed by the checkout, invoice, or signed agreement in effect at purchase.
Beta Limits
The service is provided on an early-access basis and may include errors, interruptions, missing features, changed features, or limited support. DevReadr does not guarantee that any suggestion will fix a bug, improve performance, prevent an incident, or satisfy a legal or compliance requirement.
Contact And Deletion Requests
Questions, deletion requests, support requests, and partnership requests can be sent to hello@devreadr.com.