Last updated: October 13, 2026
Privacy Policy
This policy explains what Snapside processes to create an automatically generated history of how a product was built.
1. Information processed
Snapside processes account information, consent records, connected-tool identifiers and server-side credentials, repository or file metadata, commits, pull requests, releases, selected history events, and security information.
2. Purposes
We use information to authenticate you, connect tools, import and display product history, preserve preferences and consent records, secure the service, and respond to support or legal requests.
3. Figma data
When you connect through Figma OAuth, Snapside processes your account name, email, and profile image, plus the name, link, thumbnail, modification time, version history, page and layer names, structure, layout, styles, and text through depth 6, and file-specific webhook information for individual files you select by URL. When you connect through the Figma plugin, Snapside processes the current file name, Figma display name, and page and layer names, structure, layout, styles, and text through depth 6 when you start a sync, and stores a connection credential in Figma's storage on your device. These limited snapshots are used to compare design changes before and after. Snapside does not browse or index file lists in your Figma team or organization, modify Figma file content, or use Figma data for advertising or AI model training.
4. Google Drive data
When you connect Google Drive, Snapside processes your Google Account name, email, and profile information plus read-only metadata used to provide a folder and file picker. Only for files you select and files inside selected folders, Snapside uses file IDs, names, types, creation and modification times, versions, web links, owners, parent folder IDs, and deletion status to create and display change history and maintain change notifications. Snapside does not download or store file contents and does not create, modify, or delete Google Drive files.
5. Miro data
When you connect Miro, Snapside reads user and team identifiers and the names, descriptions, links, owners, modifiers, and modification times of boards available to you to provide a selection list. Only for boards you explicitly connect, Snapside stores snapshots of supported item types, text and other content, styles, position, size, rotation, and parent item information and compares them with prior states. Snapside does not create, modify, or delete Miro boards or items or use Miro data for advertising or AI model training.
6. Google API Limited Use
Snapside's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Snapside does not sell Google user data or use it for advertising, creditworthiness, or AI model training, and does not transfer it to third parties or permit human access except to provide the user-facing change-history feature, for security, to comply with law, or with the user's explicit consent.
7. Service providers and connected tools
Snapside relies on providers such as Supabase and Vercel and communicates with tools you connect, such as GitHub, Figma, Google Drive, and Miro. Those providers process information under their own terms and privacy policies.
8. Retention and deletion
Account and product-history data are retained while your account is active. Disconnecting an integration deletes that service's stored OAuth credentials, connected-resource metadata, change-notification channels, and product history. Account deletion removes remaining associated records, except information temporarily required for security, dispute resolution, or legal compliance.
9. Your choices and rights
You can update account information and preferences, sign out, disconnect integrations, and delete your account. Depending on your jurisdiction, you may request access, correction, deletion, restriction, or objection.
10. Security
Snapside uses web integration credentials server-side and encrypts them, validates webhook signatures, and uses row-level database policies. No online service can guarantee absolute security.
11. Children
Snapside is intended for professional product-development use and is not directed to children under the minimum digital-consent age in their jurisdiction.
12. Policy changes
When material changes require renewed agreement, Snapside records consent against a new policy version.
13. Contact
Privacy questions and rights requests can be submitted to contact@snapside.io.
Build Updates and video rendering
Generating a Build Update stores the summary, highlights, statistics, social drafts and source-activity links for the selected day in your account. Videos are rendered in your browser; MP4 content is not uploaded to the rendering provider. Remotion receives the site origin, render success, output kind and execution environment for licensing and usage tracking. Project names, activity content and video files are not included in this usage event. Content is not published to external social networks before you choose to share it.
Direct social publishing
Connecting Threads, X, Instagram, LinkedIn, or Reddit stores the account identifier, display name, approved scopes, and encrypted OAuth credentials. Snapside sends a post draft to a network only after you select that destination and press Publish; Instagram also receives the Build Card through a signed URL valid for 15 minutes. We retain the external post ID, URL, timestamp, and any failure reason. Disconnecting deletes stored credentials but does not delete content already published on an external network.
Usage analytics and cookies
Snapside uses Microsoft Clarity to analyze masked page structure, clicks, scrolling, and usage flows. Text in signed-in product screens is masked from Clarity. Google Analytics measures page visits before and after login, screen types, and feature-usage events. Custom feature events do not include project content, project identifiers, names, email addresses, or OAuth credentials. Automatic pageviews may include the URL of the page visited. Advertising storage, advertising user data, and ad-personalization signals remain denied.
Welcome email and optional product updates
After initial signup, we process your email address, selected language, and delivery status to send one welcome email to your signup address through Resend. Product updates are sent only if you separately opt in during signup, and you can withdraw that consent using the unsubscribe link in each email. We delete the related records when you delete your account.
Project notes and issues
We store notes you write, the contents of Markdown files you import, linked timeline and issue references, and issue titles, descriptions, status, priority, assignees and results. This data supports project work, note import and export, and links between related records.
Desktop, local Git and AI work
For local repositories you select, we read commit identifiers, authors, timestamps and titles and sync them to project history. Local folder connection settings stay on your device; the desktop Snapside connection key uses operating-system encrypted storage. When you configure automatic issue runs, the issue title, description and selected working folder are passed to the local Codex or Claude execution tool, and result summaries are stored in issues and the timeline. Data processed by an AI tool is subject to that provider's policies.
Work summary emails and support replies
We process your work summary email preference, email address and project work information. You can change this preference in Settings independently of product-news consent. Support requests store your account email, inquiry content, replies and read status for support email handling and workspace Inbox display. Resend is used for email delivery.