Privacy Policy

Account-free does not mean anonymous

Cognify links assessment records and permitted visit information through a first-party browser credential. We do not request a name, phone number, birth date, gender, workplace, or identity document in the assessment journey. Nevertheless, answers, results, submission IP, and permitted technical metadata are stored, and an email address is stored if you request a copy. These linked records are not described as fully anonymous.

The operator identity, privacy contact, hosting details, provider information, effective date, and processing details shown with this policy apply to the deployed service. Contact the operator through those details for questions or privacy requests.

Assessment and access records

Starting an attempt records its assessment version, administration language, times, and presented policy versions. A random browser credential and its server-side hash support owned access, saved-answer resume, and result retrieval. Current answers are saved in the database; accepted edits overwrite the previous answer for that item and attempt. We do not retain earlier answer values in an answer history, analytics, receipts, or logs.

Submission stores final answers, scores, complete English and Indonesian result snapshots, versions, completion time, and the initial submission-IP record. Unfinished attempts and their current answers are retained too. These records provide the test, preserve the result, and support access and duplicate-request handling. No combined identity or ability score is derived from device data.

Submission IP and local enrichment

When a result is first created, Cognify records the client IP from the request’s forwarded headers or connection. It is operational metadata for local enrichment only, may be inaccurate, and is not captured on every visit; duplicate submission requests keep the first result’s IP. If no parseable address is available, the record contains a status instead of a guessed address.

For eligible public addresses, local DB-IP City Lite and ASN Lite data may supply approximate country, region, city, coordinates, and network ASN or organization, with dataset and coverage information. These are approximate network observations, not verified identity or precise physical location. No participant IP is sent to DB-IP for lookup. The initial service does not add VPN/Tor reputation, WHOIS, contact, or reverse-DNS enrichment. IP information remains separate from the report and never changes scores.

Optional visit and device information

When enabled under the displayed collection policy, Cognify records supported browser/operating-system information, language, time zone, screen and viewport size, motion preferences, device capabilities, connection observations, sanitized referral/campaign information, navigation performance, visibility, and semantic activity such as page or question exposure. Availability varies; missing values remain unknown.

These records support internal understanding of visits, usability, performance, and service operation. Activity time is an estimate, and unacknowledged events may be lost when a tab closes. They do not affect scoring or establish honesty. We do not collect GPS, camera or microphone recordings, contacts, session replay, detailed mouse paths, keystroke contents, typed email, or answer values through optional analytics. Device traits are not used to reconstruct lost browser ownership.

Collection settings and choices

The notice shown on the site identifies whether optional analytics require your choice or operate under the deployment’s notice-only policy. In opt-in mode, pending, declined, or withdrawn permission stops new optional collection; you can use tests without allowing it. Notice-only mode does not label a notice display or dismissal as consent. Without an active configured policy, optional collection is disabled.

Changing a choice records what you actually chose and its policy version. Withdrawal stops new optional collection and clears uncommitted browser batches; it does not erase records already stored. The ownership cookie, saved assessment records, and submission-IP storage are described separately and are not disabled by declining optional analytics.

Optional result email and Google

An address stays in the form until you press send; we do not autosave it as you type. When you request a result copy, Cognify stores the submitted recipient in encrypted form, a digest for request limits, and delivery records including status and times. This applies to successful, failed, and cancelled requests. The address is not verified and is not used to create an account or marketing subscription.

Google processes the recipient and complete report for SMTP delivery. The recipient’s email service also processes the received message. These providers’ processing, locations, retention, and any sender-mailbox copies follow the actual service configuration and their policies, as described in the accompanying provider details. Cognify’s permanent-database policy does not assert identical provider retention. We do not add open/click tracking or read mailboxes to send results. Raw answers, IP, analytics, and browser credentials are excluded from the emailed report.

Copies you choose to share

Sharing stores a fixed-language copy of selected report sections and a protected link record. Anyone with the active link may read that copy; the initial access lasts seven days or until revoked. Raw answers, email, IP, analytics, and owner credentials are excluded. Revoking or expiring a link blocks future link access but retains the stored share record and cannot remove copies already kept by recipients.

Permanent records and overwritten answers

Cognify has no routine retention deadline or automatic age-based deletion for stored browser/session records, unfinished attempts, current/final answers, results, email recipients and deliveries, submission-IP/enrichment records, permitted visits and activity, collection choices, shares, or operational receipts. They are retained permanently in Cognify’s database. An accepted edit to an unfinished answer is the exception to historical preservation: only its latest value remains.

Cookie and share expiry limit access; delivery deadlines limit sending; IP cache freshness limits reuse. None is a database deletion timer. Ending browser access does not delete records or cancel an already requested email. Applicable privacy requests or exceptional legal obligations are handled separately through the operator contact; this policy does not remove applicable rights.

Access, processing, and protection

Assessment records are processed on the operator’s hosted service and database. Operational access is restricted to authorized service operation; the public result, share, and email surfaces do not expose IP or analytics metadata. Stored email recipients are encrypted, and website ownership uses random credentials rather than email or IP matching. No system can promise absolute security.

The accompanying service details identify the actual hosting/provider locations, processing purposes and bases, and any cross-border processing arrangements. These details must reflect the deployed configuration rather than assuming all processing remains in one country. No third-party advertising or analytics tracker is part of this initial service.

Questions, requests, and policy versions

Use the displayed privacy contact to ask about applicable access, correction, withdrawal, deletion, or other privacy rights and requests. The operator may need proportionate information to assess a request without revealing another person’s records. The ordinary website does not recover lost ownership by matching an email address or IP.

The site records the notice versions actually presented and any actual collection choice. Reading, dismissing, or starting a test is not recorded as proof of agreement or verified age. Updated policies identify their effective date; existing completed reports retain their original notices and versions.

Service details

Operator

Fauzan

Contact email

fauzancodes@gmail.com

Contact address

Jakarta, Indonesia. Privacy and service contact: fauzancodes@gmail.com

Operating jurisdictions

Indonesia

Website

https://cognify.fauzancodes.id

Hosting location

Operator-managed VPS (Coolify). Application processes and PostgreSQL run on that host.

Hosting provider

Coolify on the operator VPS; optional result email via Google SMTP (Gmail)

Email service

Google SMTP (Gmail) on smtp.gmail.com with STARTTLS

Provider processing and transfers

Optional result copies are submitted to Google SMTP. Submission IPs are enriched locally from bundled DB-IP Lite files. No participant IP is sent to DB-IP. Google may process submitted email content according to Google’s terms.

Provider retention

Application records including current answers, results, optional encrypted email, and IP metadata are stored in the operator PostgreSQL database without a product TTL.

Collection mode

Optional analytics only with permission

Collection policy version

collection-opt-in-v1

Processing purposes and bases

Answers, results, the cognify_browser cookie, optional emailed report copies, and submit-time IP metadata are processed to provide the requested self-exploration service. Optional visitor telemetry (supported browser/context snapshots and semantic activity described in the Privacy Policy) is collected only after an explicit allow choice under collection policy collection-opt-in-v1. Declining or withdrawing stops new optional collection; records already stored remain. No advertising or third-party analytics trackers are used.

Effective date

2026-09-12