Privacy Policy
This policy covers the Prompt Guard service and IronStride's related product and support pages.
1. Who is responsible
IronStride, operated by Randy Wijnans in the Netherlands, is responsible for the processing described here. Contact address: Oosterheemplein 500, 2721 NJ Zoetermeer, Netherlands. For privacy questions or requests, email info@ironstride.nl.
2. Information on your device
The extension stores your saved prompts, titles, tags, favorites and preferences in the current browser profile. An optional context profile is also stored locally. Normal library actions, including search, save, import and export, do not upload the library to IronStride. There is no cloud library synchronization or backup in this version.
Saved library content, including titles, tags and favorites, and the optional context profile are encrypted with AES-256-GCM before being written to persistent extension storage. The browser keeps the non-extractable encryption key in a separate IndexedDB record. There is no password to enter or recover. This reduces exposure of the stored content, but does not protect it from someone with full access to your browser profile or device, or from malicious code running inside the extension.
Choosing the browser context-menu action loads only the text you selected into the panel, using temporary browser session storage. The extension does not send the page URL, page title or your general browsing history as part of this action.
Account session tokens and your account email are kept in the browser's extension session memory, not in the extension's persistent local storage. They are cleared when the browser restarts or the extension is disabled, reloaded or updated. Reopening the panel during the same browser session keeps you signed in. A library JSON export is a readable, unencrypted file containing prompt content; it does not include account tokens, the encryption key or your context profile. Keep exported files privately.
Existing unencrypted library and context records are migrated when the extension accesses them, after the new key has been saved and encryption has been checked. If stored content or its key cannot be read, the extension reports an error instead of replacing it with an empty record. Clearing browser data, including IndexedDB, can remove the key and make saved content unreadable. Export before clearing data or uninstalling. IronStride cannot recover a lost local key or library.
3. What happens when you choose Improve
When you choose Improve, the current prompt and any context you chose to include are sent over HTTPS to IronStride's backend. The backend sends that content to OpenAI's API for rewriting and intent review, and returns the result to the extension.
IronStride's application database does not store full prompt bodies or generated results, and the application does not intentionally write them to its logs. It records request metadata and keyed fingerprints to handle usage limits, duplicate requests, costs and failures. Provider processing is described below.
Local pattern screening can block some sensitive information but can miss other information. Review your input and do not submit passwords, sign-in codes, API keys or confidential personal or business information. An AI intent check is an assessment, not a guarantee.
Copy and open AI copies your text to the clipboard and opens your chosen third-party site. You decide whether to paste or submit it there. That site's own terms and privacy policy apply to its use.
4. Accounts, email and service records
- Account and authentication: email address, user identifier, email verification and session information, used to provide sign-in and protect account access.
- Sign-in messages: recipient email address, the message containing a short-lived code and delivery information, used to send the code you requested.
- Usage and security: account and operation identifiers, usage periods, timestamps, status, temporary reservations, keyed fingerprints, model/token counts and cost estimates, used to apply allowances, prevent abuse and resolve interrupted requests.
- Technical requests: hosting and other providers process connection and security metadata, which can include IP addresses, request times, user-agent information and response status.
- Support: your email address, messages and information you choose to send, used to answer your request. Do not include secrets or confidential prompt content.
If you choose to purchase Pro or manage an existing subscription, Stripe handles checkout, payment methods, invoices and the customer portal. We send Stripe your account email and an account reference to link the purchase to your Prompt Guard account. You provide billing and payment information directly to Stripe. Our application receives the customer and subscription references, billing periods and payment or refund status needed to manage access and support. We do not receive or store complete card numbers or card security codes. We do not send your prompts or local library to Stripe.
Withdrawal and billing support records contain the contact and purchase details you provide, your declaration, receipt reference, submission time and the status of any cancellation or refund. We use them to process your request, provide confirmation and retain evidence of the outcome. Do not include sign-in codes, API keys or complete card details in these forms.
For a first Pro purchase, we retain the purchased contract version and text, amount, currency, purchase time, paid-period dates, account email and invoice and subscription references. We email the contract and purchase confirmation through Resend and record its processing status to prevent duplicate confirmations and resolve delivery problems. These records provide evidence of the agreed purchase independently of later website changes.
5. Providers and processing locations
- Netlify hosts the public website and the backend. The backend runs in the United States, in Ohio. Requests can also pass through Netlify's delivery and security infrastructure.
- Supabase provides account authentication and the operational database. The project's database region is Ireland. Authentication, support and security processing by the provider and its subprocessors may also involve other countries.
- Resend delivers requested account and service emails, including sign-in emails from noreply@auth.ironstride.nl.
- OpenAI processes the prompt and included context to generate a rewrite and check its intent.
- Stripe processes payment and subscription information, provides hosted checkout and the customer portal, and helps with fraud prevention and financial recordkeeping. Its processing can take place outside the European Economic Area. See Stripe's Privacy Policy for its processing and international transfer information.
This service is not limited to processing within the European Economic Area. Provider contracts describe international transfer safeguards, including standard contractual clauses where applicable. You can read the Netlify data processing agreement, Supabase data processing addendum and Resend data processing addendum. Contact us for information about the safeguards applicable to your data.
6. Why we process data
We process account and request data to provide the service you ask for, including sign-in, prompt improvement and support. Where the GDPR applies, our basis for this necessary service processing is performance of the service agreement or steps you request before using it.
Security, abuse prevention, cost control and troubleshooting serve our legitimate interest in running a secure, reliable and sustainable service. We may also retain information where a legal obligation requires it. We do not sell prompt content or use it for advertising.
You can use local templates and the library without giving us an account email. If you do not provide an email or submit a prompt, we cannot provide the corresponding online account or AI function. We do not use the AI output to make decisions about you with legal or similarly significant effects.
Payment, subscription, cancellation and withdrawal records are used to perform the service agreement, handle your requests and comply with applicable administrative or legal duties. Payment disputes and fraud prevention also require limited records to protect the service. Closing an account does not necessarily delete records that must be retained for those purposes.
7. Retention
Local library and profile records stay on your device until you delete them, clear the extension's storage or uninstall it. Exported backups remain wherever you save them. Signing out clears the extension's memory session and requests server revocation; an already issued access token can remain valid until it expires, currently within fifteen minutes. After updating from a version that stored the account session locally, the first panel opening removes that old credential record and asks you to sign in again.
Account records are kept while your account remains open, subject to a verified deletion request and any necessary security or legal retention. Account deletion is handled through support. There is no automatic deletion simply because you stop using the extension.
The operational database uses a daily cleanup with these eligibility rules:
- Expired request-limit records are removed after expiry.
- Closed operation records become eligible after ninety days, outside the current usage month. Records still needed for reconciliation are retained until the linked evidence can be removed.
- Reconciliation evidence for closed operations becomes eligible after 365 days.
- Old usage and budget records become eligible after approximately four hundred days once they have no reservation or linked operation. Processed billing-event identifiers from payment processing use a four-hundred-day cleanup rule.
- Open operations and unresolved reservations remain until their status is resolved. This prevents incorrect deletion of usage or financial evidence.
These rules concern the application database. Provider security logs, mail records and backup copies have separate retention. Support correspondence is kept for handling the request and any related follow-up, dispute or legal requirement.
The application cleanup periods above describe operational records. They are not a promise to erase invoices, purchased contracts, purchase confirmations or other legally required financial records after 400 days. Financial records and provider records follow their applicable retention rules. We keep purchase and withdrawal evidence as long as required for handling the agreement or request and applicable legal or dispute needs.
OpenAI states that API content is not used for model training by default. Requests disable stored responses, but that does not remove provider abuse monitoring. OpenAI's standard abuse logs can contain prompts and responses and are normally retained for up to thirty days, with legal and safety exceptions. See OpenAI's data controls. We do not claim zero data retention.
8. Security and permitted use of data
Requests use HTTPS. Provider API credentials stay on the server and are not embedded in the extension. Account access is authenticated and online usage is limited. These measures reduce risk but cannot guarantee complete security.
Information is shared with providers only as needed to supply or protect the disclosed functions. We do not use or transfer extension data for personalized, retargeted or interest-based advertising. We do not allow people to read submitted prompt content unless you specifically provide it for support, access is necessary for a security investigation, or disclosure is required by law.
These website pages contain no advertising trackers or analytics cookies added by IronStride. Netlify can still process the ordinary request information needed to deliver and secure them.
9. Your choices and privacy requests
You choose when to submit a prompt and whether to include context. Use the local library's export and delete controls, and Remove profile for stored context. IronStride cannot directly erase library copies or exports held only on your devices.
To request account access, correction or deletion, email info@ironstride.nl, preferably from your account email address. We verify ownership before handling account data. We never need your password, sign-in code, API key or card details. We may need to resolve an open operation or identify a necessary retention exception before completing deletion.
Where applicable, you can request access, correction, erasure, restriction or portability of your personal data, object to processing based on legitimate interests, and complain to your data-protection authority. In the Netherlands that is the Autoriteit Persoonsgegevens. If processing relies on consent, you can withdraw that consent without affecting earlier lawful processing.
10. Updates and contact
We will update this policy and relevant product or store disclosures when the service's data handling changes. Questions and requests: info@ironstride.nl.