Snapshot 50022
Normalized text
Scripts and page chrome removed; this is what change detection compares.
Privacy Policy Thank you for choosing to be a customer (or a user) of ScreenshotOne (“ScreenshotOne”, “we”, “us”, or “our”). We are committed to protecting your personal information and your right to privacy. If you have any questions or concerns about our policy, or our practices with regards to your personal information, please contact us at [email protected]. ScreenshotOne collects personal data from its users. The user’s acceptance of this privacy policy occurs upon the first interaction with the service via the website screenshotone.com or any of its subdomains. ScreenshotOne’s goal is to ensure that the privacy of your company and that of your customers is protected at the highest level when you use the ScreenshotOne service for rendering screenshots, videos, documents, and more. Data collection We collect the following data: Your email address, IP address, and browser information for authentication purposes. Your email and associated product usage data for product analytics and improving the service. Your history of screenshot requests except for cookies and proxy parameters specified in the requests. Your payment transactions summary (amount and payment method, not the credit card details). Your company name if you change the ScreenshotOne organization name and it reflects your company name. Google OAuth and Sign in with Google ScreenshotOne offers Google OAuth as an optional way to create, sign in to, or link a ScreenshotOne account. When you choose “Sign in with Google,” ScreenshotOne requests the openid, email, and profile permissions. Depending on the information available in your Google account, we receive your Google account identifier, email address and email verification status, name, and profile image. We do not request access to Gmail, Google Drive, Google Calendar, or other Google product data. We use this information only to: Create, authenticate, and link your ScreenshotOne account. Display basic account information. Secure, maintain, and support your account. We store the Google account identifier and associated account information while your ScreenshotOne account remains active. OAuth tokens associated with authentication may also be stored. We do not use these tokens to access other Google services. We do not sell Google user data or use it to train artificial intelligence or machine-learning models. We share it only with the service providers listed in the Third-party providers section when necessary to operate, secure, or support ScreenshotOne, or when required by law. You can revoke ScreenshotOne’s access from your Google Account settings. Revoking access prevents future access but does not automatically delete information already stored in your ScreenshotOne account. To remove that information, delete your ScreenshotOne account or contact [email protected]. ScreenshotOne’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Storing generated content ScreenshotOne doesn’t store the generated content persistently (screenshots, videos, PDFs, HTML, Markdown, and more): If you don’t use caching. When you set cache=true in your API request, the rendered content is cached for the duration specified by cache_ttl (default 4 hours, maximum 30 days). Learn more about caching. Do not set cache=true if you do not want to store the generated content. If you don’t use any permanent storage. When you set store=true in your API request or similar storage options, the rendered content is uploaded to your configured S3-compatible storage. Learn more about storage. Do not set store=true if you do not want to store the generated content. When you use the default response_type=by_format without caching or storage options: 3.1. The screenshot is rendered and returned directly to the requestor without being stored persistently on the ScreenshotOne servers. 3.2. No copy is stored persistently on the ScreenshotOne servers. 3.3. Only the request metadata (URL, parameters excluding cookies and proxy details) is logged for analytics, service improvement, and debugging and your needs. Important note: During processing, rendered content may be temporarily stored to pass through internal system components (such as queues, message brokers, or temporary buffers). This approach ensures that your rendered content and if it contains your users data remain private by default. Third-party providers A list of third-party providers used by ScreenshotOne, links to their privacy policies, and why and how they are integrated into the ScreenshotOne service and used: For a more compact operational list, see Third-Party Providers. Crisp Crisp is used to answering questions instantly and allows you to message me immediately. When you sign in to the site, I share your email with the Crisp widget to send you replies if I amn’t available. Crisp: Privacy Policy DigitalOcean DigitalOcean is for hosting internal API management software, dashboard application, and database. Also for rendering screenshots. All the data is stored in the managed database on DigitalOcean servers. The servers are located in the United States. DigitalOcean: Privacy Policy. Google Cloud Google Cloud for running headless browsers at scale. The servers are located in the United States. Google Cloud: Privacy Policy Pirsch Analytics Pirsch Analytics is used for basic website analytics. It is cookie-free, GDPR-compliant analytics product that doesn’t require a consent form. Pirsch Analytics: Privacy Policy The servers are located in the United States. Cloudflare Cloudflare for proxying all requests to API, caching, and storage for rendered images. The servers are located in the United States. Cloudflare: Privacy Policy PostHog PostHog is used for product analytics. The servers are located in the European Union. PostHog: Privacy Policy Grafana Cloud Grafana Cloud is used for storing the ScreenshotOne logs and metrics. Cookies and proxy parameters you send are exempted from the logs—they are removed before even logging. Grafana Cloud: Privacy Policy Tolt Tolt is used for the ScreenshotOne referral program. Your email and payments are sent to Tolt if you subscribed through one of the ScreenshotOne affiliate partners. It is done to track affiliate commissions only. Tolt: Privacy Policy Better Stack Better Stack is used for monitoring the status of the ScreenshotOne services. No data is shared at all with them. Better Stack: Privacy Policy Hetzner Hetzner is used for hosting the ScreenshotOne services. The servers are located within the European Union. Hetzner: Privacy Policy Paddle Paddle is used for processing payments. Your credit card information is not stored, nor logged on our servers. It is all processed by Paddle. Paddle: Privacy Policy DPA and subprocessors If you need a data processing agreement, see Data Processing Addendum, which is available on request. For the current operational list of providers used in connection with the service, see Third-Party Providers. GDPR compliance Under the General Data Protection Regulation (GDPR), you have certain rights with respect to your data, including the right to request access, rectification, erasure, restriction of processing, data portability, and the right to object to processing. You may exercise these rights by contacting me using the contact information provided below. ScreenshotOne is not yet compliant with the GDPR. Security Check out our security compliance more details. Updates to the policy From time to time, the policy might be updated. The latest version is always at https://screenshotone.com/privacy-policy/. This policy was last updated on September 20, 2026. Contact Contact us if you have any questions, issues, or specific requests.