Bring your own provider keys
The experimental monitor supports optional OpenAI and Perplexity API connections. Consumer ChatGPT or Perplexity subscriptions do not include API billing or automatically provide an API key.
- Create API credentials in the provider's own developer account.
- Keep provider project budgets and usage alerts conservative.
- In the current prototype, account-scoped keys are configured by the operator through the protected provider-secret workflow; public self-service setup may vary by release.
- Never paste a provider key into a scan URL, report, support screenshot, or ordinary form field.
Billing, limits, and provider processing
OpenAI and Perplexity bill API use under their own terms. Your SEO Wizard does not convert a consumer subscription into API credit.
- The current default ceiling is 20 provider calls per account per UTC day.
- A run can use one or two providers, so one run may consume one or two provider calls.
- Output length and request timeouts are bounded, but provider-side budgets and alerts remain the account owner's responsibility.
- The research query and location context are sent to each selected provider for processing.
Encrypted key storage
Account-scoped provider credentials are encrypted at rest before storage. The application uses a server-held encryption key and does not return full secrets in reports or browser storage.
- Stored keys are partitioned by the account or entitlement subject.
- Removing a provider credential disconnects future requests but does not cancel the provider account.
- Provider credentials are not included in exported scan reports or monitor history.
What monitor history retains
The current prototype saves the query, optional location, target definitions, provider and model context, answer text, parsed cited and consulted sources, citation metrics, timestamps, and comparison evidence under the account subject.
- Saved answer history can contain text returned by OpenAI or Perplexity.
- The prompt does not include scanned page text, and page content is not sent to the provider as monitor instructions.
- History supports same-query comparisons but should not be treated as a complete record of consumer-product answers.
Retention and deletion
Retention controls are still being finalized for public release. Until self-service history deletion is available in a release, contact support to request deletion of stored monitor history or account-scoped provider credentials.
- Deleting a local desktop copy or export does not delete a hosted copy.
- Operational backups and security records may expire on a separate schedule where legally or technically required.
- Do not use the monitor for confidential, regulated, personal, or customer-identifying queries.
Official references
- OpenAI API data controls: OpenAI documents API data handling and control options.
- Perplexity privacy and security: Perplexity documents API privacy and security practices.
FAQ
Does my ChatGPT subscription pay for OpenAI API probes?
No. OpenAI API usage is billed separately through the API account and project.
Are provider keys included in reports?
No. Provider credentials are stored separately from reports and monitor history and should never be shown in exports.
Can I delete saved monitor answers?
Contact support to request deletion while public self-service history deletion is being finalized. Provider credentials can also be removed to disconnect future calls.
Keep the Next Step Small
Use the related guides to confirm what the page needs. Ask for support only when the change reaches code, templates, or server settings you do not want to guess at.
Contact Your SEO Wizard