Trust · Institutional directory
Trust MIRENA only to the extent that the evidence and controls support it.
The Trust Center explains security reporting, privacy boundaries, GDPR rights, retention, cookies, accessibility, AI-output review, and the external platforms involved in delivering or supporting MIRENA.
Verified facts and boundaries.
These fields identify the entity, product, document, or operational boundary without turning related parties into the same entity.
The Trust Center separates company controls from platform controls.
Semantec SEO controls its website, product description, access relationship, support records, policies, and the information it receives directly. OpenAI controls the ChatGPT platform, account, model, conversation, memory, training, and platform-security rules under its own terms.
Stripe and Authflow.ai support parts of the current payment and access flow. Their specific roles, data categories, retention, and transfer arrangements belong in the provider register and privacy documentation.
Trust is based on disclosed boundaries.
- Security claims are limited to controls and provider statements that can be evidenced
- Privacy statements distinguish Semantec SEO records from ChatGPT and provider records
- Retention is tied to purpose, legal obligation, account state, and dispute needs
- Cookie rules distinguish essential storage from optional technologies
- Accessibility is a continuing practice rather than an unsupported certification
- AI output remains subject to human review and specialist approval
No blanket assurance or certification claim.
The Trust Center does not claim ISO 27001 certification, SOC 2 attestation, PCI DSS certification by Semantec SEO, independent penetration testing, a formal bug bounty, guaranteed uptime, or zero security risk unless a current evidence record is published.
Provider compliance or security claims belong to the provider and do not automatically become Semantec SEO certifications.
Report the issue through the correct route.
Security and responsible-disclosure reports use privacy@semantecseo.com unless a dedicated security address is later published. Product and access issues use support@semantecseo.com.
Privacy rights, cookie matters, data handling, and complaints use the privacy route. Do not send passwords, secret keys, full card details, or unrelated personal data.
Trust documents work together.
| Question | Owning page | Primary answer |
|---|---|---|
| How is security described? | /trust/security/ | Scope, controls, limits, responsibilities, and incident route |
| How do I report a vulnerability? | /trust/responsible-disclosure/ | Authorised contact, safe evidence, prohibited testing, response |
| Who controls my data? | /trust/data-privacy-overview/ | Semantec SEO, OpenAI, payment, and access boundaries |
| What GDPR rights can I exercise? | /trust/gdpr/ | Rights, verification, timing, complaints, and controller routes |
| How long is data kept? | /trust/data-retention/ | Retention criteria and category-level schedule |
| How are cookies handled? | /trust/cookies/ | Consent boundary, categories, withdrawal, and provider scope |
| What accessibility target applies? | /trust/accessibility/ | WCAG target, testing, feedback, and known limits |
| How are AI outputs governed? | /trust/ai-usage-policy/ | Purpose, human review, prohibited reliance, and accountability |
| Which providers are involved? | /trust/subprocessors/ | Provider register, role, data, location, and change process |
Check the controlling first-party and official sources.
These routes support the current public statement. External platform and legal sources remain subject to their own updates.
Semantec SEO Privacy Policy
Current first-party controller and platform boundary.
GPTs in ChatGPT
Official OpenAI conversation-access and external API boundary.
OpenAI data controls
Official current ChatGPT data-control information.
Move to the page that owns the next question.
Each route has a separate job so company, product, trust, legal, and compliance information does not collapse into one promotional page.
Owned route
Security overview
Security scope, controls, limits, and responsibilities.
Open route →
Owned route
Responsible disclosure
How to report a potential vulnerability safely.
Open route →
Owned route
Data privacy overview
Who controls which records and what users can do.
Open route →
Owned route
Accessibility
Accessibility target, feedback route, and current limitations.
Open route →
Owned route
Provider register
OpenAI, Stripe, Authflow.ai, and other confirmed providers.
Open route →
Owned route
Privacy Policy
The operative privacy notice.
Open route →