Overview

This portal allows authorized users to upload files into Google Drive. Protecting privacy and personal data is important to us. This policy explains what data we collect, why we collect it, and how we handle it.

Data We Collect

• Authentication tokens required to access a connected Google Drive are stored only for the duration necessary to perform uploads and are kept server-side.
• Minimal session information (role) is stored in a signed cookie to enable role-based access (user / admin).
• Uploaded files are sent directly to your Google Drive account and are stored there; this app does not persist file contents locally.
• Portal configuration (clients, campaigns, publications) is stored as JSON in your Vercel blob storage associated with the project.

How We Use Data

We use authentication tokens only to perform Google Drive operations on behalf of an authenticated admin. Session cookies are used solely to maintain role information for the portal. Configuration data powers the UI and is not shared outside of the deployment.

Third-Party Services

This project integrates with Google Drive (Google LLC) and uses Vercel's blob storage. Please review their privacy policies for details about their data handling practices.

Retention and Deletion

Authentication tokens may be revoked by an admin at any time by disconnecting Google Drive or clearing stored session cookies. Uploaded files should be managed directly inside your Google Drive. To remove configuration data, delete the config in the admin panel or reset the configuration in the deployment.

Security

We recommend deploying this project on Vercel and keeping environment variables (OAuth secrets, session secret) safe. Use strong `SESSION_SECRET` values and rotate credentials when needed.

Contact

For privacy questions about this portal, open an issue in the project repository or contact the project owner.