Privacy policy

This policy explains how personal information may be used when you visit the website, register an interest or use an account service. The final legal controller details should be checked against the account documents.

Who is responsible

The legal entity responsible for a particular processing activity must be identified in the final service agreement and privacy notice. OptiGain AI is the trading name used on this website.

A privacy notice should name the controller and give a postal contact point, not only a trading name. Different entities may be responsible for the public website, account verification and payment processing. Where those roles differ, each should explain its own purposes and obligations.

Before supplying identity documents, check the name of the account provider and its privacy notice. If you ask us to correct or delete information, we may need to pass the request to the entity that controls the relevant account record.

Information you provide

Registration may involve your name, contact details and information you choose to share with support. Account onboarding can require identity and payment information through the relevant provider’s secure process.

The contact form may collect a name, email address and telephone number so that a team member can respond. Further information can be created when you describe a support issue or make a complaint. Do not include a password, one-time code or more identity information than is needed for the question.

If you later open an account with a provider, its onboarding process may collect date of birth, address, identity evidence, payment details and suitability information. Its own documents should describe those categories precisely.

Information collected automatically

Basic technical data such as device type, browser, request time and IP address may be processed to deliver the site, protect it and diagnose errors. Optional analytics remains disabled unless configured.

Server logs can contain a request address, timestamp, browser details and a partial or full IP address. Those records help deliver pages, detect misuse and investigate faults. They should not be used to make an unannounced personal investment profile.

The market ticker and calculator may use technical information to display relevant currency or regional content. Their operation does not change the need for a clear explanation of any data used by the account provider.

Why information is used

Contact details are used to respond to an enquiry and explain the account process. Other processing may be needed for service delivery, security, legal compliance or a legitimate operational purpose.

We use a submitted enquiry to answer the requested question, explain the registration process and maintain a record of the exchange. Security records can help detect unauthorised activity and investigate incidents. Legal duties may require the provider to keep evidence of an account relationship.

A new use that is unrelated to the original purpose should be explained before it begins, and consent should be requested where that is the appropriate legal basis. A person should be able to understand which communication is necessary for service and which is optional marketing.

Legal basis

Depending on the activity, processing may rely on your request before a contract, performance of an agreement, a legal obligation, consent or a legitimate interest. The final provider notice should map each purpose to its basis.

Pre-contract steps can justify processing needed to respond to a request for an account. A contract may justify processing needed to deliver an active service, while a law may require identity and transaction records. Legitimate interests can cover limited security and operational activities after balancing the effect on individuals.

Consent, where used, should be specific and capable of withdrawal. Withdrawing marketing consent should not prevent necessary account messages, although it may affect an optional feature that depends entirely on consent.

Calls and messages

Support correspondence may be retained to answer your question and resolve disputes. Marketing contact should follow the preference and consent rules applicable to the channel used.

A call about registration should identify the caller and purpose. Where calls are recorded, the responsible organisation should explain that, the reason for recording and the retention period. Email records can be important when resolving a complaint about what was said.

You can ask for written confirmation of a material term discussed by phone. Never rely on a caller's statement alone to verify a payment address or regulatory claim; compare it with the provider documents.

Identity checks

Where an account requires verification, documents should be supplied through the confirmed secure channel. The provider responsible for the check should explain retention, verification partners and any automated matching.

Verification information may include document images, extracted fields and the result of a comparison with trusted records. It should be handled through a secure provider flow rather than an ordinary marketing form. A failed match can be caused by an error and should have a route for review.

The provider should explain whether an automated decision has a significant effect, what human review is available and how long evidence is retained. Avoid sending copies of documents through social media or an unverified mailbox.

Sharing with providers

Hosting, communications, payment and verification providers may process data to provide their services. Data should be shared only to the extent needed and under appropriate contractual safeguards.

A hosting company may process technical logs, while a communications service may deliver emails or calls. Identity-check and payment providers can need specific personal details to perform their tasks. Each should receive only information relevant to its role and be subject to appropriate safeguards.

We do not infer that an exchange logo on the homepage is a data-sharing partner. Any actual recipient or category should be named in the final provider notice, and a customer can ask which entity receives their data.

International transfers

If information is transferred outside the UK, the responsible entity should use an applicable legal transfer mechanism and explain the destination and safeguard in its final notice.

Some technology suppliers store or access information in other countries. A transfer should be assessed against UK data protection requirements and supported by a valid mechanism where required. A contractual safeguard does not by itself explain every practical security risk.

The responsible controller should be able to say which categories of data leave the UK, why and what protection applies. Ask for those details if they are important to your decision to use the service.

Retention

Information should be kept no longer than necessary for its purpose, subject to legal and dispute-related retention duties. The precise periods depend on the data category and provider obligations.

A short website enquiry does not necessarily need to be kept as long as a regulated account record. Retention periods should reflect the purpose, legal obligations, dispute windows and security needs of each data category. Records should be deleted or anonymised once there is no reason to keep them.

An account provider may have to retain identity and transaction records after closure. If you request deletion, it should explain which data can be erased and which must remain under a specific obligation.

Security

Access controls, transport protection and restricted staff access help reduce unauthorised disclosure. No online service can claim absolute security, so report a suspected breach promptly.

Practical controls include role-based access, protected transmission, monitoring, tested backups and a process for revoking staff access. A supplier should also be reviewed before it receives personal data. These measures reduce risk but cannot make any online system invulnerable.

You can help protect your information by using a unique password and checking the complete domain before signing in. Report a suspicious message or exposed document promptly so the responsible team can investigate.

Your rights

UK data protection law may give you rights of access, correction, erasure, restriction, objection and portability, subject to conditions. Contact support to start a request and verify the responsible controller.

You can ask whether a controller holds information about you and request a copy subject to legal exceptions. Inaccurate information may be corrected, and some processing may be restricted or objected to. Portability applies only in defined circumstances.

To make a request, provide enough information to identify the relevant record without sending unnecessary documents in the first message. The controller may verify identity before disclosing account information to protect it from another person.

Cookies and local storage

Essential storage may support site operation and security. Optional analytics or advertising tools should be disclosed and controlled before they are activated.

Some browser storage is needed to maintain a session, remember a security preference or prevent abuse. Optional measurement tools should be distinguished from those functions and described before they are enabled. A cookie list should identify purpose and lifespan.

You can manage browser settings, but blocking essential storage may prevent parts of an account from functioning. The site leaves its analytics identifier empty by default, so no GA request is sent until an authorised operator configures it.

Children

The service is intended for adults who can enter a financial agreement. If information relating to a child has been submitted, contact support so it can be reviewed.

A financial account is not designed for a child. If a child submits contact details through the website, the team should avoid using that information for marketing and investigate how to remove it in line with applicable duties.

Parents or guardians can raise a concern through the published support address. We may need enough information to locate the record, but should not request excessive details about the child.

Contact and changes

Send privacy questions to [email protected]. Material changes to the policy should be dated and published before they take effect where required.

A revised notice should show an effective date and explain material changes in a way a reader can find. A new account provider, different data recipient or substantially different purpose may require a direct communication rather than a silent website update.

Send questions and rights requests to [email protected]. If the issue concerns a separate account provider, the team should identify the correct controller and route your request accordingly.