TRANSPARENCY & TRUST

Privacy Policy

A readable draft explaining this frontend prototype and the privacy topics a future live service would need to address.

PLACEHOLDER · REVIEW BEFORE LAUNCH

Draft design copy, not legal advice or a finalized contract. A qualified reviewer must verify jurisdiction, operator details, user rights, provider terms, and operational practices before any live service.

Draft prepared for the Phase 1 prototype · 21 October 2026 · No live service

1. Scope and operator identity

This draft applies to the AKRAMORA Phase 1 frontend. It is not a live rewards platform. The legal operator, registered business details, privacy contact, and applicable jurisdictions are not yet published and must be confirmed before launch.

2. Information in this prototype

The app has no account backend, database, authentication service, or form-submission API. Names, email-format values, task responses, and preferences entered in demo forms remain in browser memory during the current session. Do not enter real credentials, identity documents, payment information, or sensitive personal data.

3. Device storage and browser actions

The light or dark theme preference may be stored in localStorage on this device. Other demo workspace edits remain in memory and reset on reload. The referral copy action writes a fictional code to your clipboard. A selected submission file is not read, uploaded, or sent; only its local file name and size may be displayed.

4. Hosting and platform services

The hosting platform and browser may independently process connection information or operational logs under their own terms. This frontend does not establish or control those practices. The live operator must audit hosting, analytics, security, and service-provider processing before publishing a finalized privacy statement.

5. Future purposes and lawful grounds

A future service would need to define information used for account administration, task verification, participant support, fraud prevention, and eligible rewards. It must identify valid legal grounds, minimize collection, explain optional versus required data, and avoid using prototype copy as a substitute for a processing assessment.

6. Sharing and international transfers

This app sends no form data to third-party providers. Future sharing with payment, verification, or support providers must be documented, limited, secured, and supported by applicable transfer safeguards. EasyPaisa and JazzCash are design labels only, not active data recipients or claimed partners.

7. Retention and deletion

Current in-memory form and workspace state is lost when the page reloads. The saved theme can be removed by clearing this site’s browser storage. Future retention periods, deletion procedures, legal exceptions, and backup handling must be specified before real personal information is collected.

8. Your choices and rights

You can explore this prototype without creating an account and can avoid providing any personal data. Depending on a future service’s jurisdiction, rights may include access, correction, deletion, objection, restriction, portability, withdrawal of consent, and complaint to a regulator. The operator must publish a working rights-request channel before launch.

9. Children and eligibility

This prototype does not collect ages or verify identities. The design intent for future live participation is adults aged 18 or above, subject to verified local rules. A live operator must adopt appropriate eligibility controls and rules for handling information inadvertently provided by minors.

10. Security and changes

No prototype is a promise of production security. Before launch, authentication, access controls, transport security, incident response, and independent review must be implemented and assessed. Material changes to a final policy should be clearly communicated with a revised effective date.

⚡Make an app like this, free