Information collected
The final policy should list the personal and technical information the service collects, including information provided directly by users.
Privacy
Privacy Policy
This is a prototype disclosure, not a complete legal policy. The application currently stores account names and email addresses, password hashes, manually entered portfolio/watchlist/journal/alert records, support request details, and administrator-published content in a local JSON file outside the web root. Stored fields other than passwords are not encrypted at rest.
Use and retention
The final policy should explain why information is used, how long it is kept, and the legal basis for processing where applicable.
Your privacy choices
The final policy should explain applicable access, correction, deletion, and other privacy rights. Questions: support@forexwallet.com.
Draft policy topics for review
The current data handling is described above. These additional sections identify what a complete production policy still needs to explain; they are not claims about integrations that are not currently in place.
Current prototype storage
Data is kept on the server in a JSON file. Passwords are stored as PHP password hashes; names, email addresses, support messages, and user-entered records are stored as ordinary JSON values. No wallet, broker, market-data, or analytics provider is connected by this prototype.
Information and purpose
A complete policy should name each category of personal information collected, explain whether it comes from users, devices, or service providers, and state the specific purpose and applicable legal basis for each use.
Cookies and third parties
Document any cookies, analytics, hosting, payment, identity, or market-data providers, including what information they receive and how users can manage optional tracking.
Sharing and international transfers
Explain when information may be disclosed, which service providers receive it, how cross-border transfers are handled, and what safeguards apply.
Retention and security
State how long each information category is retained, how deletion requests work, and the real technical and organizational safeguards used. Avoid promising absolute security.
Individual rights
Set out the privacy rights that apply in each operating region, how to make a request, how identity is verified, and how to raise a complaint with a regulator.
Updates and contact
Include the responsible legal entity, effective date, change-notification process, and a monitored privacy contact. The displayed support address should be confirmed before publication.
Publication note: Have the final policy checked against the site's actual code, vendors, data flows, and applicable law before collecting personal information.