Pixel2Vector service policies
Privacy Policy
Effective Date: October 18, 2026
1 Information We Collect
We collect information you provide when you create an account, upload images, or contact us for support.
• Account Information: Name, email address, encrypted password
• Usage Data: Uploaded original images and their embedded metadata, generated vector results, API usage and service preferences
• Technical Data: IP address, browser information, device details for service functionality
2 How We Use Your Information
We use collected information to:
• Provide image vectorization services
• Process uploads, generate vector outputs, and privately archive new originals and results for quality review and model evaluation, improvement and training as described below
• Manage your account and subscription
• Provide customer support
• Send service-related communications
3 Information Sharing
We do not sell your personal information. We may share information only:
• With your consent
• To comply with legal requirements
• With trusted service providers under confidentiality agreements
4 Payment Processing
All payment processing and checkout is handled by Stripe. Stripe processes your payment information securely, and we do not store your full payment details on our servers. Stripe's privacy policy governs the collection and use of payment information during checkout.
5 Data Security
We implement security measures including data encryption, secure transmission (HTTPS), and limited access controls to protect your information. Email/password sign-in and registration use Cloudflare Turnstile to help detect automated abuse. Cloudflare processes browser and network signals for this security check; our server sends the verification token to Cloudflare, not your password or email address.
6 Data Retention
We retain your information as needed to provide services and comply with legal obligations. You may request account deletion at any time.
7 Your Rights
You may access, correct, or request deletion of your personal information. Contact us to exercise these rights.
8 Cookies
We use essential cookies for secure sign-in, request protection and temporary guest-preview ownership. The guest cookie expires after 24 hours and links previews to the same browser during sign-in. We store a hash of its random secret and a hash of the observed network peer for abuse limits; these are pseudonymous security records, not a guarantee of anonymity. Guest images use temporary processing storage and are not enrolled in the model-improvement archive, even after being claimed by an account. Clearing cookies or changing browsers may prevent preview recovery. No optional analytics cookies are enabled by the essential-cookie preference. You can control cookies in your browser.
9 Updates to This Policy
We may update this policy occasionally. We will notify you of material changes via email or service notifications.
10 Contact Information
For privacy questions, contact: [email protected]
We're here to help address any questions about your data.
Browser signals for account security
When enabled, we use the open-source FingerprintJS library after sign-in to derive a browser identifier from browser and device characteristics. Our server stores a keyed hash of that identifier linked to your account, the library version, and first and last observation times. We do not upload the underlying fingerprint components or send usage telemetry to the FingerprintJS provider through this integration. This is for investigating repeated-account and service abuse, not advertising or cross-site tracking.
Authorized administrators can review accounts with matching browser signals alongside their account history. A match is not proof of identity or abuse and does not automatically block an account or remove credits. We keep at most 20 recent browser signals per account, exclude them from review 30 days after their last observation, and delete expired records in hourly cleanup runs. Browser settings may prevent collection; missing signals are not evidence of abuse.
These account-linked hashes are pseudonymous personal data, not anonymous data. Contact [email protected] with questions, objections or requests concerning your security data.
Image retention and model improvement
New images uploaded while signed in to Pixel2Vector and their generated vector results are saved by default in a private archive for quality review, evaluation and development of our vectorization models, including training. This includes the original file and any metadata it contains. Guest-preview uploads use temporary processing storage and are not enrolled in this archive, including after sign-in and claim. There is no per-upload opt-in checkbox for account uploads. Upload only content you have the necessary rights to provide for the applicable purposes; do not upload confidential or sensitive personal information.
Archive copies are losslessly compressed and retained for up to 90 days, separately from your plan's result download window. Results are copied after conversion in the background. Files are not publicly accessible through this archive, and retaining them does not transfer ownership to Pixel2Vector. Historical uploads are not enrolled retroactively.
Archiving does not itself start model training or designate a result as approved training data. Before use in training, files require review for suitability and applicable rights. Contact [email protected] to request deletion or object to model-improvement use, identifying your account and relevant uploads. Requests must be resolved before affected files are used for training. Archive deletion does not itself remove data from previously trained model weights.