Trust · Trust disclosure
One MIRENA interaction can involve Semantec SEO, OpenAI, and other service providers.
This overview identifies who controls which records, what Semantec SEO receives directly, what remains inside ChatGPT or another provider, and which privacy route applies.
Verified facts and boundaries.
These fields identify the entity, product, document, or operational boundary without turning related parties into the same entity.
Start with the record, not the product name.
Semantec SEO controls personal data where it decides the purpose and means, such as direct website, account, entitlement, support, billing, privacy, and business records it receives or creates.
OpenAI controls ChatGPT account, conversation, file, memory, training, and platform records under its own privacy terms. Stripe and Authflow.ai may control or process their own payment and access records.
Common data paths.
| Interaction | Typical data | Primary controller or platform | User route |
|---|---|---|---|
| Browse semantecseo.com | IP, device, pages, referral, security and cookie data | Semantec SEO and confirmed site providers | Privacy and cookie settings |
| Contact support | Name, email, message, account context, supplied files | Semantec SEO and communication providers | support@semantecseo.com |
| Pay for MIRENA | Billing identity, transaction, tax and payment records | Semantec SEO and Stripe according to role | Support and Stripe routes |
| Access MIRENA | Email, entitlement, authentication and access events | Semantec SEO and Authflow.ai according to role | Account support |
| Use MIRENA in ChatGPT | Prompts, chats, files and outputs | OpenAI for platform records; another provider if an action is used | OpenAI privacy and data controls |
| Exercise a privacy right | Identity, request, correspondence and response record | The controller receiving the request | privacy@semantecseo.com |
GPT builders cannot view individual conversations by default.
OpenAI states that GPT builders cannot view individual conversations users have with their GPTs. That platform statement does not mean every external action, app, support message, or uploaded record is invisible to every provider.
When a GPT uses an action or external API, relevant parts of the input may be sent to the named service. Users should review the interface confirmation and the recipient's privacy notice before proceeding.
Training, history, memory, and Temporary Chat.
OpenAI states that model-improvement use depends on the user's plan and data-control settings. Business, Enterprise, and Edu plans have different default treatment from consumer plans.
Temporary Chats have separate history, memory, training, and retention behaviour under current OpenAI guidance. These controls belong to OpenAI and can change independently of Semantec SEO.
Data minimisation.
- Provide only information needed for the SEO task
- Remove passwords, authentication codes, secret keys, and full card details
- Avoid personal data where anonymised or business-level information is sufficient
- Confirm authority before uploading client, employer, or third-party material
- Do not submit sensitive or regulated records by default
- Use Temporary Chat or plan-specific controls only after reviewing current OpenAI guidance
Rights and contacts.
Use privacy@semantecseo.com for personal data controlled by Semantec SEO. Use the OpenAI privacy portal or account controls for ChatGPT records controlled by OpenAI. Contact Stripe or Authflow.ai directly where they control the requested record, or ask Semantec SEO to clarify the route.
The Privacy Policy contains the detailed purposes, lawful bases, recipients, retention criteria, transfers, rights, and complaint information.
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 data-path record.
GPTs in ChatGPT
Official GPT conversation-access and external action information.
OpenAI data controls
Official training and Temporary Chat controls.
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
Privacy Policy
Operative privacy notice and processing details.
Open route →
Owned route
GDPR overview
Rights, timing, verification, and complaints.
Open route →
Owned route
Data retention
Category-level retention criteria.
Open route →
Owned route
Cookie overview
Device storage, consent, and withdrawal.
Open route →
Owned route
Provider register
External platform and service-provider record.
Open route →
Owned route
MIRENA inputs
Data minimisation and input suitability.
Open route →