WildcatIQ · privacy
Privacy, plainly stated.
This page describes information the current sign-in and correction flows handle, and what is not yet collected.
Teable sign-in
Depending on the provider configured for this app, sign-in may use email verification or an account provider such as Google or Teable. The selected provider receives the information required to complete authentication. WildcatIQ uses the verified app-member record and email server-side to check existing membership and access. Sign-in does not itself create an Active membership.
Correction form
The signed-in correction form asks for a research record or page, a description of the claimed issue, the requested change, and an optional HTTPS evidence URL. It does not ask for your name, email, phone, or other contact details. The submitted claim, requested change, page reference, optional evidence, status, source, year, and retrieval time are stored in WIQ_Corrections for owner review. A separate private write-audit log stores the authenticated app-member record identifier and event time for arbitration; it is not shown publicly. Do not include private investor information or unrelated personal data.
Membership request
The membership request page currently collects no information and does not submit a request. WIQ_Contacts lacks fields for the requested name, email, role, and geographic interest; the submission form remains unavailable until a suitable storage schema is authorized. Visiting the page alone does not create an account or membership.
Retention
A fixed retention period has not been supplied. Authentication records and submitted correction records remain in the associated Teable resources until handled under the owner’s retention and deletion procedures. WildcatIQ does not claim a specific deletion schedule.
Questions
A monitored contact email has not been supplied. The public Contact page states this limitation. Source links lead directly to their publishers.