Uploads are temporary
Uploaded images and PDFs are used to create the explanation. The original uploaded file is not saved in Secure History and is not intended to be retained after processing completes.
Security
DocPlainly is designed to keep the upload flow clear, temporary, and transparent about AI processing.
Your selected file is sent for AI processing to generate a plain-language explanation. DocPlainly does not save the original uploaded file in Secure History. Saving an explanation is optional: free accounts can keep up to 3 explanations in local browser history on one device, and paid subscribers can keep more saved explanations or use encrypted Secure History.
Uploaded images and PDFs are used to create the explanation. The original uploaded file is not saved in Secure History and is not intended to be retained after processing completes.
Document content may be sent to AI providers such as OpenAI to generate explanations. AI provider terms, availability, and model limits may also apply.
DocPlainly does not use uploaded documents, Secure History, or follow-up questions to train DocPlainly-owned AI models.
DocPlainly never saves explanations automatically. Free accounts can keep up to 3 explanations in Secure History on one device. Paid subscribers can keep more saved explanations and add encrypted cloud access with their own recovery key or DocPlainly-managed access.
If you keep your recovery key, DocPlainly cannot recover encrypted Secure History if that key is lost. If you use DocPlainly-managed access, signed-in devices can unlock Secure History more easily, but that option is not customer-only key custody.
Access to account and service data is limited to people and systems that need it to operate, secure, troubleshoot, support, or comply with legal obligations for DocPlainly.
DocPlainly uses providers such as Vercel, Supabase, OpenAI, Stripe, Resend, and TrustedSite to host, secure, process, certify, bill for, and support the service. TrustedSite operates the visible site-certification trustmark and a limited visit signal described in the Privacy Policy.
Paid checkout and billing management are handled through Stripe-hosted pages, so card details are not stored in DocPlainly frontend code.
The public site uses HTTPS, and server-side services are designed to use encrypted connections for account, billing, and support data.
Crop documents before uploading when possible, and only upload documents you have permission to submit for AI processing.
If a security incident affects information covered by law, DocPlainly will investigate and provide notices required under applicable federal or state law.
Original uploads are not intended to be retained after processing completes, except for narrow temporary technical, security, troubleshooting, or legal needs described in the Privacy Policy. A temporary copy of the current analysis may remain in this browser session for up to 30 minutes so the upload and result screens can work together; it is not Secure History. Explanations in Secure History on this device stay until you delete them or clear browser storage. Explanations in encrypted Secure History stay until you delete them, reset Secure History, delete your account, or an enabled auto-delete period applies. The original uploaded file is never included in Secure History.
DocPlainly is a reading aid for dense wording. It should help you understand a document, but it is not a replacement for checking the original source.