This policy explains what personal information StaticPear collects, why we collect it, who we share it with, and how long we keep it. "Personal information" means information about a person, such as an email address or an IP address. It is part of the Terms of Service.
In short:
- To run your account we need your email address. If you sign in with Google we also get your name.
- We keep a record of each connection (time, destination host and port, the IP address it resolved to, bytes) for 7 days. We do not record what is inside your traffic.
- We keep a record of which customer held which IP address for up to 13 months, so that we can match an abuse report to a customer.
- Some records we must keep for longer; see sections 7 and 10.
- Stripe handles payments. We do not receive your full card number.
- We do not sell personal information. There are no advertising or tracking cookies, and no analytics service, on our website or dashboard.
- Email support@staticpair.com to see, correct or delete your information. We delete it within 30 days after you ask us to delete it.
1. Who we are
StaticPear is a service of GitView LLC, an Illinois limited liability company ("we", "us"). We decide how and why the personal information described here is used. You can reach us at support@staticpair.com.
2. What we collect, and why
| What | Where it comes from | Why we use it |
|---|---|---|
| Account details: your email address; your name, if Google shares it; and the ID that Google uses for you | You, and Google if you choose to sign in with it | To create your account, sign you in, and contact you |
| Terms acceptance records: which version of the Terms of Service you agreed to, when, and the IP address and browser type you agreed from | Your browser | To keep a record that you agreed to the Terms |
| Sign-in codes: stored only as a one-way hash, with a count of wrong guesses | Our systems | To keep sign-in secure |
| Billing details: your Stripe customer and subscription IDs, your plan, payment status, invoices and refunds. Card details are entered on Stripe's page and we do not receive the full card number | Stripe | To take payment, give refunds, and keep financial records |
| Proxy login: your username and password. The password is stored encrypted so that your dashboard can show it to you. The proxy servers hold only a one-way hash of it | Our systems | To check your proxy connections |
| Approved hostnames | You | To limit the proxy to the hosts you chose, and to prevent abuse |
| Connection records: for each connection, the time, the method, the destination host and port, the IP address it resolved to, the status, bytes sent and received, and how long it lasted. Query strings are stripped | Our proxy servers | To enforce your data allowance, keep the service secure, investigate abuse, and fix problems |
| Pair assignment history: which customer account held which IP address, and from when to when | Our systems | To match an abuse report or legal request about one of our IP addresses to the customer who held it, and, while your account is open, to answer billing questions. |
| Website and dashboard logs: your IP address, the time, the page you asked for and your browser type. We leave sign-in requests out of the web server log | Your browser | To keep the site secure and fix problems |
| Messages to us: emails to support@ and abuse@, and what is in them | You | To reply, and to keep a record |
| Abuse reports about our IPs: the report and any personal information in it | The person who reports | To investigate and act (see the Acceptable Use Policy) |
If you sign in with Google we ask for your email address and basic profile (openid, email and profile). We use what Google returns once, to find or create your account. We keep the fields in the table above and we do not keep the access token.
3. What we do not collect
- The content of your traffic. The proxy passes encrypted connections to the host you approved. We do not decrypt them. We do not record web addresses beyond the host name, headers, cookies or message bodies.
- Tracking data. Our website does not set cookies of its own, load scripts, fonts or images from other companies, or send analytics events to any service. Our dashboard does not either, apart from the cookies in section 9. Cloudflare, which sits in front of both, may set strictly necessary security cookies (see section 9).
4. How we use information
We use personal information to:
- provide the service, sign you in, and check proxy logins;
- take payments and give refunds;
- send you service emails: sign-in codes, usage warnings (when available), a notice if we slow or suspend your proxy for heavy use, billing, cancellation and refund messages, and security notices. Stripe also emails you when a payment fails;
- measure your data allowance and apply the limits in the Terms of Service;
- keep the service secure, and detect, investigate and stop abuse;
- answer your questions; and
- meet our legal duties.
We do not sell personal information. We do not use it for advertising, and we do not share it with advertisers.
5. Who we share it with
We use these companies to run the service. They handle information for us, under their own terms and privacy policies as well as ours.
| Company | What it does for us | What it handles |
|---|---|---|
| Amazon Web Services (AWS) | Runs our proxy servers and IP addresses, and stores our proxy logs | Your encrypted traffic as it passes through the proxy, connection records |
| Hetzner | Hosts our website, dashboard and account database in Germany | Account details, billing references, proxy logins, approved hostnames, web logs |
| Cloudflare | Runs our DNS, sits in front of our website and dashboard, and forwards inbound mail sent to support@ and abuse@ to our Google Workspace mailbox (Email Routing). It does not store those messages | Visitor IP addresses and requests to our website and dashboard, and the emails you send to us |
| Google (Workspace) | Hosts our team inbox (Gmail) | Mail sent to support@ and abuse@ is delivered and stored there |
| Stripe | Takes payments, refunds, invoices and the customer portal, and emails you when a payment fails | Your email, your name, your payment details, the billing details Stripe asks for, and your payment history. Stripe also acts under its own privacy policy |
| Mailgun (US) | Sends our outbound email, with tracking turned off | Your email address and the content of the emails we send you |
| Google (sign-in) | Only if you choose to sign in with Google | The sign-in request, and the profile data described in section 2 |
Cloudflare Email Routing forwards inbound mail to our support@ and abuse@ addresses on to our Google Workspace mailbox; Cloudflare does not store it. Traffic you send through the proxy does not pass through Cloudflare.
We may also share information:
- when the law requires it, for example for a court order or other valid legal request, or when we believe in good faith that we need to in order to protect people, our providers or our service;
- to deal with abuse, with the person who reported it, the service that was affected, our providers, or the authorities, and no more than is needed (see the Acceptable Use Policy);
- in a sale or reorganization of our business, with the new owner, who must respect this policy; and
- with your consent, or when you ask us to.
6. Where information is processed
We are based in the United States. Our proxy servers are in the United States. Our website, dashboard and account database are hosted by Hetzner in Germany. Some providers handle information in other countries too. By using the service you understand that your information may be processed in the United States and elsewhere.
7. How long we keep it
These are the longest periods we keep each kind of record. Some are deleted by our systems automatically and some by our team on a regular schedule. We may keep a particular record longer while we deal with an investigation, a legal request or a dispute, and then we delete it.
| Information | How long |
|---|---|
| Account details | Until you ask us to delete them. Closing your account does not delete them. We delete them within 30 days after you ask us to delete them. The exceptions are the pair assignment history (up to 13 months), billing and tax records, and records tied to an investigation or a legal request. The rows below give the periods that apply. |
| Terms acceptance records | Until we delete your account details (see above) |
| Sign-in codes | They expire after 10 minutes. We clear out old ones after about a day |
| Sign-in cookies | 30 days, or until you sign out in that browser |
| Proxy login and approved hostnames | The login stops working as soon as your service ends. We keep both until you ask us to delete them, and delete them within 30 days after you ask us to delete them |
| Connection records | 7 days |
| Total traffic per proxy pair, to detect abuse | Up to 15 months |
| Pair assignment history (which customer held which IP address, and when) | Up to 13 months after the assignment ends, even if you have closed your account or asked us to delete your data. We keep only the IP address, the start and end times, and the account ID and email address needed to identify who held it. We use it only to answer abuse reports and legal requests about that address, and then delete it. |
| Website, dashboard and security logs | 30 days |
| Billing and tax records | As long as tax and accounting rules require. We expect that to be up to 7 years. Stripe keeps its own records under its own policy |
| Messages to support@ and abuse@, and abuse reports | Kept as long as needed to handle support and abuse |
8. How we protect it
We take reasonable steps to protect personal information:
- The dashboard and the proxy use encrypted (TLS) connections.
- Sign-in uses a one-time code that expires after 10 minutes and works once. A code stops working after 5 wrong guesses. Signing in needs no password.
- Your sign-in cookie is signed, and your browser sends it over secure connections only.
- The proxy needs your username and password, and its servers hold only a one-way hash of your password.
- We limit access to personal information to the staff and the automated systems that need it to run the service.
No system is completely secure. If we learn that a security incident has affected your personal information, we will tell you without unreasonable delay, and as the law requires.
9. Cookies
The dashboard uses two cookies, and both are needed for it to work:
sp_sessionkeeps you signed in. It is signed, readable only by the server and not by scripts on the page, sent only over secure connections, and lasts 30 days.sp_oauth_stateis set only while you sign in with Google. It lasts 10 minutes.
We do not use advertising, analytics or tracking cookies. Cloudflare sits in front of our website and dashboard and may set its own strictly necessary security cookies, depending on how it is set up.
10. Your choices and rights
You can email support@staticpair.com to:
- ask what personal information we hold about you;
- correct it; or
- ask us to delete it.
We reply within 30 days. We delete your information within 30 days after you ask us to delete it. To protect you, we may ask you to confirm the request from the email address on your account. We cannot delete records that we have to keep: the pair assignment history (up to 13 months), billing and tax records, and records tied to an investigation or a legal request. Messages to support@staticpair.com and abuse@staticpair.com and abuse reports are kept as long as needed to handle support and abuse. Depending on where you live, you may have more rights, for example in California or the European Economic Area. Tell us where you live and we will follow the rights that apply to you. You cannot opt out of service emails while you have an account, because they carry sign-in codes and billing and security notices.
11. Children
StaticPear is for adults and businesses. You must be at least 18 to use it, and we do not knowingly collect information from children.
12. Changes to this policy
We may change this policy. For a change that matters, we email the address on your account at least 30 days before it takes effect, and we update the date at the top. Section 17 of the Terms of Service applies.
13. Contact
GitView LLC, an Illinois limited liability company. Email support@staticpair.com. To report abuse: abuse@staticpair.com.