TheSmartPrompt
Back Home Open Templates
Privacy Policy

How TheSmartPrompt handles visitor, prompt, and contact data

This page explains what information is collected when someone browses TheSmartPrompt, uses the workspace, submits the contact form, or opens public articles. It is written to match the product as it works today.

Effective date: May 2, 2026 Applies to: Public site and workspace

What we collect

TheSmartPrompt currently collects a limited set of information based on the part of the product being used.

  • Contact form submissions: name, email, company, message, and submission time.
  • Public visit tracking: requested page path, internal endpoint, referrer, browser user-agent, a site session visitor id, and visit timestamp.
  • Local browser workspace data: saved prompts, selected template, lesson progress, sidebar state, workspace prompt drafts, and local preference settings are stored in the browser using local storage.
  • Published content access: visits to blog articles, template pages, learn pages, and public workspace routes may be logged through the visit tracker described below.

How we use it

Collected data is used to run the product, reply to inbound requests, and understand what parts of the site people are actually using.

  • Contact form details are stored privately so the site owner can review and reply.
  • Visit tracking is used to show page-level traffic, recent activity, and referrer information in the admin analytics screens.
  • Local browser data is used to keep the workspace usable between visits without forcing an account system.

Prompt and workspace data

Prompts you type into the public analyzer and rewrite workspace are primarily handled in the browser unless you choose a live AI action. Saved prompts in the normal user workflow are stored locally in the browser rather than automatically added to a server-side account.

  • Local actions: copy, save, selected-template state, and local prompt drafting are stored in the browser only.
  • Live AI actions: if a user chooses live rewriting or generation and enters an API key, the request content is sent to the chosen model provider for that request.
  • API keys: the app is designed to use live API keys for the current request flow and does not add them to the admin contact database or public analytics tables.
Do not paste confidential client, legal, medical, financial, or regulated material into live AI flows unless you are comfortable sending that content to the selected provider.

Visit analytics

The site includes a lightweight first-party visit tracker. It logs public page views so the site owner can understand page activity, top paths, visitor counts, referrers, and recent traffic.

  • Tracking is limited to public GET page requests.
  • Static assets, API endpoints, and private management pages are not included in the visit tracker.
  • The visitor count is approximate and based on a site session identifier stored in the browser session.

Sharing and external processors

TheSmartPrompt may send data to third-party AI providers only when a user explicitly uses a live model feature. Those providers process the prompt content according to their own terms and privacy policies.

  • Examples may include OpenAI, Anthropic, Google, Mistral, OpenRouter, or other providers enabled in the workspace.
  • Normal public browsing analytics described on this page are stored by the site itself in the local application database.

Storage and retention

Contact records and visit logs are stored in the application database used by the site owner. Browser-saved prompt data stays in the visitor's own browser until it is cleared, overwritten, or removed by local storage cleanup.

  • Contact records may remain until they are reviewed or manually deleted from the private records area.
  • Visit logs may remain in the site database until the operator rotates or removes them.
  • Browser local storage persists according to the user's own browser behavior and cleanup choices.

Your choices

You can choose not to submit the contact form, avoid live AI actions, or clear local browser storage if you do not want prompt drafts and preferences kept on the device.

  • Use the contact form only if you are comfortable sharing your name, email, company, and message.
  • Clear browser storage if you want to remove locally saved prompts and workspace settings from the device.
  • Ask the site owner to remove a stored contact message if needed.

Contact and policy updates

If you need to ask about privacy, stored contact submissions, or the way prompts are handled, use the contact page linked from the public site. This policy can be updated as the product changes, especially if authentication, payments, or broader analytics are added later.

This document is a practical product policy page, not legal advice. If the site later handles customer accounts, payments, or regulated data, it should be reviewed and expanded before broader public launch.