Frequently Asked Questions

DocCraft offers a free tier that includes 10 document generations per month. Free accounts also get access to all standard document types (API Reference, README, User Guide, Admin Docs, Release Notes) and all export formats. Paid plans are available for teams and higher usage volumes — see the Pricing page for current plans.

Free-tier monthly generations reset on your account anniversary date each month. They do not roll over — unused generations in a given month are not added to the following month. Paid plan credits follow the same reset cycle unless otherwise specified in your plan terms.

Yes. You can upgrade, downgrade, or cancel from your Account Settings → Billing page at any time. Cancellation takes effect at the end of your current billing cycle. You retain access to all generated documents in your dashboard regardless of plan status.

Team plans supporting multiple users, shared projects, and centralized billing are on the roadmap for 2025. Currently, DocCraft is designed for individual users. If you need team access, contact the support email to discuss early access options.

Navigate to Account Settings → Privacy → Delete Account. This permanently deletes all your documents, generation history, and account data. This action cannot be undone. If you have an active paid subscription, please cancel it first to avoid further charges.

DocCraft accepts: OpenAPI/Swagger specs (.yaml, .json), Postman collections (.json), plain text and Markdown (.txt, .md), and code files (.js, .py, .ts, .go, .java, and others). You can also paste a GitHub repository URL directly — DocCraft will fetch the public repo contents.

Direct private repo ingestion via GitHub URL is not currently supported. For private repos, the recommended approach is to export a Postman collection, export your OpenAPI spec, or copy/paste relevant source files directly into the DocCraft input field. Full GitHub OAuth integration (including private repo access) is planned.

DocCraft uses a combination of large language models optimized for technical writing tasks. The specific model combination and version is not disclosed as it may change as the product evolves. The output is post-processed with terminology normalization and structure formatting passes to ensure consistency across generated sections.

Yes. In the Document Editor, hover over any section and click the Regenerate icon (a circular arrow). A prompt field will appear allowing you to give specific instructions for that section — for example: "Make this more concise", "Add a Python code example", or "Rewrite this for non-technical users". Section-level regeneration does not affect other sections.

Generated documents are stored in your dashboard for 90 days from creation date. After 90 days, documents are automatically deleted unless you have exported them or saved them to an integration. Free-tier users should export important documents promptly. Paid plan users may have extended storage — check your plan details.

Yes. DocCraft supports custom tone instructions (technical, approachable, concise), section inclusion/exclusion, and custom templates. In Advanced Settings, you can specify a company style guide summary, preferred heading hierarchy, and terminology preferences. These are applied to the generation prompt before processing.

When generating API references, DocCraft can produce code examples in Node.js, Python, cURL, Ruby, PHP, Go, and Java. Language selection is available in the Advanced Settings panel before generation. If your source is a typed language like TypeScript or Kotlin, DocCraft will maintain the original language for examples while offering translated examples in your selected secondary languages.

Go to Settings → Integrations → Confluence. You'll need your Confluence Cloud workspace URL (e.g., https://yourcompany.atlassian.net) and a Confluence API token. You can generate an API token at id.atlassian.com → Security → API tokens. Once connected, you can select a target Space and parent page before exporting any document.

Auto-push to GitHub is not yet available. Currently, you export your generated README as a Markdown file and commit it to your repository manually. A GitHub integration that allows direct push (including PR creation) is in active development.

Notion export via the Notion API is on the roadmap. Currently, the best workaround is to export your document as Markdown and use Notion's built-in Markdown import feature (Block menu → Import → Text & Markdown). Notion does not preserve all HTML structure from the HTML export, so Markdown is the recommended format for Notion.

A DocCraft REST API is in development and expected in 2025 H1. The API will allow trigger-based generation from CI/CD pipelines (e.g., regenerate API reference on every OpenAPI spec change) and programmatic export to connected destinations. Early API access is available — contact support if you have an enterprise use case.

Source material you upload is processed in-memory for generation and is not persistently stored after generation completes. The generated document output is stored in your dashboard (see storage policy above). DocCraft does not use your source code to train or fine-tune AI models. See the full Privacy Policy for details.

DocCraft processes data in compliance with GDPR. User data is stored in EU-region infrastructure. You can request a full data export or account deletion at any time from Account Settings → Privacy. Data deletion requests are fulfilled within 30 days of submission.

DocCraft can generate draft documentation for regulated products. However, all AI-generated content must be reviewed, verified, and approved by qualified human reviewers before use in production, regulatory submissions, or customer-facing materials. DocCraft output is a starting point, not a compliance-ready final deliverable.

By default, all documents are private — visible only to your account. DocCraft does not have a public sharing feature at this time. When you export a document, the exported file exists only on your local device. No team members, DocCraft staff, or third parties can access your documents without your explicit sharing action.