Privacy Policy

This policy applies to PraxiHub’s public website, forms, administrator authentication, editorial operations, and supporting technical infrastructure.

Public Newsletter subscription is disabled. Existing records may include an email address, optional first name, consent timestamp, source, subscription status, and operational timestamps. They remain preserved for withdrawal, compliance, and historical operational purposes. A subscriber may withdraw by emailing the privacy contact below.

Contact records may include name, email address, selected subject, message, status, internal handling notes, and timestamps. They are used to review and respond to inquiries, correction requests, privacy requests, content-removal requests, and platform issues.

Public Research Submission intake is disabled. Existing records may include corresponding-author name and email, optional affiliation and ORCID, manuscript title, abstract and public URL, selected Topics, optional co-author text, funding and conflict disclosures, confirmations, review status, internal notes, and timestamps. They remain preserved for editorial history, communication, provenance, and compliance.

Administrator operations use Supabase authentication. Required authentication and session data may be processed to sign in, refresh a session, reset a password, sign out, and prevent unauthorized access. Security and audit records may include administrator identity, action, time, target record, outcome, and minimized operational metadata. Passwords and session tokens are not stored in PraxiHub content records.

Readers may create an account to maintain a private Research Library, follow Topics, and manage Research Alert preferences. Account records use Supabase authentication and may include an email address, authentication and session data, full name, country or region code, current professional role, primary research interest, and optional organization or university, LinkedIn profile URL, and ORCID iD. Passwords are handled by the authentication provider and are not stored in PraxiHub content records.

Saved publication identifiers, Topic follows, per-Topic notification choices, and global Research Alert preferences are private and protected by owner-only access controls. They are not published, used for follower counts, or added to Search, RSS, sitemap, analytics, or public metadata. Alert matching uses only explicit Topic follows and does not infer interests from browsing, clicks, search history, IP address, or reading time.

The public Research Community application flow is disabled. Existing records include the account identifier, research interests, motivation, preferred contact method and contact value, submission and review timestamps, and a review status. They remain private and preserved for authorized historical and operational review. A CV was not uploaded to or stored by the application workflow.

Pending, under-review, verified, and not-approved statuses are private. Verification records an application review outcome only and does not create authorship, contributor, publication, editorial, administrator, employment, or professional rights.

PraxiHub records a limited set of first-party events to understand site traffic and Research readership. Events may include the event type, time, a restricted canonical path, random first-party visitor and session identifiers, and a canonical Research or Topic identifier where relevant. A session ends after thirty minutes of inactivity. Historical Research-access and Community-funnel events remain preserved but are not active public funnels. When an existing user is authenticated, the server discards the anonymous visitor identifier and may associate an internal account identifier with an event without joining earlier anonymous activity to the account.

The random visitor and session identifiers are stored in the browser's local storage, not an analytics cookie. Clearing site storage resets anonymous uniqueness. These records do not contain exact IP addresses, browser user-agent strings, referrers, fingerprints, device identifiers, precise geolocation, query strings, profile-field copies, passwords, authentication tokens, Research bodies, CVs, private application text, or administrator notes. PraxiHub does not use third-party advertising pixels, session replay, or cross-site tracking for this workflow.

Product analytics are available only to authorized administrators, are kept separate from security and editorial audit records, and are reported in aggregate. Groups containing fewer than three authenticated users are not shown individually. The initial retention period is thirteen months, after which events are deleted unless a shorter period is adopted or limited preservation is required for a documented operational or legal reason.

User information may be processed through service providers required to operate PraxiHub, including hosting, database, authentication, security, delivery, and email infrastructure. Those providers may process ordinary request and security data such as IP address, request time, requested path, browser or device information, and error signals under their own terms and configurations.

Information is used to operate the requested workflow, protect the service, maintain editorial and audit records, respond to requests, investigate failures or abuse, and comply with applicable obligations. PraxiHub does not store honeypot values in operational form records.

Records are retained for as long as reasonably necessary for the relevant account, saved Library, Topic follow, alert preference, correspondence, editorial, security, archival, or compliance purpose. Removing a saved item or unfollowing a Topic removes that private relationship. Deleting an authentication account, when handled through an approved privacy request, cascades deletion of the associated private profile, Library, Topic follows, alert preferences, and minimal delivery-deduplication state unless limited retention is required for security or applicable obligations. Retention may also depend on infrastructure-provider settings, backup cycles, dispute preservation, and applicable requirements.

Users may update their profile and Research Alert preferences in Account, opt out of Research email without deleting the account, or request access to, correction of, or deletion of their submitted personal information by emailing praxifi.official@gmail.com. Historical Newsletter withdrawal requests may use the same address. PraxiHub may request reasonable verification and may retain limited information where required for security, legal compliance, dispute handling, or publication integrity.

PraxiHub uses access controls, server-side authorization, validation, restricted client boundaries, encrypted provider connections, and minimized audit records. No system can guarantee absolute security.

PraxiHub is a general research and educational service and is not designed to solicit personal information from children. A parent or guardian may contact PraxiHub about information they believe was submitted by a child.

This policy may be updated as platform functionality, infrastructure, or applicable requirements change. Material changes will be published on this page.

Privacy, access, correction, deletion, and Newsletter withdrawal requests may be sent to praxifi.official@gmail.com.