Privacy Policy
This Privacy Policy explains how Polyer ("Polyer", "we" or "us") collects, uses and shares personal data when you visit https://polyer.io or use the Polyer console, API and hosting services (the "Services"). Terms not defined here have the meanings given in our Terms of Service.
Summary
- We collect what we need to run your account and your applications: your sign-in details, the content and configuration you give us, billing records, and technical logs.
- Google sign-in only receives your basic profile and email. GitHub repository access is limited to the repositories you select.
- We do not sell your personal data or show ads. We measure how our website and console are used with analytics that don't use cookies, and with Google Analytics only if you accept analytics cookies.
- Our control plane is hosted in Germany. Your applications run in the region you choose, currently in the United States.
- You can access, correct, export and delete your data. Contact us at help@polyer.io.
Who is responsible for your data
Polyer is the controller of the personal data described in this policy. You can reach us at help@polyer.io for any privacy question or request.
Your applications' users. Applications that you deploy on Polyer may process personal data about their own users, for example in their databases or in request logs that record visitors' IP addresses. For that data, you are the controller and Polyer processes it on your behalf only to provide the Services. If you are a user of an application hosted on Polyer, please contact the operator of that application about your data.
Personal data we collect
Account data. Your email address, name, profile picture (if your sign-in provider shares one), language preference, and whether your email address is verified. If you sign up with a password, we store only a one-way hash of it. If you turn on two-factor authentication or passkeys, we store the information needed to verify them. If you create API keys, we store the information needed to verify and manage them.
Sign-in with Google or GitHub. When you sign in with Google or GitHub, we receive your name, email address, profile picture (if available) and the provider's account identifier. The provider also returns access tokens, which we use only to complete the sign-in and do not store. If an existing Polyer account uses the same verified email address, we link the sign-in method to that account.
- Google sign-in requests only the
openid,emailandprofilepermissions. It does not give us access to your Gmail, Google Drive, contacts or any other Google data. - GitHub sign-in and the GitHub repository connection are separate. Signing in with GitHub does not give us access to your repositories.
Repository connection. If you install the Polyer Deploy GitHub App, you choose which repositories it may access. The app has read-only access to repository contents, metadata, pull requests and checks. We use it to list your repositories and branches, retrieve source code for builds, suggest configuration from example files in your repository, and react to push, pull request and check suite events for deployments. We receive installation identifiers and account information to link the installation to your workspace. We use short-lived installation tokens to access the repositories you selected and do not store them.
Workspace and service data. The content and configuration you provide, such as workspace and project names, members and their roles, invitations, source code, container images, environment variables, domains, volumes, databases, buckets, deployment history, and application and build logs. Environment variables and other secrets are stored encrypted. Other members of your workspace can see this information according to their roles. If you publish a template, the template and your workspace's name are shown publicly. A new workspace is named after the part of your email address before the "@" until you rename it.
Billing data. Your plan, top-up history, balance, usage and charges, spending limits, alerts and automatic top-up settings. Payments are made through Creem, Polar or Stripe, which collect your payment details directly. Depending on the payment method, Stripe may offer cards, Alipay or WeChat Pay. If you save a card for automatic top-up, Stripe stores it, and we keep only Stripe's customer and payment method identifiers and the card brand and last four digits. We do not store full card numbers.
Usage and technical data.
- Records of the compute, memory, storage and network resources your services use, which we need for billing and capacity planning.
- Session records, which include the IP address, browser user agent, and the session's creation and expiry times.
- Security events, such as sign-ins, failed sign-in attempts, two-factor and password changes, and account deletion requests, together with the IP address and user agent involved.
- An activity history of changes made in your workspaces.
- Server logs that we use to operate and protect the Services.
- Analytics data about how you use our website and console, such as the pages you view, the actions you take (for example clicking sign-up, deployment or top-up buttons), the referring site, your browser, operating system and device type, and your approximate country. See "Analytics" below.
Referrals. If you arrive through a referral link, your browser stores the referral code, and we record which account referred yours so that we can apply referral credit.
Communications. Emails you send us, such as support requests and abuse reports, and our replies. We send you service emails, such as sign-in, verification, deployment, billing and security notices. We do not send marketing emails.
We do not ask for sensitive data such as health, biometric or government ID information. Please do not put such data in support requests.
How we use personal data and why
| Purpose | Legal basis (where the GDPR applies) |
|---|---|
| Creating and managing your account, signing you in, managing workspaces and members | Performance of our contract with you |
| Building, deploying, running and backing up your services | Performance of our contract with you |
| Calculating usage, charging your credit, applying referral credit and keeping billing records | Performance of our contract; legal obligations such as tax and accounting |
| Sending service emails, such as sign-in, deployment, billing, security and service notices | Performance of our contract; our legitimate interest in keeping you informed |
| Answering your requests and providing support | Performance of our contract; our legitimate interest in helping our users |
| Preventing fraud, abuse and security incidents, and enforcing our Terms and Acceptable Use Policy | Our legitimate interest in protecting the Services, our users and third parties; legal obligations |
| Operating, troubleshooting and improving the Services, using aggregated or de-identified data where possible | Our legitimate interest in providing reliable Services |
| Measuring how our website and console are used | Our legitimate interest in improving the Services, for analytics that don't use cookies; your consent, for Google Analytics |
| Complying with the law and responding to lawful requests from authorities | Legal obligations |
We do not use your personal data for advertising. We do not make automated decisions that have legal or similarly significant effects on you, except for automatic limits that suspend a workspace when its credit or spending limit is reached, as described in our Terms of Service.
Google user data. Polyer's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google sign-in data only to sign you in and maintain your account.
How we share personal data
We do not sell or rent personal data. We share it only as follows:
Service providers. We use the following providers to run the Services. They process personal data on our behalf, only as needed to provide their services:
| Provider | Purpose |
|---|---|
| Data center and server providers in Germany, the United States and the other countries where our regions are located | Hosting the control plane and the regions where your services run |
| Cloudflare | DNS, network protection and connectivity for our console and API, email routing, encrypted backup storage, and web analytics that don't use cookies |
| Google Analytics, only if you accept analytics cookies | |
| Plunk | Sending service emails |
| Creem | Merchant of record for payments made through Creem: payment processing, tax calculation and invoicing |
| Polar | Merchant of record for payments made through Polar: payment processing, tax calculation and invoicing |
| Stripe | Payment processing and saved payment methods for payments made through Stripe |
Sign-in and repository providers. Google and GitHub process the information you submit to them under their own privacy policies. We exchange data with them when you sign in or connect a repository.
Integrations you configure. If you set up webhooks or notifications to services such as Slack, Discord, Feishu, DingTalk or WeCom, we send the event data you selected to them.
Other users. Members of your workspace can see workspace data according to their roles. Published templates and the workspace name shown with them are public.
Legal and safety. We may disclose personal data if we believe in good faith that the law requires it, or that it is needed to protect the rights, property or safety of Polyer, our users or others, including to investigate and prevent fraud, abuse and security incidents.
Business transfers. If Polyer is involved in a reorganization, merger, acquisition or sale of assets, personal data may be transferred as part of that transaction, subject to this policy.
Analytics
We use the following tools to understand how our website and console are used and to improve them:
- Umami, which we host ourselves on a server in Germany. It does not use cookies or store IP addresses. It records the pages you view and actions such as clicking sign-up, deployment or top-up buttons, together with the referring site, browser, operating system, device type and country.
- Cloudflare Web Analytics, provided by Cloudflare. It does not use cookies, and it measures page views and page performance in aggregate.
- Google Analytics, provided by Google. We load it only after you accept analytics cookies. It sets cookies and receives the same kind of usage data. Google uses your IP address to estimate your location and does not store it. We have turned off Google signals and ad personalization, and we do not let Google use this data for its own purposes. Google Analytics data is kept for 14 months.
We do not send your name, email address or the content of your services to these tools. You can change your choice at any time with "Cookie settings" at the bottom of our website. If you reject analytics cookies, Google Analytics stops and its cookies are removed.
Where data is stored and international transfers
The Polyer control plane, which stores account, workspace, billing and configuration data, is hosted in Germany. Your applications, volumes, databases and buckets run in the region you choose for each service, and their data is stored and processed in that region's country. Our regions are currently located in the United States. We plan to add regions in the Netherlands, Germany, France and Singapore, and the console shows which regions are available when you create a service. Encrypted backups are stored with Cloudflare.
Some of our service providers, such as Cloudflare, Stripe, Google and GitHub, may also process data in the United States or other countries. Where the GDPR applies and personal data is transferred to a country outside the EU or EEA that does not have an adequacy decision, we rely on appropriate safeguards, such as the European Commission's Standard Contractual Clauses or the recipient's certification under the EU-U.S. Data Privacy Framework.
Free allowance eligibility records
To prevent repeated claims, we may retain minimal eligibility digests of verified identities and original grant records after account closure. These are pseudonymous anti-abuse records, not public identity information, and contain no passwords or third-party access tokens. We retain them only as needed to prevent repeat claims; closing an account does not create another trial entitlement.
How long we keep data
We keep personal data only for as long as we need it for the purposes described above. Current retention periods are:
| Data | Retention |
|---|---|
| Account data | While your account exists |
| Workspace and service data | Until you delete it, delete the workspace, or your account is closed. Data of workspaces that remain suspended for a long period may be deleted, as described in our Terms of Service |
| Sessions | Up to 30 days of inactivity, or until you sign out |
| Security events | 180 days |
| Workspace activity history | 90 days |
| Application runtime logs | 7 days on the Hobby plan, 30 days on the Pro plan |
| Build and deployment logs | 30 days |
| HTTP request logs of your applications | 3 days |
| Detailed usage records | 180 days after they are billed |
| Billing records (top-ups, charges, balances) | As long as required by tax and accounting law, including after your account is closed |
| Platform backups | Up to about 60 days, on a rolling basis |
When you delete your account, we delete your profile, sign-in methods, sessions, API keys and passkeys, delete the projects in workspaces you own alone, end your workspace memberships, and remove your email address from activity records. We keep the billing records of those workspaces as described above. Payment providers keep their own records under their own policies.
Container images built for your services can remain in the region's internal image registry after the services are deleted, until they are cleaned up. They are not accessible to other users.
Deleted data can remain in our encrypted backups until those backups expire. We do not restore deleted data from backups except to recover from a failure.
We may keep data longer when needed to resolve disputes, enforce our agreements or meet legal obligations, and we may keep aggregated or de-identified data that no longer identifies you.
Cookies and local storage
We use only cookies that are necessary for the Services to work. These include the session cookie that keeps you signed in, and short-lived cookies used during sign-in, two-factor authentication and passkey verification. If you choose to trust a device during two-factor authentication, a cookie remembers that choice.
If you accept analytics cookies, Google Analytics sets cookies named _ga and _ga_<ID>, which last up to two years, to tell visitors apart. They are not set unless you accept them.
The console also uses your browser's local storage to remember preferences, such as your language, theme, last-used workspace and analytics cookie choice, and a referral code if you arrived through a referral link.
We do not use advertising cookies. Cloudflare, which protects our console and API, may set strictly necessary cookies for security. Payment pages hosted by Creem, Polar or Stripe may set their own cookies under their own policies.
You can block or delete cookies in your browser settings, but you will not be able to sign in without the session cookie.
Security
We protect personal data with technical and organizational measures appropriate to the risk, including encryption in transit, encryption of environment variables and other secrets, encrypted backups, access controls, two-factor authentication for administrators, logging of administrative actions, and isolation between customer workloads. No method of transmission or storage is completely secure. Please protect your sign-in methods, and tell us at help@polyer.io if you suspect unauthorized access.
Your rights and choices
You can view and update your profile and manage sign-in methods, passkeys, two-factor authentication and API keys in account settings, and you can delete your account through the account deletion flow there. If you are the only owner of a workspace that has other members, you must make another member an owner, or remove the members, before you delete your account.
To revoke Google sign-in access, use your Google Account's third-party connection settings. To revoke repository access, change or uninstall the Polyer Deploy GitHub App on GitHub. Revoking provider access does not delete your Polyer account.
Depending on where you live, including in the EU, the EEA, the UK and Switzerland, you may have the right to:
- access the personal data we hold about you and get a copy of it;
- correct inaccurate or incomplete data;
- delete your data;
- receive your data in a portable, machine-readable format;
- object to processing based on our legitimate interests;
- restrict processing in certain circumstances; and
- withdraw consent where we rely on it.
To exercise these rights, email help@polyer.io. We may ask you to verify your identity, and we will respond within the time required by law. Some requests may be limited where we need to keep data for legal reasons or where fulfilling them would affect the rights of others; if so, we will explain why.
If you are in the EU or EEA, you also have the right to lodge a complaint with your local data protection authority. A list is available from the European Data Protection Board.
Children
The Services are not intended for anyone under 16. We do not knowingly collect personal data from children under 16. If you believe a child has given us personal data, contact us at help@polyer.io and we will delete it.
Changes to this policy
We may update this Privacy Policy from time to time. We will post the updated version on this page with a new "Last updated" date, and we will notify you by email or through the Services before material changes take effect.
Contact
For privacy questions and requests: help@polyer.io