Privacy Policy

Effective: July 2026  ·  Contact: shares@svgslid.es

What svgslid.es does

svgslid.es converts SVG files into Google Slides format. It is available as a web app, a Google Slides add-on, and a Chrome extension. This policy describes, for each surface, exactly what data is accessed, how it is used, whether it is shared, how it is stored and protected, and how long it is retained.

Data accessed

Web app (svgslid.es):

• The SVG files you upload for conversion.
• Your Google account email address, only if you choose to enter it so the output can be shared directly with you.
• Standard web server logs (IP address, timestamp, HTTP status) generated by Google Cloud Run.

Google Slides add-on:

• The current presentation's page dimensions, so converted content is sized to fit — read via presentations.currentonly, which is scoped to the single presentation the add-on is running in and cannot access any other file.
• The SVG files you select from within the dialog.
• No Google Drive access of any kind, and no other content in your presentation is read or modified via the Slides API. The add-on never creates, reads, or deletes any file in your Drive.

OAuth scopes requested by the add-on:

• presentations.currentonly — read the active presentation's page dimensions only, so inserted content is sized correctly. Cannot access any other presentation or file.
• script.external_request — call the svgslid.es backend to convert your selected SVG files.
• script.container.ui — display the add-on's dialog.

Converted shapes are inserted by writing data to your device's own clipboard, which you then paste into the slide yourself (Cmd/Ctrl+V) — this happens entirely in your browser and does not involve any Google API call or server-side write to your presentation or Drive.

Chrome extension:

• The SVG file(s) you drag onto an open Google Slides tab.
• No Google account data of any kind, and no Google OAuth scope is requested — the extension cannot access your Drive, your presentations via the Slides API, or any other Google data.
• Two narrow Chrome permissions only: activeTab (lets the extension's script run on the Slides tab you're actively using — a browser permission, not a Google one) and a single, specific host permission to reach the svgslid.es backend described below.

Data usage

• SVG content is used solely to perform the requested conversion (to PPTX/Slides format for the web app, or to Google Slides' own clipboard format for the add-on and the extension). It is not analyzed, indexed, or used for any purpose other than fulfilling your conversion request.
• Email address (web app, optional) is used only as the recipient address for a one-time Drive sharing permission on the output file.
• Slide dimensions (add-on) are used only to scale and center inserted elements to match your presentation.
• Chrome extension: SVG content is converted to Google Slides' shape format directly in your browser, using an embedded Python-in-WebAssembly runtime — in this (the common) case, your SVG file never leaves your device. Only if that in-browser conversion isn't available yet does the extension send the SVG to the svgslid.es backend for conversion, handled identically to the add-on's request-scoped processing described throughout this policy.
• We do not use any data accessed through Google APIs, or any file you convert, to train or improve machine-learning or AI models, ours or anyone else's.
• We do not build profiles of users or track behavior across sessions.

Data sharing

• We do not sell, rent, or share Google user data with advertisers, data brokers, or any other third party.
• The only data transmitted to a third party is the SVG/PPTX file content sent to Google Cloud Run (our hosting provider) and Google Drive (for the web app's output storage) — both are Google infrastructure, not an external third party. See Third-party services below.
• The web app's output PPTX is shared via Drive's "anyone with the link" viewer permission so you can access it without signing in, plus a direct share to your email if you provided one. It is not made discoverable or indexed, and no one else is given access by us.
• The add-on never creates, shares, or touches any Drive file — the converted result is written only to your device's own clipboard, which never leaves your browser except for the SVG-to-shape-data conversion request described above.
• The Chrome extension behaves the same as the add-on here: the converted result is written directly to your device's own clipboard. It never creates, shares, or touches any Drive file, and never calls any Google API.

Data storage & protection

• Uploaded SVG files are written only to an ephemeral temporary directory on the Cloud Run instance handling your request and are deleted as soon as that request finishes. They are never written to a database or other persistent storage.
• The add-on's /insert-svg-clip endpoint (and the extension's equivalent /insert-svg-clip-at fallback) holds your SVG and the resulting shape data only in memory for the duration of the request; nothing is persisted server-side, and nothing is written to Drive or any other Google service.
• The web app's output PPTX is stored in a single Google Drive folder owned by the service's Google Cloud service account, protected by Google Drive's standard infrastructure security (encryption at rest and in transit) and access controls. Anyone with the share link can view that specific file, per the sharing model described above.
• When the Chrome extension converts a file locally in your browser (the common case), no SVG data is transmitted anywhere at all — it never reaches our servers, so there is nothing for us to store or protect.
• We do not maintain a separate database of user data, so there is no additional data store to secure beyond the Drive folder and Cloud Run's transient request handling.

Data retention & deletion

• Uploaded SVG files and in-progress conversion data are deleted automatically within seconds, as soon as the request that created them completes.
• Output PPTX files in the web app's Drive folder are automatically deleted after 7 days by a scheduled daily cleanup job. To keep a file beyond that window, use Drive's File → Save to Drive → File → Make a copy — the copy belongs entirely to your own Google account and is unaffected by our cleanup.
• The add-on has nothing to retain or delete on our end beyond the transient in-memory conversion request — no file is ever created anywhere by the add-on.
• The Chrome extension has nothing to retain or delete on our end either: local, in-browser conversions never reach our servers at all, and the rare fallback request is handled the same transient, in-memory-only way as the add-on.
• To request deletion of any file, at any time, email shares@svgslid.es with the Drive link or filename — we will delete it promptly, typically within 2 business days. You may also delete any file you were shared with directly from your own Google Drive.

What we do not do

• We do not create user accounts or store personal profiles.
• We do not use cookies or analytics tracking.
• We do not sell, share, or monetise any data.
• We do not use your files to train models or improve any AI system.
• The Chrome extension requests no Google account access or OAuth permission of any kind.

Third-party services

svgslid.es runs on Google Cloud Run (compute) and stores output files in Google Drive. Google's own privacy policy governs their infrastructure. No other third-party services receive your data.

Changes to this policy

If we make material changes, the effective date above will be updated. Continued use of the service after that date constitutes acceptance.

Contact

Questions or requests, including data deletion requests: shares@svgslid.es