Privacy Policy

This Privacy Policy explains how Pictograph LLC ("Pictograph", "we", "us") collects, uses, shares, and protects personal information when you use pictograph.io, app.pictograph.io, our APIs, and the hosted services we provide through them (the "Service"), and the choices and rights you have. Capitalized terms not defined here have the meanings given in our Terms of Service.

1. Who we are and what this covers

• Our users and visitors. Pictograph LLC, an Oregon limited liability company, is responsible for (and, under laws such as the GDPR, is the controller of) the personal information we collect about the people who use the Service and visit our websites.
• Content organizations upload. The images, datasets, annotations, and other content that organizations upload may contain personal information about other people, such as people who appear in images. We process that content on behalf of the organization that uploaded it, to provide the Service to it. That organization is responsible for the content and for having a lawful basis to process it. If you appear in content someone uploaded, please contact them; we will help where we can.
• Self-hosted deployments are not covered. Pictograph Enterprise Self-Hosted runs in the customer's own cloud environment and sends nothing to Pictograph. It is described in the Enterprise Self-Hosted Privacy Notice, not this policy.

2. Information we collect

Information you provide

• Account information: your email address, name, password (stored by our authentication provider in hashed form), and sign-in method. If you sign in with Google or GitHub, we receive your name and email address from that provider. We do not import your profile photo.
• Profile information: your username (generated from your name; you can change it), bio, README, avatar, profile colors, and pinned items. Your profile is public by default (see Section 5).
• Organization information: organization names, descriptions, and avatars; members and their roles; and invitations, including the email address of each person invited.
• Content: the images, video, datasets, annotations, models, comments, and other content you upload or create.
• Prompt history: prompts you submit for image generation and editing are saved to a history that only you can see. This is on by default, and you can turn it off in Settings.
• Billing information: your plan, billing contact, and purchase history. Card details are collected and stored by our payment processor, Stripe, not by us.
• Credentials for imports: if you import data from another service, the API key you provide is used for that import only and is not stored.
• Communications: what you send us when you contact support or otherwise correspond with us.

Information collected automatically

• Request logs: IP address, browser and device type (user agent), the pages and API endpoints requested, timestamps, and account and organization identifiers.
• Error reports: when the app encounters an error, it sends us the error details, the page address, your browser type, a session identifier, and the recent steps that led to it.
• API usage records: for each request made with an API key, the endpoint, method, response status, timing, size, user agent, and IP address.
• Security and abuse prevention: short-lived counters keyed to IP addresses and accounts that enforce rate limits, and a record (including IP address and user agent) each time someone reveals a stored API key.
• Usage and billing records: the compute your organization uses and the resulting charges and credits.
• Browser storage: see Section 11.

Information from others

• Organization owners and admins who invite you provide your email address.
• Google and GitHub, if you sign in with them; Stripe, about the status of payments; and services you import data from, for the content you import.

3. How we use information

We do not sell personal information, and we do not use it for targeted advertising. We do not make decisions that have legal or similarly significant effects on you based solely on automated processing.

4. AI processing of your content

• On upload. When you upload an image, we run AI models on it to create embeddings, automatic tags, and a depth map. They power search, similarity, and labeling in your organization, and they run on hardware provided by our GPU computing providers. Automatic tags on public datasets are shown publicly.
• On request. AI-assisted annotation, model training, and inference run on the same GPU infrastructure when you use those features.
• Features powered by Google. Image generation, image editing, and on-demand tagging send the relevant images and your prompt to Google's Gemini API. We use Google's paid service tier, under which Google does not use that content to improve its products; Google keeps it for a limited period to detect abuse and comply with the law. To show icons for tags, we may send tag names (never images) to Google, and the resulting icons are shared across the Service.
• No training on your content. We do not use your content to train any shared or foundation model, including any model we offer to other customers. Models you train belong to your organization.

5. Public content and how it spreads

• Your profile. Your profile is public by default: anyone, including people who are not signed in, can see your name, username, avatar, bio, README, pinned items, and public work, and can find you in the user directory. You can make your profile private in Settings. Comments you post show your name, username, avatar, and bio even when your profile is private.
• Public datasets and models. When a dataset or model is made public, its images, annotations, automatic tags, README, and other details can be viewed by anyone. We publish pages about public content on pictograph.io that are rebuilt about once a day, so changes, including making something private, can take up to a day to appear there. Search engines and AI crawlers may index and copy public pages.
• Hugging Face mirror. By default, a public dataset or model is also published to Pictograph's organization on Hugging Face, where Hugging Face's own privacy policy applies. You can turn this off with the "Mirror to Hugging Face" switch in the item's settings. Making the item private, or turning the switch off, makes the mirror private.
• Copies persist. Other users can import copies of public content into their own workspaces, and those copies remain after the original is made private or deleted. Copies that others downloaded, or that third parties cached, are outside our control.

Please do not make public any personal information that you do not have the right to share.

6. How we share information

Service providers. We use a small number of established service providers (sub-processors) to operate the Service. Each processes personal information only for the purpose below, under contractual confidentiality and data protection obligations. A current list of named sub-processors is available on request at support@pictograph.io.

