Privacy Policy

We collect account information such as your name, email address, profile image, organization membership, and sign-in status through our authentication provider.

We collect the content you choose to provide, including guidance, notes, instructions, uploaded file text, spreadsheet data, selected URLs, selected page titles, built presentations, export metadata, and support attachments.

If you connect Google, we store the Google account email, granted scopes, OAuth tokens, presentation identifiers, Drive file identifiers, slide metadata, and the Google Slides content needed to create, export, insert, edit, or synchronize presentations.

The Chrome extension stores draft source and guidance content, selected URLs and page titles, slide count, recent export state, and a short-lived sign-in token in Chrome local storage so the side panel can preserve your work between opens.

We use this information to authenticate you, preserve your drafts, create presentations, export to Google Slides, insert or edit slides you request, manage credits and billing state, secure the service, debug failures, and respond to support or privacy requests.

Ploxs uses Google API data only to provide or improve user-facing Ploxs features that you request and that are visible in the app, including Google Slides and Google Drive export, insert, edit, and synchronization workflows.

We do not sell user data. We do not use Google API data or other user data for personalized ads, retargeting, creditworthiness, lending, data brokerage, information resale, or training generalized AI or machine learning models.

Ploxs uses Google API data only to provide the Google Slides and Google Drive features you request. Ploxs' use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements.

Humans do not read your Google content except when you ask us to review specific content for support, when required for security or abuse investigation, when required by law, or when the data has been aggregated and anonymized for internal operations.

Ploxs does not use Google API data to train generalized AI or machine learning models. AI model providers may process your content only to generate or edit presentations you request and are not allowed to use your Google API data for their own advertising, profiling, or model training.

We share information with service providers only as needed to operate Ploxs, including authentication, hosting, database and storage, AI model processing, Google APIs, payment processing, and transactional email.

Service providers may use your information only to provide services to Ploxs and are not allowed to use it for unrelated purposes. Google API data is transferred only as needed to provide or improve the user-facing Ploxs features you request, for security, to comply with law, or with your explicit consent as part of a business transaction.

We may disclose information if required by law, to protect users and the service, or as part of a merger, acquisition, financing, or sale of assets with any consent required by applicable law or Google policy.

Ploxs transmits data over HTTPS. Access to production systems is limited to people and systems that need it to operate, secure, and support the product. OAuth token exchanges and Google API calls are handled by server-side systems, not published client-side code.

We keep information while your account, built presentations, connected Google account, support requests, or billing records are active, and longer when needed for security, legal, tax, or operational reasons.

You can disconnect Google from Ploxs settings. When you disconnect Google, we revoke the refresh token when possible, delete stored Google OAuth tokens, and stop new access to your Google account. You may also request account and data deletion.

For privacy requests, account deletion, or questions about this policy, contact privacy@ploxs.com.