How VizAI handles visitor and integration data.
VizAI collects only the data needed to operate the public gallery, respond to contact requests, and support optional platform integrations.
What we collect
VizAI may process contact details submitted through forms, public gallery interactions, basic technical logs, and optional Pinterest OAuth metadata when an authorized account is connected.
Why we collect it
This data is used to operate vizai.art, maintain the public gallery, respond to support or collaboration requests, and keep optional integrations working correctly.
How Pinterest data is used
Pinterest data is used only after OAuth authorization. VizAI never asks for a Pinterest password. If Pinterest data is displayed or used, it is handled according to the permissions granted by the connected account.
Disconnecting and deletion
A connected Pinterest account can be disconnected from VizAI. Stored integration records can be removed on request unless retention is required for security, audit, or legal reasons.
Cookies and local storage
VizAI may use HTTP-only session cookies for protected areas of the site. No third-party tracking cookies are used. Pinterest OAuth tokens are stored server-side only and are never exposed to the browser.
Data retention
Pinterest OAuth access tokens and refresh tokens are retained until the connected account is disconnected or deletion is requested. Integration metadata used for reporting is retained for up to 90 days unless a longer period is legally required.
Third-party sharing
VizAI does not sell personal data. Pinterest OAuth data is not sold, shared, or transferred to third parties and is used only to operate the connected integration on vizai.art.
Your rights
You have the right to access, correct, or request deletion of any personal data processed by VizAI. To exercise these rights, contact admin@vizai.art.
Contact
Questions about privacy, Pinterest integration, or data handling can be sent to admin@vizai.art.
Effective date
This privacy policy is effective as of 20 April 2026. It will be updated to reflect any material changes to data handling practices.