• Within your organization. Owners and admins of an organization can see its members, their roles, and the content in its workspace.
• The public and other users. Public profiles and public content are visible to everyone, as Section 5 describes, including on Hugging Face when mirrored.
• Where you direct us. For example, to webhook endpoints and integrations you configure.
• Legal and safety. When we believe in good faith that the law requires it, or that it is necessary to protect people, the Service, or our rights. We report apparent child sexual abuse material to the National Center for Missing and Exploited Children.
• Business transfers. As part of a merger, acquisition, or sale of assets, subject to this policy.

7. Where information is processed

Pictograph is based in the United States, and we and our service providers process information primarily in the United States. If you use the Service from outside the United States, your information is transferred to and processed in the United States, where data protection law may differ from the law where you live. Where the law requires it, transfers to our service providers rely on their contractual safeguards, such as the European Commission's Standard Contractual Clauses.

8. How long we keep information

We may keep information longer where the law requires it or to resolve disputes and enforce our agreements.

9. Security

We protect information with industry-standard safeguards: all traffic is encrypted in transit over TLS, stored data is encrypted at rest, each organization's data is isolated from every other organization's, passwords are never stored in plain text, API keys are stored as one-way hashes with a separately encrypted copy so that you can view a key again in Settings (each reveal is recorded and the key's owner is notified), signed links to files expire quickly, and multi-factor authentication is available for every account. No method of transmission or storage is perfectly secure. If we learn of a security breach that affects your personal information, we will notify you as the law requires.

10. Your choices and rights

Controls in the app

• Make your profile private, and edit or remove profile information, in Settings.
• Turn prompt history on or off, and delete saved prompts.
• Choose which notification emails you receive, or use the unsubscribe link in any of them. Security emails cannot be turned off.
• Turn off the Hugging Face mirror for a public dataset or model, or make it private.
• Export your organization's data (owners and admins).
• Deactivate your account. Deactivation keeps your account data, hides your public profile, and removes you from your organizations; signing in again reactivates your account.

Your rights

Depending on where you live, you may have the right to know what personal information we hold about you and to access it; to correct it; to delete it; to receive a portable copy; to object to or restrict certain processing; to withdraw consent; and to opt out of the sale or sharing of personal information, targeted advertising, and profiling. We do not sell or share personal information for targeted advertising, or engage in such profiling. These rights apply under laws including the GDPR, the UK GDPR, the California Consumer Privacy Act, the Oregon Consumer Privacy Act, and similar laws in other states.

• How to make a request. Email support@pictograph.io with the subject "Privacy request", from the email address on your account if you have one. To permanently delete your account and personal information, use this method.
• Verification. We will verify your request, usually by confirming control of your account email. You may use an authorized agent, who must provide proof of authorization.
• Timing. We respond within the time the law requires, generally within 30 to 45 days, and we will tell you if we need more time.
• Appeals. If we decline your request, you may appeal by replying to our decision with the word "Appeal". We will respond to appeals within the time the law requires. If you remain unsatisfied, you may contact your state attorney general.
• Complaints. If you are in the European Economic Area, the United Kingdom, or Switzerland, you may also complain to your data protection authority.
• No discrimination. We will not treat you differently for exercising your rights.
• Organization content. Requests about content an organization uploaded (for example, a request to remove images of you) should go to that organization. We will forward requests to it and support its response.

11. Cookies and browser storage

• Sign-in. Your sign-in session is kept in your browser's local storage, not in a cookie.
• One first-party cookie. When you view images, we set a short-lived image delivery cookie, valid for about 15 minutes, that lets our content delivery network serve them.
• Preferences and caches. The app stores preferences (such as your theme, layout, and last workspace) in your browser, and caches image thumbnails there for up to 24 hours, including after you sign out. The pictograph.io website stores only your theme preference.
• Payments. On billing pages, Stripe's payment form may set its own cookies to prevent fraud, under Stripe's privacy policy.
• No advertising or tracking. We do not use advertising cookies, tracking pixels, or third-party analytics. Because we do not sell personal information or use it for targeted advertising, browser privacy signals such as Global Privacy Control and Do Not Track require no further action from us, and we honor Global Privacy Control as an opt-out request.

12. Children

The Service is not intended for anyone under 18, and we do not knowingly collect personal information from children. If you believe a child has provided us personal information, contact us and we will delete it.

13. Notice for US state residents

This section supplements the rest of this policy for residents of California and other US states with comprehensive privacy laws. In the last 12 months we have collected the following categories of personal information, from the sources and for the purposes described in Sections 2 and 3, and disclosed each category for business purposes only to the service providers described in Section 6. We have not sold or shared any personal information for cross-context behavioral advertising, and we have no actual knowledge of selling or sharing the personal information of anyone under 16.

We keep each category for the periods in Section 8. We use sensitive personal information only for purposes the law permits without offering a right to limit it.

14. Changes to this policy

We may update this policy. If a change is material, we will notify you by email or in the app before it takes effect. The "Last updated" date above shows when it last changed.

15. Contact

Pictograph LLC, an Oregon limited liability company. Questions and requests about this policy: support@pictograph.io (subject "Privacy request" for requests about your information).