Google Play Publication Center
A single source of truth for the public URLs, listing copy and declarations used to publish Doc Scanner 2027.
Play policies and SDK behavior can change. Verify this page against the final signed AAB and Play Console policy status immediately before every submission.
Permanent public URLs
https://ptrs.ltd/apps/doc_scanner_2027/Privacy Policyhttps://ptrs.ltd/apps/doc_scanner_2027/privacy/Data Safety disclosurehttps://ptrs.ltd/apps/doc_scanner_2027/data-safety/Data deletionhttps://ptrs.ltd/apps/doc_scanner_2027/data-deletion/Supporthttps://ptrs.ltd/apps/doc_scanner_2027/support/Termshttps://ptrs.ltd/apps/doc_scanner_2027/terms/Default store listing — English
Doc Scanner 2027
Download textScan multi-page documents, recognize text, sign PDFs and share smaller files.
Download textProfessional multi-page scanning, page editing, local OCR, searchable PDFs, HTML text export, multiple signatures and PDF optimization.
Download textInitial production release.
Download textGraphic assets
Store screenshots: upload at least two screenshots captured from the final release build. Four portrait screenshots at 1080 × 1920 or higher are recommended. Marketing mockups from this website must not be submitted as actual app screenshots.
Play Console declarations baseline
| Category | Tools / Utilities |
|---|---|
| App access | All core features are available without a Doc Scanner account. Optional AI OCR requires the user’s own API key. |
| Ads | No |
| Account creation | No |
| Target audience | General productivity audience; not specifically directed to children. Final age selection remains a publisher decision. |
| Financial features | No financial product or financial-management functionality. Re-evaluate the voluntary support flow separately under Payments policy. |
| Government / news / health | No |
| Content rating | Complete the IARC questionnaire in Play Console using the final feature set. |
| Contact | ceo@ptrs.ltd |
Submission blockers still requiring publisher action
- Capture truthful phone screenshots from the final release build.
- Confirm the permanent package ID and configure Play App Signing/upload key.
- Complete identity verification and any required closed test.
- Complete Data Safety from the final AAB and current SDK disclosures.
- Complete content rating, target audience, app access, ads and financial-feature declarations.
- Resolve the Stripe support-payment policy path before enabling it in a Play build.
- Run pre-launch reports and real-device Android 16 / 16 KB page-size testing.
Payments policy warning
Google Play’s standard Payments policy permits external donation collection only for validated tax-exempt organizations using a secure payment system. A voluntary Stripe contribution to an ordinary developer can be rejected even when it unlocks nothing. Keep Stripe unconfigured in the Play build unless Peter’s Engineering qualifies for that exception or is enrolled in an applicable regional alternative-billing/external-links program and implements every program requirement.