Is my data really private?

Yes. All substitution runs in your browser tab. No data is sent to any server. Session history lives only in localStorage. Shareable URLs encode your data as a base64 string in the URL — no server stores it. Verify by opening your browser's Network tab (F12 → Network) and observing zero outbound requests when you click "Process All".

How does batch pagination work?

Set a batch size (10, 25, 50, 100, 250, or 500) using the Batch Size control above the Process button. "Process All" runs the first batch starting from row 1. A "Process Next N" button then appears — click it to advance through the dataset in controlled chunks. This is useful for spot-checking results before committing to a full large-dataset run.

How do I save a custom template?

Click the "Save" button next to the template editor header. Give your template a name and optional description, then click "Save Template". Your custom templates appear in the Template Library under the "My Templates" tab. They are stored in your browser's localStorage and persist across sessions. You can edit or delete them at any time.

Diff view shows a side-by-side comparison of the original template (left) and the substituted result (right). {{variable}} placeholders are highlighted in amber on both sides — the left shows the placeholder name, the right shows the substituted value. This makes it easy to audit substitution accuracy at a glance, especially for multi-variable CSV templates.

How does multi-column CSV substitution work?

Upload or paste a CSV where the first row contains column headers (e.g., product_name, category, price). The tool automatically maps each {{column_name}} placeholder in your template to the corresponding column value for each row. Column names are case-insensitive and spaces are converted to underscores.

How accurate is the token estimator?

The estimator uses the ~4 characters per token heuristic, accurate to within 10–15% for standard English text. For non-English content, code, or heavily punctuated text, actual token counts may differ. For precise counts, use the tokenizer provided by your target model's API.

Legal

Privacy Policy

Effective date: May 1, 2025

The short version: The core batch processing tool runs entirely in your browser. Your prompt templates, variable data, and outputs are never sent to our servers. We collect only what is strictly necessary for optional features like the waitlist and contact form.

1. Overview

PromptProcessor.com ("we", "us", "our") is committed to protecting your privacy. This Privacy Policy explains what information we collect, how we use it, and what choices you have. It applies to all users of the PromptProcessor.com website and service.

The architecture of our core tool is privacy-first by design: all prompt substitution, template processing, and result generation happens locally in your web browser using JavaScript. No prompt templates, variable lists, or processing outputs are transmitted to our servers during normal tool operation.

2. Information We Collect

We collect information in the following limited circumstances:

2a. Information you provide voluntarily

Waitlist registration: If you submit your email address to join the Pro waitlist, we store that email address to send you updates about the Pro launch. You can request removal at any time by contacting us.

Contact form submissions: If you use the contact form, we collect your name, email address, selected subject, and message content. This information is used solely to respond to your inquiry.

2b. Information collected automatically

Server logs: Like most web servers, ours automatically records standard access log data including IP addresses, browser type, referring URLs, and pages visited. These logs are used for security monitoring and are retained for a limited period.

Analytics: We may use privacy-respecting analytics to understand aggregate usage patterns (such as which pages are visited most frequently). We do not use Google Analytics or other third-party tracking services that build cross-site user profiles.

2c. What we do NOT collect

We do not collect, store, or have access to: your prompt templates, variable data inputs, processing results, session history (stored only in your browser's localStorage), or custom templates you create (also stored only in localStorage). This is not a policy choice — it is an architectural fact. The tool does not transmit this data to any server.

3. How We Use Your Information

We use the limited information we collect for the following purposes:

Waitlist emails are used only to notify you when the Pro tier launches. We will not send marketing emails unrelated to the product.
Contact form data is used to respond to your inquiry and is not used for marketing or shared with third parties.
Server logs are used for security monitoring, abuse prevention, and diagnosing technical issues.
Aggregate analytics are used to understand how the tool is used and to guide product decisions.

We do not sell, rent, or trade your personal information to any third party. We do not use your information for advertising targeting.

4. Cookies and Local Storage

The core tool uses your browser's localStorage to persist session history, custom templates, and waitlist submission status. This data is stored entirely on your device and is never transmitted to our servers. You can clear it at any time through your browser's developer tools or by clearing site data.

We may use a minimal session cookie for optional features that require server-side authentication (such as the Pro tier, when available). We do not use third-party tracking cookies or advertising cookies.

5. Third-Party Services

Real AI Runner: If you use the Real AI Runner feature with your own API key, requests are sent directly from your browser to the respective AI provider (OpenAI, Anthropic, etc.). These requests bypass our servers entirely. Your API key is stored only in your browser's sessionStorage for the duration of your browser session. We never see or store your API key.

Shareable URLs: When you generate a shareable URL, your template and data are encoded as a base64 string in the URL itself. No server stores this data. Anyone with the URL can decode it, so do not share URLs containing sensitive information.

6. Data Retention

Waitlist email addresses are retained until you request removal or the waitlist program ends. Contact form submissions are retained for a reasonable period to allow us to follow up on ongoing inquiries, after which they are deleted. Server logs are retained for a limited period for security purposes.

7. Your Rights

Depending on your jurisdiction, you may have the right to access, correct, or delete personal information we hold about you. To exercise these rights, contact us through the Contact page. We will respond within a reasonable timeframe.

For data stored in your browser (localStorage, sessionStorage), you have full control and can delete it at any time through your browser settings — no request to us is required.

8. Security

We take reasonable technical and organizational measures to protect the limited personal information we hold. However, no method of transmission over the internet or electronic storage is completely secure. We cannot guarantee absolute security.

The privacy-first architecture of the core tool means that the most sensitive data — your prompts and variable data — never reaches our servers, which significantly reduces the risk surface compared to traditional SaaS tools.

9. Children's Privacy

The Service is not directed to children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact us and we will delete it promptly.

10. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated effective date. For material changes, we will make reasonable efforts to notify waitlist subscribers. Continued use of the Service after changes are posted constitutes acceptance of the revised policy.

11. Contact

If you have questions about this Privacy Policy or our data practices, please contact us through the Contact page.