DeckSync is designed to move presentation work from Figma into Google Slides while keeping authentication and payment handling delegated to trusted platform providers.
1. Information DeckSync uses
DeckSync may use the following information to provide Figma to Google Slides conversion and sync:
- Figma current user ID and name for trial status, Pro activation, checkout binding, and deck metadata.
- Google account profile information returned by OAuth, such as email, name, and profile picture, to show connection status.
- App session tokens used to confirm DeckSync Pro status and Google connection state.
- Managed deck metadata, including presentation ID, title, URL, slide count, sync status, and recent deck history.
- Selected Figma frame export data or local PPTX files when you ask DeckSync to create or sync Google Slides.
2. Figma permission
The DeckSync manifest requests Figma `currentuser` permission. This permission supports account-aware trial limits, Paddle subscription activation, and display of your account status inside the plugin.
3. Google OAuth and Google Slides access
DeckSync uses Google OAuth with scopes needed to identify the Google account and create or update files through Google Drive and Google Slides import flows. DeckSync does not collect or store Google passwords. Google refresh tokens are encrypted before storage in Cloudflare KV using AES-GCM, and app session tokens are used by the plugin when calling the Google Slides worker.
4. Paddle checkout
DeckSync uses Paddle for Pro checkout. Payment credentials are handled by Paddle, not by DeckSync. DeckSync receives activation status and stores app session tokens so the plugin can verify Pro access.
5. Figma client storage
DeckSync stores app session tokens, Google connection status, Google account profile data, managed deck metadata, and recent deck metadata in Figma client storage. Disconnecting Google or logging out clears relevant local plugin state.
6. Content processing
When you create or sync a Google Slides deck, DeckSync converts selected Figma frames into a PPTX package or accepts a local PPTX file, then sends that data over HTTPS to the DeckSync Google Slides worker for import into your Google account. DeckSync uses this content to complete the requested conversion or sync action.
7. Network access
DeckSync network access is limited by the Figma manifest to approved HTTPS domains used for authentication, checkout, font/script loading, and Google Slides import. The primary service domains are `www.deck-sync.com` and `google-slides-worker.timori.workers.dev`.
8. Data retention
OAuth sessions are short-lived. App session tokens expire according to the worker configuration. Managed deck metadata and Google connection records may remain while your connection is active so DeckSync can support recent decks and sync workflows.
9. Your controls
You can disconnect Google in the plugin, remove recent deck entries, log out of DeckSync Pro, or revoke Google access from your Google account permissions page. You can also contact support to ask privacy questions about DeckSync.
10. Contact
Privacy questions can be sent to support@deck-sync.com.