Who this policy covers
This policy covers SaveMyToken’s public pages, site search, tools, account features and Coding Plan services. The site publishes independent AI learning and comparison content. You can read the public content without creating an account.
SaveMyToken is operated by onetoall. Privacy questions can be sent to contact@savemytoken.com.
Information we process
- Site requests: Our hosting provider processes technical request information, which can include your IP address, browser details, the page requested, and the time of the request. Requests may appear in infrastructure logs.
- Search questions: When you submit a question in the site finder, it is sent to this site’s server to match published pages. A search entered in the search page URL may also appear in browser history and request logs. The current search does not send questions to an external AI model or save them in an application conversation database.
- Accounts, if enabled: Sign-up and sign-in use Clerk. The information involved depends on the sign-in methods configured for this site and may include an email address, profile details, and authentication/session information. Clerk processes this information to provide account access and security.
- Site analytics: Plausible Analytics measures visits to public pages using page URLs, referral sources, and general browser and device information. Plausible does not use analytics cookies or store visitors’ IP addresses. We use its reports to understand aggregate traffic, not to identify individual visitors.
- Coding Plan interaction analytics: On public plan, setup and service-status pages, we use Plausible to count page and section exposure, allowance-comparison result categories, user-marked setup checks, download clicks and checkout progress or issue categories. These custom properties contain fixed product identifiers and categories, not entered usage estimates, downloaded summary content, API keys, account or order IDs, error messages, private code or conversations. A setup check is self-reported; a checkout click is not evidence of payment. Recognized AI-site referrers are labeled as source candidates, not proof of a natural recommendation. These added events do not create a separate identifier or browser-storage record and are suppressed on local/preview hosts and when Do Not Track or Global Privacy Control is signaled. Existing page-view analytics have their own behavior as described above.
- Site analytics, if enabled: Google Analytics 4 receives page-view information so we can understand which public pages are used. This can include the page URL, referrer, browser and device information, and approximate location. The GA4 web stream is configured to redact the search page’s
qURL parameter and not to collect automatic site-search or form interaction events.
The interview scratchpad, RAG worksheets, and cost calculator run in your browser. Their entries are not submitted to SaveMyToken by those tools. Downloads you choose are created from the content or values shown in the tool.
Why we use it
We use request information to deliver and protect the site and to diagnose failures. We use a submitted search question to return relevant published content. If account access is enabled, Clerk uses account information to authenticate you and manage your session. We use Plausible Analytics reports to understand aggregate site traffic and improve the public pages. When Google Analytics 4 is enabled, we also use its reports for that purpose. The site does not include advertising pixels.
Cookies and service providers
If account access is enabled, Clerk uses cookies and related session mechanisms needed for sign-in and account security. Our hosting provider processes technical requests to serve the site. Plausible Analytics does not set analytics cookies. When enabled, Google Analytics 4 may use cookies or similar identifiers to measure visits. Retention and processing practices for these services depend on their settings and terms. Read more about Clerk’s authentication cookies, Vercel’s function logs, Plausible’s data policy, and Google Analytics cookies.
Links to model providers, publishers, and other external sites open services with their own privacy practices. We do not control those sites.
How Coding Plan API requests are handled
Your coding tool sends content to the SaveMyToken gateway, which forwards the model request to the upstream inference service configured for that route. The response returns through the gateway to your tool.
What content is sent?
A request can contain your prompt, code or document excerpts, conversation history, tool definitions and tool messages. Supported routes can also receive images included in the request. Your coding tool chooses which content to send and may process it through its own services; review that tool's settings and privacy terms separately.
What does the usage ledger record?
Our billing usage ledger records request and model identifiers, token and points counters, request status and timing rather than the prompt or response text. These records support allowance checks, usage settlement and billing investigations. They are separate from operational logs and any records held by your coding tool or the upstream service.
What about logs, retention and training?
Gateway and hosting services process operational records to authenticate keys, enforce limits, reconcile usage and investigate failures. Usage records, operational logs, upstream caches and provider retention are different parts of the request path. An upstream inference service may be operated by a hosting provider rather than the model's developer; its processing and retention follow the terms applicable to that route.
This policy does not provide a blanket zero-data-retention, no-training or processing-region guarantee across coding tools and upstream services. If your project requires particular handling, contact us to confirm the route, provider terms and processing requirements before sending confidential information. Do not include passwords or third-party API keys in prompts or tool output.
How can I ask about my data?
Email contact@savemytoken.com with the relevant account email, model or route, and an order or request ID if available. Describe the handling requirement or issue without sending a full API key, private code or complete conversation. We may need additional information to verify account ownership before handling a data request.
Payments and service records
Waffo provides hosted payment and subscription management. We retain your account ID, order and payment references, plan, price, purchase terms version, payment and delivery status, paid period, encrypted API key and usage counters to deliver and manage your service. Full payment-card details are collected by the payment provider and are not stored in our billing database.
Billing records are stored in our configured PostgreSQL service. Records needed for payments, disputes, security or legal obligations may need to be retained after account closure. Contact contact@savemytoken.com for account or billing data requests.
Storage and retention
The current site does not maintain an application database of search conversations, calculator entries, or worksheet answers. Technical request logs are retained according to the hosting provider’s settings and plan. If accounts are enabled, account and session information is retained under the configured Clerk service until it is deleted or expires, subject to its applicable settings and legal obligations. Plausible Analytics and, if enabled, Google Analytics retain their collected analytics data according to their respective settings and terms. We do not specify a fixed retention period here because those settings have not been verified for every deployment.
Your choices
You can browse public content without signing in. Avoid putting passwords, API keys, or sensitive personal information into site search or page URLs. You can use browser settings to limit cookies. If account access is available, use the account menu to review or change your profile and security settings. Depending on where you live, you may also have rights to access, correct, or delete personal information, or object to its processing.
Changes to this policy
We will update this page and its date if the site’s data handling changes, including if we add external AI conversations or a way to save user content. For our publishing practices, see Editorial standards.