Privacy Policy

1. Who we are

Picverce AI (picverce.com) is a bilingual suite of AI image tools and generators. This policy explains what information we collect when you use Picverce AI, how we use it, and the choices you have. If you have questions at any point, reach us at support@picverce.com.

2. What this policy covers

One policy, five places you can use Picverce AI from:

• The website at picverce.com, where the tools, your History, and your account live.
• The Public API at api.picverce.com, which you call from your own software using an API key.
• The MCP connector at mcp.picverce.com, which lets an assistant such as Claude run tools on your behalf.
• The Shopify app, which works on product images in a store you connect.
• The WordPress plugin, which works on images in a site you install it on.

Section 7 describes each of the last four in more detail. When you use Picverce AI through Shopify or WordPress, those platforms also handle your data under their own policies, which are theirs to explain and not ours to speak for.

3. Information we collect

We collect information in a few ways:

• Account information you provide when you create an account, including your email and login details.
• Images you upload, and the images our tools generate or edit for you.
• What you send with a job, wherever it comes from: the image or the description, and the tool, model, and settings you chose.
• API key details, meaning the name you give a key, its first few characters so you can recognise it in a list, when it was made, and when it was last used. We never store the key itself.
• Webhook settings, if you set one up: the address you give us, the events you asked for, and a signing secret so you can check a message came from us.
• Connection details for an app, such as the address of a Shopify store you connect and the state of the runs you start there.
• Usage data, such as which tools you use and how often.
• Subscription and credit information, including your plan, credit balance, and billing status.
• Device and log data, such as browser type and IP address.
• Cookies and similar technologies (see section 10).

4. How we use it

We use this information to:

• Run the tools you use and deliver your results
• Maintain your account, credit balance, and History
• Authenticate API keys and show you what you have used
• Process payments and manage your subscription
• Provide support when you contact us
• Keep the Service secure and prevent abuse
• Improve existing tools and build new ones

5. Service providers

We work with trusted third parties to help run the Service, for example to process payments, host the app securely, and power automated image processing. These providers only receive the information needed to do their job and may not use it for anything else.

6. How long we keep things

When you process or generate an image on the website, the result can be saved to your account History so you can find it again later. How long an item stays visible in your History depends on your current plan:

This window is based on your current plan, so upgrading can extend how far back your History reaches, and downgrading or cancelling can shorten it. You can delete individual items from your History earlier at any time. We do not use your uploaded images to train our AI models.

Everything else keeps its own clock:

• Job records from the Public API, the MCP connector, the Shopify app, and the WordPress plugin are kept on your account so you can see what you ran and what it cost. These do not appear in your website History. Ask us and we will delete them.
• API keys stay until you revoke or delete them. A revoked key stops working immediately.
• A Shopify connection lasts until the app is uninstalled. See section 7.
• A WordPress key lives on that WordPress site and is removed when the plugin is deleted. We never hold a copy of it.

7. Using Picverce AI from other places

The Public API

You can create API keys in your account and use them to send jobs to api.picverce.com from your own software. A job carries the image or the description you send, plus the tool or model and the settings you picked, and it returns a result and a status.

We do not store the key itself. It is shown to you once when you create it, and what we keep is a one-way fingerprint that can check a key but cannot reproduce one, alongside the first few characters so you can tell your keys apart.

If you set up a webhook, we send job notifications to the address you gave us and sign them with a secret so you can confirm they came from us. What happens to a message after it arrives is up to the endpoint you built.

The MCP connector

mcp.picverce.com lets an MCP-compatible assistant, such as Claude, run Picverce AI tools for you. It uses your own API key and your own credits, and it keeps nothing of its own: every request passes through to the Public API and is handled exactly like any other API job. What you ask an assistant to work on is sent to us for that job, so send it the same way you would send it to us directly.

The Shopify app

When you install the app and connect it with your own Picverce AI API key, we store the address of the store, the access token Shopify issues for it, your API key and the few characters of it we display, any callback settings you configure, and the state of the runs you start. Credentials are encrypted.

The app works on product images you select. It does not read, receive, or store information about your customers.

When the app is uninstalled we delete the credentials and the run history straight away, and the rest of the connection is erased when Shopify asks us to, about two days later. Images the app has already written into your store stay in your store, because they belong to it. Shopify handles your store data under its own policies.

The WordPress plugin

An administrator saves an API key in the plugin settings. That key is stored on the WordPress site itself, never in a visitor browser, and we do not hold a copy of it.

When someone runs a tool, that site sends us a copy of the image they chose, or the description for a new one, along with the settings. We send back a result, which the plugin saves into that site Media Library.

Nothing is sent until a key is saved and somebody presses a button. The plugin does not report to us in the background, and we do not receive the site visitors, its posts, its users, or its settings. Deleting the plugin removes the key and its settings from that site. Images already in the Media Library belong to the site and stay there.

8. What you are responsible for

• Having the right to use and edit the images you send us, from any of these places.
• Keeping API keys secret. A key spends the credits on your account, so treat it the way you would treat a password and never put one in a public repository or a web page.
• Any webhook endpoint you point us at, including keeping it secure and checking the signature on what arrives.
• The content of a store or a site you connect, and following that platform terms.

9. Payments

Payments are handled by third-party payment processors. We never see or store your full card number. We keep a record of your subscription status, credit balance, and billing history so you can manage your plan and view past charges in your account settings.

10. Cookies and similar technology

We use cookies and similar technologies to keep you signed in, remember your theme and language preference, and understand how the site is used so we can improve it. You can control cookies through your browser settings, though disabling them may affect how the site works. The Public API, the MCP connector, and the plugins do not use cookies.

11. Sharing and legal requests

We do not sell your personal information. We may share information with the service providers who help us run the Service, or when required to comply with a law, regulation, or valid legal request.

12. Your rights

Depending on where you live, you may have the right to access, correct, or delete your personal data, and to opt out of marketing communications. That includes job records from the API, the MCP connector, and the apps. To exercise any of these rights, contact us at support@picverce.com and we will respond as quickly as we can.

13. Children's privacy

Picverce AI is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, contact us and we will remove it.

14. Changes to this policy

We may update this Privacy Policy from time to time. When we make a change, we will update the date at the top of this page. Significant changes will be communicated through the Service or by email.

15. Contact us

Questions about this Privacy Policy? Email support@picverce.com. You may also want to read our Terms of Service or Refund Policy, or contact us directly.