PrezGo Logo

Privacy Policy

Last Updated: August 3, 2026

1. Introduction

This Privacy Policy describes the policies and procedures of PrezGo (“PrezGo,” “we,” “us”) regarding the collection, use, and disclosure of your information when you use prezgo.app and related services. PrezGo is designed as a secure, ephemeral presentation generation service, not a data storage or account product for end users. Our fundamental operating principle is the immediate processing of user inputs to generate content, followed by systematic deletion of those inputs after the session ends.

You do not need a PrezGo account to use the core product. Optional features (such as cloud import/export via Google Drive or OneDrive, 24-hour share links, Contact Support, or Report a bug) may collect limited personal information as described below.

2. Data Collection & Processing

PrezGo employs an ephemeral data processing architecture. We collect and process user-supplied text, documents, preferences, and instructions exclusively to generate presentation materials (speaker notes, handouts, slides, and related exports). This data is processed in real time and is not stored in a permanent, user-accessible product archive. If you choose to create a share link, the exported file is stored temporarily (up to 24 hours) so recipients can download it; after expiry the link and file are removed.

  • Processing infrastructure: We use Google Vertex AI (Gemini) to perform natural language processing and content generation.
  • Session identifiers: Your browser is assigned a temporary session ID (stored in session storage) so the API can correlate requests, progress, and technical logs for that visit. Session IDs are not a login account.
  • Session Workspace Hub (Local Browser Storage): Generated speaker notes, slide decks, and handouts are saved in this browser’s IndexedDB (with a small sessionStorage fallback). They stay on this device across refresh and browser restarts until you click “Clear all” in the Session Hub or clear this site’s data. PrezGo does not store these drafts in a server account. On a shared computer, use Clear all before you leave.
  • Temporary media storage: Extracted images and short-lived processing artifacts may be held in Google Cloud Storage with short object lifecycles and signed URLs. These objects are not a permanent library of your files.
  • Prohibition on persistent product storage: Uploaded source files and server-side generated artifacts are retained only as needed for the active generation or revision request. They are not a cloud library.
  • Server-side erasure: Uploaded source files and Cloud Run processing artifacts are removed as part of normal cleanup when the generation request ends. Refreshing the page does not by itself delete Session Hub drafts stored in this browser.
  • Optional cloud import / export (Google Drive, OneDrive): If you choose Import from Google Drive or OneDrive, that provider may show a sign-in and consent screen so your browser can list and download a file you select. If you choose Save to Google Drive or OneDrive from Export, the provider may show consent so your browser can upload the exported file (for example into a PrezGo folder on OneDrive). OAuth tokens stay in your browser for that session; PrezGo does not store your cloud passwords or long-lived cloud credentials on our servers. Imported content is processed ephemerally the same way as a local upload. Your use of Google or Microsoft services is also subject to those providers’ terms and privacy policies.

3. Analytics and Cookies

We use Google Analytics 4 (GA4) on the public website (product app and static pages such as Help, About, Contact, Privacy, Terms, and Reviews) to understand aggregate usage (for example page views and basic interaction events). On the product app this is via Firebase Analytics; static pages load a lightweight gtag script. Analytics is loaded after first paint. GA4 may set or read cookies or similar identifiers, and may collect technical data such as browser type, approximate location derived from IP, device/category information, and referring URLs.

We use this information to improve reliability, performance, and product design—not to sell personal data or to train our generative models on your presentation content. You can limit analytics cookies through your browser settings or industry opt-out tools where available. Blocking cookies may affect measurement but does not prevent core generation features.

4. Contact Support

When you use the Contact Support form (or email [email protected]), we collect the information you provide—typically name, email address, subject, and message—so we can respond. Messages are delivered by email through our email provider (Resend) to our support inbox. We use this data only for support and product improvement related to your request, not for marketing lists.

5. Bug Reports and Diagnostic Data

When you use Report a bug, we collect your email address, a description of the issue, optional severity, product area, page URL/browser metadata, and technical session logs from that session so we can investigate. If you opt in to include session files, we may also receive chat history, document content, preferences, and related session metadata from your browser for that report only.

This material is used only to diagnose and fix bugs and product issues. It is not used for marketing or to train generalized AI models. Report packages may be emailed to support and stored temporarily for investigation (for example object storage). Report attachments and related diagnostics are kept only as long as needed for investigation (typically up to thirty (30) days, or until the issue is resolved plus a short buffer), then deleted. Session files are optional; technical logs may be included with every bug report.

6. Data Retention Policy

Product content: Uploaded source files and server-side processing artifacts are not kept as a permanent archive after the generation request ends.

Local session documents: Presentation drafts in the Session Workspace Hub live only on this device in IndexedDB. They survive refresh and browser restart, have no automatic expiry, and are removed when you click “Clear all” or clear this site’s data. They are not uploaded to a PrezGo account.

Share links: If you create a share link, the exported file and related metadata (for example filename, expiry time, and download counts) may be stored temporarily—typically up to twenty-four (24) hours—so recipients can download the file. After expiry, the link stops working and the file is removed under our storage lifecycle practices.

Operational logs: Structured API and reliability logs (for example in Google Cloud Logging) may be retained for a limited period for security, abuse prevention, cost monitoring, and product diagnostics. These logs may include session IDs, timestamps, error messages, and limited request metadata—not a full permanent copy of your documents by default.

Support and bug reports: Contact messages and bug-report packages are retained only as needed to respond and investigate, as described in sections 4 and 5.

7. Security Measures

We implement industry-standard security practices to protect data integrity and confidentiality during transmission and processing.

SSL / TLS Encryption

Data transmission between your browser, our infrastructure (including Cloud Run), and Google Vertex AI is secured with TLS.

Vertex AI Security

Generation runs on Google Vertex AI. We do not use your presentation inputs to train generalized third-party AI models for unrelated purposes. Google’s cloud terms and data processing terms apply to infrastructure providers we use.

8. Third-Party Service Providers

We rely on trusted processors to run the service. They process data only as needed to provide their services to us:

  • Google Cloud — hosting (Cloud Run), databases and ops state (Cloud SQL), temporary media (Cloud Storage), Vertex AI generation, and Cloud Logging.
  • Firebase / Google Analytics — product analytics (GA4) on the public site.
  • Resend — transactional email for Contact Support and bug-report delivery.
  • Firebase Hosting — delivery of the website static assets.
  • Optional: Google / Microsoft (user-chosen cloud import or export) — if you use Google Drive or OneDrive features, sign-in and file access happen in your browser with that provider. PrezGo does not receive your cloud password; short-lived tokens are handled in the browser as described above.

These providers process data under their own terms and privacy policies. We do not sell your personal information.

9. User Rights

For ordinary product use, uploaded files are not kept as a long-term server archive after the generation request ends. Session Hub drafts remain on this device until you click Clear all or clear site data. Material you submit via Contact Support or a bug report is retained only as described in sections 4–5. To remove local drafts immediately, use Clear all in the Session Hub.

To request deletion of a support message or bug report you submitted, or to ask a privacy-related question, contact [email protected]. Depending on your location, you may have additional rights under applicable law (such as access, correction, or deletion of personal data we still hold). We will respond within a reasonable time.

10. Changes to This Policy

We may update this Privacy Policy from time to time. The “Last Updated” date at the top of this page will change when we do. Continued use of PrezGo after an update constitutes acceptance of the revised policy. Material changes will be reflected on this page at prezgo.app/privacy/.