ActionForge — Privacy Policy
Effective date: 13 August 2026
ActionForge is operated by Prita Sharma, a sole proprietor located in San Diego, California, United States. Contact for any privacy question or request:
pritasharma25@gmail.com.
This policy describes what the Service collects, why, who it is shared with, and how long it is kept. It is written against what the system actually stores rather than in general terms.
1. What we collect
You give us
| Data | When | Why |
|---|---|---|
| Email address | Signing up | Identifies the account, prevents one person minting unlimited free accounts, and is how we reach you about billing or service changes |
| Account name or label | Signup or key issuance | Distinguishes tenants |
| Tool descriptions and JSON Schemas | Creating a tool | Sent to our code-generation provider to produce the tool |
| Invocation inputs | Every tool call | Executed by the tool; recorded in full — see Section 2 |
Generated for you
| Data | Why |
|---|---|
| Generated source code | Stored per tool so it remains reproducible if the execution platform loses its copy |
| Invocation results | Recorded in full alongside inputs |
| Execution timing and counts | Billing and quota enforcement |
Generated automatically
| Data | Why |
|---|---|
| A one-way digest of your API key | Authentication. We never store the key itself and cannot recover it |
| A one-way digest of your network address | Rate limiting signup. We do not store your IP address — only a hash from which it cannot be read back |
| Stripe customer and subscription identifiers | Linking your account to its subscription |
| Server logs | Operating and debugging the Service. These record account identifiers, event identifiers, and error text — never API keys, request bodies, or email addresses |
We do not use cookies or tracking technologies. ActionForge is an API with no user interface.
2. Invocation inputs and results are stored in full
This is the most important thing in this policy. Every time a tool is called, the input you sent and the result it produced are written to our database and retained.
They are kept so that usage can be billed accurately, so a failing tool can be diagnosed, and so abuse can be investigated. They are not used to train any model, and they are not sold or shared for advertising.
Because of this, do not send sensitive personal data through ActionForge. It is not designed for and must not be used with protected health information, payment card numbers, government identifiers, financial account credentials, or comparable categories. If you need to process such data, do not put it in a tool input.
3. Legal bases
Where the GDPR or UK GDPR applies to you, we rely on:
- Contract — account data, tool definitions, invocation records, and billing
data are all necessary to provide the Service you asked for.
- Legitimate interests — rate-limit digests, server logs, and abuse
investigation, balanced against your interests and limited to what is needed to keep the Service running and unabused.
- Legal obligation — retention of billing records for tax and accounting.
If you submit personal data belonging to someone else through a tool input, you are the controller of that data and we process it on your behalf.
4. Who we share it with
We do not sell personal information and we do not share it for advertising. We use these providers, each of which processes only what its function requires:
| Provider | What it receives | Purpose |
|---|---|---|
| Anthropic | Your tool descriptions and JSON Schemas | Generating tool source code |
| Cloudflare | Generated code, and invocation inputs at call time | Executing your tools |
| Supabase | All stored data described above | Database hosting |
| Stripe | Your email and payment details, which you enter directly with Stripe | Subscription billing. We never see or store your card number |
| Railway | Traffic to the API | Application hosting |
We may disclose data where legally required, and we will tell you unless prohibited from doing so.
Data is processed in the United States. Where required for transfers out of the EEA or UK, we rely on the Standard Contractual Clauses adopted by our providers.
5. How long we keep it
| Data | Retention |
|---|---|
| Account, email, key digests | Until you delete the account |
| Tools and generated source | Until the tool or the account is deleted |
| Tool deletion audit records | Retained after a tool is deleted, including its generated source, so deletion is recoverable. Removed when the account is deleted |
| Invocation records | Retained after the tool is deleted, with the link to the tool removed, so a billing period cannot be recomputed after the fact. Removed when the account is deleted |
| Billing records (Stripe events, invoices) | Up to 7 years, as required for tax and accounting, even after account deletion |
| Rate-limit digests | Automatically expired shortly after their time window closes |
| Server logs | Retained only as long as our hosting provider's log window |
Deleting your account removes its tools, keys, invocation records, and deletion audit records. Ask at the contact address above and we will confirm when it is done.
6. Your rights
Wherever you are, you may ask us to access, correct, export, or delete your data, and we will respond within 30 days at pritasharma25@gmail.com. We may need to verify you control the account before acting.
If you are in California (CCPA/CPRA), you have the right to know what personal information we collect and why, to request deletion or correction, to request a portable copy, and not to be discriminated against for exercising these rights. We have not sold or shared personal information in the preceding twelve months, and we do not knowingly collect data from anyone under 16.
If you are in the EEA or UK, you additionally have the right to object to or restrict processing, to withdraw consent where we rely on it, and to complain to your local supervisory authority.
7. Security
API keys are stored only as SHA-256 digests. Every request is authenticated and scoped to its account by a database query filter, so one tenant's data is not reachable from another's credentials. Traffic is encrypted in transit. Generated code is scanned before deployment and refused if it attempts network access or runtime code execution.
No system is perfectly secure. If we become aware of a breach affecting your personal data, we will notify you and any required regulator without undue delay.
8. Children
The Service is not directed to anyone under 16, and we do not knowingly collect their data. If you believe a child has provided us data, contact us and we will delete it.
9. Changes
We may update this policy. Material changes will be notified to the email on your account or posted here before taking effect. The effective date above marks the current version.
Questions or requests: pritasharma25@gmail.com