RoleVerge · 2026-09-29
Privacy policy
Who operates this service
RoleVerge / RolePaths is operated by Hezhong Tonghui Co., Limited, Hong Kong. Privacy contact: [email protected]. Effective 29 September 2026. This notice describes the current P0 product; material changes will be dated here before introducing new processing.
Assessments without an account
Skill answers and calculated scores stay in the memory of this browser page. We do not upload them or save them in local storage. Clear the answers or close the page to discard them. Browsing sends ordinary network information (such as IP address and request metadata) to the hosting infrastructure. Selected occupation, language and country reach our server to request reference data; they are not linked to a stored personal assessment.
Public Career Pulse
Voting is optional and separate from your private assessment. Only on submission, a random essential vote-integrity cookie is set for 24 hours (Secure on HTTPS, HttpOnly, SameSite Strict). We store fixed-choice answers, occupation, expiry and a role-scoped keyed digest of that random cookie. No name, email, account ID, IP address, free text, personal assessment or referrer ID is stored in the ballot table. Ballots are pseudonymous, not guaranteed anonymous. The cookie supports correcting or withdrawing a ballot in the same browser while available. Cross-career digests differ. Cookie deletion or expiry can permit repeat participation; counts are ballots, not verified people. Choices contribute to public distributions only at five ballots per occupation. Ballots are excluded after 30 days and purged at the next daily backup (within about 24 hours); encrypted backups may retain them for up to seven more days. Abuse controls temporarily process network information. We use requested-service necessity for vote integrity, where applicable, and your optional agreement for publication; no advertising use.
Optional product event counts
Optional first-party product event counting is off by default and is separate from Cloudflare Web Analytics below. If you opt in, we count fixed events (assessment completed, card downloaded, resource clicked) using a single-use token expiring after ten minutes. Aggregated event counts expire after 32 days. They do not include scores, answers, names, email addresses or a persistent visitor ID. Opting out stops future optional counts.
Cloudflare Web Analytics
Cloudflare may automatically load its Web Analytics beacon on public pages to measure page views, visits and loading performance, separately from the optional product-event checkbox. Cloudflare states that this service does not use analytics cookies, local storage or fingerprinting to identify individual visitors. Requests still reach Cloudflare infrastructure and include ordinary network information. We do not add private skill answers, assessment scores, usernames or account email addresses to analytics events. Visits are not a count of verified individuals. Cloudflare currently makes up to six months of Web Analytics history available. Contact [email protected] with questions or objections; browser privacy tools may also block this measurement. Provider information: https://developers.cloudflare.com/web-analytics/
Contributor accounts and evidence
Contributor accounts use a username, optional email, password hash, necessary session/authentication records and contribution history. Wiki sessions and security controls may process identifiers and IP-related information. Do not submit resumes, identity documents, employer secrets or personal information about others. Reviewed contributions may be published with attribution under the contribution license; private account email and authentication data are not published.
Why we process data
Data is used to deliver requested pages, maintain account access, review evidence, prevent abuse, respond to privacy requests and restore the service. Where GDPR applies, account and requested-service processing relies on contract necessity; proportionate security and evidence integrity on legitimate interests, subject to balancing and objection; optional first-party product event counting on consent. Cloudflare operational performance and aggregate traffic measurement serves site reliability and audience understanding; where legitimate interests is applicable, it remains subject to balancing, minimisation and objection. Cookie-free measurement is not a blanket exemption from local privacy requirements. Consent is not bundled with unrelated marketing. Applicable local law may require an additional basis or notice.
Cookies and logs
We use necessary MediaWiki authentication/session cookies for contributors. There are no advertising pixels or embedded social SDKs. Cloudflare can inject its Web Analytics script as described below. Product proxy and Apache access logs are disabled; transient rate limiting and error/security records can still contain network information. Hosting and mail suppliers may maintain their own operational records; this is not a zero-log or zero-personal-data service.
Providers and international processing
The application and database run on Tencent Cloud in Hong Kong. Encrypted daily backups are stored in Cloudflare R2 with an APAC location hint; APAC is not a Hong Kong-only residency guarantee. Encryption reduces exposure but does not make account data anonymous. Account emails, when requested, use Tencent Enterprise Mail; regional routing and supplier retention require contractual verification. Cloudflare provides domain/DNS and the enabled proxy/CDN, which processes network requests at its edges and may generate connection diagnostics under its own retention policies. Our operator may administer the service from outside Hong Kong.
Sharing and outside websites
Sharing is initiated by you. Card images are generated locally and may reveal the self-assessment information shown on the preview if you publish them. A participation QR/link contains only the occupation and language, never your score, answers or account ID. Social links contact the selected platform only when clicked; platform terms then apply. You can share a generic card without your score. We do not collect your social account credentials or publish automatically. Course partnerships are currently pending approval.
Retention and deletion
Browser answers last only for the page lifetime. Optional counters last up to 32 days; local and R2 backup copies follow a seven-day rolling retention policy. Contributor accounts persist while active; request closure by email. Evidence, license and version histories may be retained for attribution, integrity or legal claims, with personal details suppressed/redacted where appropriate. We review necessity at least yearly; those records do not currently have an automatic deletion deadline. Support correspondence has a target retention of 12 months after resolution, subject to dispute/legal obligations and manual review. Backup restoration must reapply completed privacy requests.
Your choices and rights
Contact [email protected] for access, correction, deletion, objection, restriction, portability where applicable, or consent withdrawal. Tell us the relevant username or record; do not send identity documents unless a proportionate verification process is agreed. We aim to reply within 30 days, without overriding applicable statutory deadlines, extensions or exceptions (Hong Kong access requests normally within 40 days; GDPR normally one month). You may complain to the Hong Kong PCPD or your competent regulator. Public contribution licenses already granted are not automatically revoked by account closure; unnecessary personal data can still be reviewed for removal.
Scope and limits
This preview is designed for adults and does not invite children to open contributor accounts. We do not sell personal data, process resumes, decide hiring, deliver training or issue certificates. Hong Kong hosting is not an exemption from other applicable privacy laws. Before expanding region-specific account services, we must assess notices, processors, representation and lawful international-transfer mechanisms.
Public account registration
A contributor account uses a public pseudonymous username, a securely hashed password and an optional recovery email. Native account/session and anti-abuse mechanisms may process a client IP address and security logs; this is separate from optional product event counts. Account creation is rate-limited. Do not use a sensitive personal identifier as your username. Account data is processed in our existing Hong Kong hosting and backup environment. Contact support for account deletion or recovery; do not send your password.