Different data has different permissions.
Public browsing stays open
You do not need a TIGEE membership to browse public Discover profiles, Culture, TPS methodology, Awards, or other public pages. Membership is a separate, curated participation layer.
First-party audience analytics
TIGEE can ask permission to use first-party audience analytics. If you choose “Allow audience analytics,” the site may set a TIGEE first-party browser identifier and record structured events such as page views, profile opens, scroll depth, Discover filters, search activity, Culture article opens/completion, selected outbound-link clicks, and membership intent. TIGEE’s current audience-events system does not intentionally store raw IP addresses or raw browser user-agent strings in the research event table.
No TIGEE audience-analytics identifier is created by the audience-intelligence layer and audience events are not recorded by that layer.
A first-party anonymous browser identifier and session identifier may be used to understand return behavior and navigation patterns.
Analytics permission can be changed through the browser’s local site data or, for members, through membership preferences as TIGEE expands the settings interface.
Membership data
Audience membership applications may store account identity information, the display name chosen for membership, a broad self-selected relationship to aesthetics, an optional broad geographic region, declared TIGEE interests, the applicant’s membership statement, application status, member tier, and internal review notes. TIGEE uses these fields to curate participation and understand its audience without requiring invasive personal profiling.
Analytics consent is not research consent
TIGEE separates ordinary audience analytics from permission to use eligible member data in aggregated research. A member can allow audience analytics without agreeing to aggregated research. A separate research-contact choice controls whether TIGEE may invite that member to future studies. Consent choices are versioned so TIGEE can preserve which permission language applied when a decision was recorded.
TIGEE Research Registry
The site includes a dedicated Research Registry foundation for named studies, study versions, variable definitions, enrollments, consent state, and versioned responses. The goal is to prevent future aesthetic reports from being reverse-engineered out of ordinary traffic logs. A research dataset should be tied to a defined study, variables, eligibility rules, and the applicable consent version.
Published reports should generally use aggregated or de-identified results. TIGEE should not publish an individual member’s browsing history as a research finding.
Sensitive information boundaries
TIGEE should not infer or build audience profiles around sensitive attributes such as religion, political affiliation, sexual orientation, medical conditions, or precise location from ordinary browsing behavior. Optional research that genuinely requires sensitive information should use a separate study-specific consent process and additional legal/ethical review before collection.
Private model evidence
Photos uploaded through the Participant Portal are stored as private TIGEE evidence. Participant evidence is not exposed through TIGEE’s public media endpoint unless a separate publication action explicitly approves an image for public use. TIGEE’s current research workflow favors deliberate manual upload, participant upload, TIGEE Capture, and other rights-cleared sources rather than automated Instagram photo scraping.
What TIGEE may store for models
The current portal may store account identity information, profile information, optional outbound social/profile links, self-reported or verified measurements when supplied, permissions, uploaded evidence images, evidence review notes, TPS analyses, participant application/identity-clearance state, and related audit records.
TPS analysis and AI-assisted drafts
TIGEE may use selected evidence to create an AI-assisted TPS draft for internal review. AI-generated drafts are not automatically official or public. TIGEE OS calculates the locked TPS arithmetic and an administrator must review the analysis before it can become an Official TPS record.
Public use is separate
A private profile photo or evidence upload is not automatically a public profile image. Public Research Evaluations and TIGEE Verified profiles use separate publication controls. A Research Evaluation does not by itself imply that the subject participated in, approved, or endorsed TIGEE. Identity clearance also does not automatically mean TIGEE has admitted the claimant as a participating model.
Physique Stream tags
TIGEE may editorially tag a documented public/professional identity in a Physique Stream post using an existing TIGEE model record. A tag can appear before that person has claimed or controls a TIGEE profile. An unclaimed tag is an editorial identity reference only; it does not imply participation, endorsement, identity verification, model approval, or permission to control the page. Profile control still requires the separate claim and identity-clearance workflow.
Deleting photos and accounts
The current portal allows participants to permanently delete uploaded photos. Admins can also delete evidence. Deleting an image removes its stored image object and associated evidence record. If an affected image supported a public analysis, TIGEE returns that analysis to review and removes the affected public publication until it is checked again.
When an Identity account is deleted, TIGEE attempts to remove or detach linked membership, consent, participant, and research records according to the current database relationships while preserving institutional model records where appropriate. TIGEE should continue formalizing a written retention schedule as the platform scales.
Measurements
TIGEE does not infer physical inches or centimeters from ordinary photographs. Participants should identify measurements accurately as verified or self-reported. Confidence A requires standardized evidence and verified current measurements where the methodology requires them.
Access and account security
Participant and administrator areas are protected by authenticated roles. Audience community actions can require approved membership. Password recovery is handled through Netlify Identity. Provider/API credentials remain server-side in Netlify environment variables and are not placed in public browser code.
Contact, corrections, and data requests
For privacy questions, correction requests, publication-permission changes, removal requests, membership-data questions, or other data-related inquiries, contact research@tigeeaesthetics.com. Include the relevant profile or page URL when possible. Do not email government identification or sensitive identity documents; TIGEE will provide separate secure instructions if identity verification is required.
Before broad public launch
TIGEE should continue formalizing its retention schedule, final legal privacy policy, cookie/consent controls, terms of use, study-governance procedures, and jurisdiction-appropriate data request procedures as the platform scales.