Which data this page explains
FermatMind assessment experiences may involve several kinds of data: users' answers, results generated from those answers, service data for support with retrieval or unlocking, and aggregate statistics used to observe public page performance.
These data have different uses and risks. This page helps users understand what belongs to private results, what is needed to operate the product, and what is merely aggregate observation of visits.
Answer data and result data
Answer data consists of users' choices in questions. Result data consists of the summaries, dimensional interpretations or report content generated from those answers. These data are personal because they may reflect users' self-descriptions of personality, interests, behavioral tendencies or career preferences.
Private results should not become public page materials, enter search engines, or appear in sitemaps, llms, internal links in public articles, social media links or statistics pages. Any result link with a user-specific identifier should not be used as public content.
Support and retrieval data
For result retrieval, unlocking failures, refunds or account problems, the system may need the minimum information necessary to locate a request. A safer approach prioritizes email and masked identifiers, rather than asking users to submit complete order numbers, payment numbers, result links or private links in screenshots on public pages.
When additional information is needed, prefer the last few digits, masked order codes or a secure identification method specified by the system. Official Help pages and support rules govern the specific fields and processing timelines. Consult the published help pages for current support requirements.
Aggregate statistics differ from individual results
Public pages may use aggregate statistics to observe product experiences, such as how often a public page is visited, whether a public test entry point is clicked, or whether a process is abnormal. These statistics improve the product and should not be understood as public individual assessment results.
Aggregate statistics should not record private result pages, order pages, payment pages, history pages or user-specific links. If such paths appear in analytics tools, address the privacy issue before continuing growth analysis.
Data retention, deletion and account handling
Whether users can request deletion, which data can be deleted, processing times and whether results remain retrievable must be confirmed by the formal Privacy Policy and support process. Consult published privacy and support explanations for specific timelines. This page does not promise immediate deletion or that no data will ever be retained.
Deletion requests should use secure channels for identity verification. Public comments, social media direct messages and insecure forms should not be the main channels for handling private results or orders.
Boundaries of this page
This page explains basic assessment data boundaries and does not replace the formal Privacy Policy or Terms. Retention, deletion scope and processing methods are governed by formal policies and confirmed support processes. There is no uniform commitment for timelines or scopes not listed here.
Frequently asked questions
Will search engines see my assessment results?
They should not. Private results and user-specific links should not enter sitemaps, llms, search submissions or public internal links.
Does support need my complete order number?
Public pages should not request complete order numbers. A more appropriate approach prioritizes email and uses masked identifiers or secure methods specified by the system.
Will analytics tools see my results?
Analytics tools should not record private result or order pages. At most, they should observe public pages and aggregate behavior.
Can I delete assessment data?
You may submit a request. Formal privacy and support processes govern the specific scope, identity verification and processing time. There is no uniform commitment for unlisted scopes or timelines.
Can results be retrieved after deletion?
This depends on the scope of deletion and how the system handles it. Current public explanations do not provide a uniform conclusion; formal support rules should confirm it.
