Privacy Policy
DocEasy AI helps you understand administrative letters and documents. This policy explains what information is processed, where it is stored, and the choices available to you.
1. Information DocEasy processes
Documents you choose to analyze
When you explicitly approve an analysis, the selected PDF or image, including its contents and filename, is transmitted over HTTPS to the DocEasy hosted analysis service and then to OpenAI to generate the requested analysis or draft.
DocEasy does not copy the original uploaded file into its saved-case database. The backend processes the file for the request and does not intentionally write document contents or filenames to application logs.
Saved case information on your device
If you save a case, structured analysis data, the source filename, workflow state, verification choices, and reminder information are stored locally on your device. DocEasy currently has no account system or cloud case synchronization.
Anonymous installation and quota information
The app creates a random installation identifier on your device. It is sent to the backend so DocEasy can apply the free monthly analysis limit. The backend stores only a SHA-256 hash of that identifier together with monthly usage counts and timestamps.
Technical and security information
Network and request metadata, such as IP address, request path, response status, timing, and a request identifier, may be processed for security, rate limiting, reliability, and hosting operations. DocEasy does not use this information for advertising or cross-app tracking.
2. Why the information is used
- To analyze the document you explicitly submit.
- To generate structured explanations, deadlines, actions, evidence, and optional drafts.
- To maintain cases and reminders locally on your device.
- To enforce free usage limits and protect the service from abuse.
- To diagnose failures and keep the service secure and available.
3. Service providers
OpenAI
DocEasy uses the OpenAI API for document analysis and draft generation.
Requests are sent with Responses API storage disabled (store=false).
OpenAI states that API inputs and outputs are not used to train its models
by default unless the API customer opts in. OpenAI may retain abuse-monitoring
logs containing customer content for up to 30 days by default, unless
different approved data controls apply.
OpenAI data controls: platform.openai.com
Render
DocEasy uses Render to host the backend service and PostgreSQL database. Render may process infrastructure and network metadata needed to operate the hosted service. DocEasy does not intentionally store uploaded document files in the Render database.
Render privacy information: render.com/privacy
4. Retention and deletion
- Original document files: not intentionally retained by the DocEasy application after the analysis request completes.
- Saved cases: remain on your device until you delete the case, clear the app's local data, or uninstall the app.
- Quota records: pseudonymous monthly quota records are retained for up to approximately 13 calendar months and then removed by backend cleanup.
- OpenAI processing: subject to OpenAI's API retention controls described above.
You can delete saved cases directly in the app. For a privacy or deletion request concerning DocEasy backend data, email mayukhronty@gmail.com. The app's Privacy & Support screen shows the installation identifier that support may ask you to provide so the pseudonymous quota record can be located.
5. Your choices
Analysis only begins after you explicitly agree to send the selected document for AI processing. You can cancel instead, delete local cases, disable notification permission in your device settings, or contact support with a privacy request.
6. Security and limitations
DocEasy uses HTTPS for the production API and applies bounded uploads, request-rate controls, no-store response headers, and privacy-oriented application logging. No online service can guarantee absolute security.
DocEasy provides administrative assistance, not legal advice. Important deadlines, obligations, and legal consequences should be independently verified.
7. Contact
For privacy questions, access requests, or deletion requests:
mayukhronty@gmail.com