What to send in a good app support request
The fastest support path is a concrete report. Include the device model, Android or iOS version, app version, tool route, and the action that failed.
If the problem affects a private file, describe the file pattern rather than attaching the original document unless you are comfortable sharing it.
- Launch or splash-screen issues
- Broken upload, run, merge, or download flows
- Export naming or share-sheet problems
- Navigation or mobile layout bugs
- Privacy and local-processing questions
Known limits to mention when reporting issues
Some PDF operations depend on browser memory, device storage pressure, and document complexity. Large scanned files, unusual encryption, and damaged PDFs can still fail even when the app is working correctly in general.
Telling us the approximate page count, file size, and document type often helps more than saying only that a tool failed.
How DayFiles handles app support
Support is best-effort for the current release. The product is actively maintained, and actionable reports are the fastest path to a fix or documentation update.
Android and iOS Lifetime Premium and Premium monthly plans include the same ad-free access, Premium features, and premium developer support for app issues and feature requests. Use the premium-support action in the app so the request identifies the plan; platform purchase verification may be requested when needed.
Each Premium-labeled tool can be tried multiple times on a device before the purchase screen is required. Those on-device tries do not grant Premium benefits such as ads-off or priority support. Existing free PDF tools remain available without a purchase. The public website keeps Premium tools free.
For business or partnership questions, use the same support path and label the message clearly.