Privacy Policy
Effective Date: October 15, 2026
High Agency, Inc. ("we," "our," or "us") values your privacy. This Privacy Policy explains what information we collect, why we collect it, and how you can control it.
1. What we collect
When you use pen.dev, we collect:
Account information
- Your email address
- Your name
- A username
- A password (or other authentication credential)
Organizations & shared workspaces. If you join or create an organization or shared workspace, we also process your name, email address, and role within that organization, which are visible to its administrators and members. An organization can verify ownership of its email domain: an administrator signs in with a Google Workspace account on that domain, and we store the verified domain, the identifier of the Google account used, and which administrator verified it and when. If an organization has verified your email domain, your account is added to that organization automatically, as a contributor, when you verify your email address; its administrators and members can then see your name, email address, and role, and you count as a user of that organization for billing purposes (see our Terms of Use).
Service operation & security data. We collect limited device and log data (e.g., IP address, browser/IDE version, OS, timestamps). If you use our IDE/Editor extensions, we process authentication tokens and minimal usage/diagnostic events required to operate core features. We do not collect your source code or keystrokes.
Developer keys. If you create a developer key for the CLI or CI/CD pipelines, for your personal space or for an organization, we store the key's name, its prefix, a hashed form of the key, who created it, and when it was last used. The full key is shown to you once when it is created and is not stored.
Billing & subscription information. If you or your organization subscribe to a paid plan, payments are handled by our payment processor, Stripe. Stripe collects your payment details and billing address directly; we do not receive or store your full card number. To set up the subscription, we share with Stripe the organization name (for a personal plan, your name), the purchaser's email address, and our internal identifiers for the organization and the purchaser. If you have accepted marketing cookies, the subscription record in Stripe also includes your IP address and browser user agent and, where present, the referral, campaign, and advertising click identifiers, Meta (Facebook) click identifiers, and the address of the external page you came from, as described in Section 4. We keep the resulting Stripe customer and subscription identifiers together with your plan, subscription status, and billing period. We also keep a copy of the billing event notifications that Stripe sends us (for example, subscription changes and invoice payments), which include the billing name, email address, billing address, and amounts shown on your invoices, so that we can apply them reliably and retry any that fail.
Usage records. To apply plan limits, we record how much each user and organization uses certain features: the days on which AI agents are used ("Agent days"), the number of image and SVG generations, and, for hosted AI models, the usage metadata described below. These records contain counts and identifiers, not your Inputs or Outputs.
Inputs & Outputs (content) — how they flow. pen.dev processes content you submit ("Inputs") and generates results ("Outputs") through different technical paths, depending on the feature:
- Text-based AI features using your own provider accounts (e.g., code generation, design assistance, chat completions via Anthropic, OpenAI, or GitHub Copilot). Inputs and Outputs are exchanged directly between your device and the third-party AI provider, using API credentials that you supply. They do not pass through, and are not accessible to, High Agency, Inc. servers at any time.
- Hosted AI models. If you choose an AI model provided by pen.dev ("hosted AI models", labeled "pen.dev Pro" in the app), your Inputs and Outputs are sent from your device to High Agency, Inc. servers and forwarded in real time to our model hosting provider listed at pen.dev/sub-processors, using service credentials provisioned by High Agency, Inc. We do not store, record, log, or cache this content on our servers, and we do not use it to train AI models. For billing and usage limits, we record usage metadata for each request (organization, user, model, token counts, cost, status, and duration).
- Image and SVG generation, image editing, and stock image features (e.g., Google Gemini, OpenAI, Quiver AI, Recraft, Unsplash). Requests, including any image you choose to edit, are transmitted through High Agency, Inc. servers to the relevant third-party provider.
- Website import. If you import a web page by entering its URL in the web app, our servers load the public page you specify and return it to your browser as editable layers. The page is processed in real time and is not stored on our servers. Importing through the desktop app's built-in browser or our browser extension happens entirely on your device.
Any local storage of Inputs or Outputs occurs solely on your device (e.g., browser localStorage or OS filesystem) for your convenience.
2. How we use your information
We use your information to:
- Let you sign in and personalize your onboarding
- Provide the cloud storage and sharing features you use
- Process subscriptions and payments, and apply plan limits
- Credit partners who refer new users to pen.dev
- Improve pen.dev based on how people actually use it
- Communicate about updates, new features, or policy changes
- Keep our systems secure and reliable
3. Legal bases (EEA/UK)
Where GDPR/UK GDPR applies, we rely on: Consent (where we ask for it, e.g., analytics cookies on shared-file pages and marketing cookies on pen.dev), Legitimate interests (service operation, security, abuse/fraud prevention, product improvement/analytics, product communications to our users, and referral attribution), Contract (providing requested access and features, including paid subscriptions), and Legal obligations (responding to lawful requests and keeping required tax and accounting records).
4. Analytics
We use PostHog (US Cloud) to understand how people use pen.dev.
What we collect. PostHog collects usage data (e.g., clicks, time spent in features, device/browser information, and error logs). In our implementation, these events are linked to your profile so we can provide product analytics, support, and security. We do not use analytics to target advertising. We may also create aggregated or anonymized statistics that no longer identify you.
What we do not collect. Our PostHog implementation is configured to exclude user Inputs and Outputs from analytics events. This means no prompts, no AI-generated content, and no source code are captured by analytics. We use analytics only to understand feature usage, performance, reliability, and security signals — not to track your personal activity outside of pen.dev.
No sale of data. We do not sell or rent your data.
International transfers. PostHog is hosted in the United States. For users in the EEA/UK, we rely on appropriate transfer safeguards (Standard Contractual Clauses, and for the UK, the UK Addendum/IDTA).
Error monitoring. We use Sentry to detect and diagnose crashes and errors. Error reports include technical context such as IP address, user identifier, device and OS information, and stack traces. Our implementation is configured not to include your Inputs or Outputs in error reports.
Web analytics. We also use GoatCounter, a cookie-free web analytics service, to measure aggregate website traffic without collecting personal information.
Cookies and similar technologies. Our website and web app use cookies and browser storage that are needed to keep you signed in and to remember your settings. On the pen.dev website, PostHog also stores an identifier in cookies and browser storage to recognize returning visitors. In the web app (app.pen.dev), analytics stays off until you accept the cookie notice. You can block or delete cookies in your browser settings; sign-in and other essential features may then stop working.
Referral attribution and marketing measurement. On pen.dev and docs.pen.dev, marketing measurement stays off until you accept the cookie notice. If you accept, we store cookies that expire after 30 days. They hold an anonymous visitor identifier and, where present, the referral or affiliate code, advertising click identifiers and campaign (UTM) parameters from the link you followed, and the address of the external page you came from. We then send a record to our referral partner, Evangelist, when you view our marketing, sign-up or sign-in pages, create an account, sign in, download the app, or make a purchase, so that we can measure our marketing and referrers can be credited. The record contains the information from those cookies (the visitor identifier in hashed form), the address of the page, your IP address and browser user agent, and, where available, hashed forms of your account identifier and email address, the operating system of the app you downloaded, the purchase amount and currency, and Meta (Facebook) click identifiers already stored in your browser. If you sign up or make a purchase after arriving through a referral or affiliate link, we also record that event, including the purchase amount and currency, in our product analytics. If you decline the cookie notice, we do not store these cookies, we delete any that were stored earlier, and we send nothing to Evangelist. We keep your choice in your browser, including in a cookie that lasts one year, so that we do not ask again.
Google Ads conversion measurement. If you accept the cookie notice, we also load Google's advertising tag (gtag.js) on the pen.dev marketing pages and on our sign-up and sign-in pages, and we report to Google Ads when an account is created (as a conversion with a nominal value of USD 1), so that we can measure which of our advertising campaigns lead to sign-ups. Google uses its own cookies and identifiers for this and receives the address of the page you are on, your IP address and browser user agent, and advertising click identifiers from the link you followed. We do not send Google your name or email address. Google's handling of this data is described in Google's privacy policy. If you decline the cookie notice, the tag is not loaded.
4a. Third-party image and SVG providers
pen.dev uses third-party services to generate, edit, or source images and SVG graphics, including Google Gemini, OpenAI, Quiver AI, Recraft, and Unsplash.
How the image and SVG flow works. Image- and SVG-related features operate differently from text-based AI features and hosted AI models. When you use image generation, SVG generation, image editing (such as background removal or vectorization), or stock-image features, your request and any content you intentionally submit, including an image you choose to edit, are transmitted through High Agency, Inc. servers to the relevant third-party provider. This transmission is the minimum technically necessary to fulfill your request and is performed in real time. We do not store, record, log, or cache this content on our servers — it is forwarded to the third-party provider and the response is returned to you along the same path. For image editing, the provider makes the edited result available at a temporary address, from which your device downloads it directly. For stock image search (Unsplash), pen.dev's agent generates search queries derived from your project context; your prompts are not transmitted verbatim to Unsplash.
Third-party retention. Once forwarded, content is subject to the third-party provider's own terms, privacy policies, and retention practices. We do not control, and are not responsible for, those practices. Your use of third-party services is also subject to the providers' own licensing terms, including any attribution or usage requirements.
International transfers. Image providers may process data outside the EEA/UK. We rely on appropriate transfer safeguards (e.g., Standard Contractual Clauses) where required.
4b. Cloud files, sharing, and collaboration
Some pen.dev features let you save files to your pen.dev workspace or share your work with others. These features work differently from the AI request flows described above: content you deliberately save or share is stored on our infrastructure (Google Cloud Platform, in the United States) so we can provide these features.
What we store. When you use cloud or sharing features, we store the files and designs you save to your workspace (including their version history), preview thumbnails we generate from them, export archives you create, share links, and comments posted on shared files (including the commenter's name, the comment text, any images attached to the comment, and — for signed-in users — their account identifier).
This applies only to content you deliberately save or share using these features. The commitments above remain unchanged for everything else: AI requests continue to pass through in real time without being stored, and files you work with locally stay on your device.
Who can access shared content. By default, anyone with a share link can view, comment on, and download the shared file. Where available, sharing controls let you restrict access — for example to your organization or workspace members, specific people, or email domains — and choose what recipients can do (view, comment, or download). Restricted links require the recipient to sign in with a pen.dev account, Google, Microsoft, or a one-time code sent by email; we then process the recipient's email address and sign-in identifier to verify access and keep them signed in.
Comment notifications. When someone comments on a file you shared, we may email you a summary that includes the comment text and the file name. You can manage these emails in your account settings.
Deletion. You can delete stored files, versions, shares, and comments at any time. Deleted files and shares move to the workspace trash, where a workspace owner or admin can restore them or delete them permanently; permanent deletion removes them from our storage. Deleted comments are no longer shown. Deleting your account permanently deletes the content of your personal workspace and the shares you created, and removes your comments from shared files; content you saved in an organization's workspace stays with that organization.
5. International transfers
If we transfer personal data outside the EEA/UK, we use appropriate safeguards such as EU Standard Contractual Clauses (and, for the UK, the UK Addendum/IDTA) or rely on another valid transfer mechanism.
6. Emails, communication & sub-processors
Email. We use Twilio SendGrid to send onboarding, product communications, and transactional emails (e.g., access confirmations, account notifications, and comment notifications). To send product communications, we keep your name and email address in a contact list with this provider. You can unsubscribe from marketing emails anytime using the link inside the email. Transactional emails necessary to provide the service may still be sent.
Sub-processors. We share personal data with sub-processors acting on our instructions. A current list of our sub-processors and their purposes is maintained at pen.dev/sub-processors. We update that list prior to engaging any new sub-processor.
Data handled. These sub-processors process account data and operational metadata (e.g., email addresses, authentication tokens, usage events, error logs). Our infrastructure providers also store the cloud files and shared content described in Section 4b, our email provider delivers comment notifications that include comment text, and our payment processor handles the billing details described in Section 1. Sub-processors do not receive or store Inputs/Outputs from text-based AI features used with your own provider accounts, which are exchanged directly between your device and the relevant third-party AI provider. Where you use hosted AI models, your Inputs and Outputs pass through our servers in real time to the model hosting provider identified at pen.dev/sub-processors and are not stored by us. Image, SVG, image editing, and stock image requests transit through our infrastructure in real time but are not stored.
Safeguards. We do not sell or rent your data. We enter into data-processing agreements with all sub-processors and require appropriate security measures. International transfers from the EEA/UK rely on Standard Contractual Clauses (and, for the UK, the UK Addendum/IDTA) or another valid transfer mechanism.
Data Processing Agreement (DPA). For regulated, enterprise, or business customers requiring a signed Data Processing Agreement, please contact hq@pen.dev.
7. How we store and protect data
Inputs and Outputs. Inputs and Outputs from text-based AI features used with your own provider accounts are not stored on our servers — they are exchanged directly between your device and the relevant third-party AI provider. Inputs and Outputs from hosted AI models pass through our servers in real time on their way to our model hosting provider and are not stored, recorded, logged, or cached on our servers. Image, SVG generation, image editing, and stock image requests likewise transit through our infrastructure in real time and are not stored, recorded, logged, or cached. Inputs and Outputs may be stored locally on your device (e.g., localStorage or filesystem), and you can delete them by clearing local storage or removing local files.
Security. Account data, operational metadata, and the cloud files and shared content described in Section 4b are stored securely using modern encryption (in transit and at rest) and access controls. We keep data only as long as needed to run pen.dev or as required by law.
Deletion requests. If you delete your account or ask us to remove your information, we will do so within a reasonable timeframe unless we are legally required to retain it.
Typical retention periods
The retention periods below apply to account data, operational metadata, and cloud files & shared content. They do not include Inputs/Outputs from text-based AI features or hosted AI models (not stored on our servers) or image, SVG, image editing, and stock image content (forwarded in real time, not retained).
| Data category | Retention |
|---|---|
| Account & onboarding data | 24 months after account deletion, or until you request deletion |
| Cloud files & shared content (workspace files, version history, thumbnails, export archives, comments) | Retained until you permanently delete the content from the trash or delete your account. Permanently deleted files are removed from our storage; residual copies in backups are purged within a short period thereafter. Deleted comments are no longer displayed, and their text is erased on request. |
| Billing & subscription records (Stripe identifiers, plan, subscription status, billing periods) | Kept for as long as required by tax and accounting laws, including after your organization's account is deleted. This covers the subscription records, the invoices and payment records held by Stripe, and the billing event notifications described in Section 1. |
| Usage records (Agent days, generation counts, hosted AI model usage metadata) | Kept for as long as your organization's account exists. Deleting a user's account does not delete that user's usage records; they keep the internal user identifier of the deleted account. |
| Diagnostic logs (system errors and crashes; do not contain Inputs/Outputs) | Error reports are kept for up to 90 days and server logs for up to 30 days |
| Marketing contacts | Until you unsubscribe or request deletion |
| Suppression records (to honor unsubscribe) | Retained as required to honor your opt-out |
| Backups | Up to 30 days before they are overwritten |
Where legally required or necessary to establish, exercise, or defend legal claims, we may retain limited data for longer.
8. Your rights
Depending on your location (including the EU/UK), you may have the right to access, rectify, erase, object to or restrict processing, and request data portability. You can withdraw consent at any time without affecting the lawfulness of processing before withdrawal, and you can complain to your local data protection authority. To exercise your rights, contact hq@pen.dev. We may ask you to verify your identity and will respond within 30 days where required by law.
9. Children
pen.dev isn't intended for children under 16, and we don't knowingly collect their information.
10. Changes
We may update this Privacy Policy from time to time.
If we make major changes, we'll post an update here or notify you directly.
11. Contact us
Data controller. For the purposes of GDPR and UK GDPR, the controller of your personal data is High Agency, Inc.
Email: hq@pen.dev
Mailing address:
High Agency, Inc.
440 N BARRANCA AVE #2993
COVINA, CA 91723
USA
For data subject requests (access, rectification, erasure, portability, objection, restriction, or withdrawal of consent), please contact us at hq@pen.dev with the subject line "Data Subject Request."