Privacy policy
Last updated: November 16, 2026
Effective date: 16 November 2026 · Version: 1.1
1. Who we are and what this policy covers
1.1 E.M. Coperato Ltd., company number 514961523, of 26 Ba'alei Melacha Street, Haifa, Israel ("TunnelYard", "we") provides dedicated IPsec VPN servers and a dashboard to manage them. Contact us about privacy at privacy@tunnelyard.com.
1.2 We have not appointed a data protection officer. Send privacy questions and requests to privacy@tunnelyard.com.
1.3 Where we are the controller. We decide how personal data is used when you visit https://tunnelyard.com, send the contact form, hold an account or team seat at app.tunnelyard.com, pay us, or contact support. Sections 2 to 7 describe this.
1.4 Where we are a processor. Our customers use their servers to connect offices and remote users. Data about those remote users and their connections is processed by us only on the customer's instructions, under our Data Processing Addendum. The customer is the controller.
1.5 If your organisation gave you VPN access. You are a remote user of one of our customers. That organisation decides who gets access, what is logged and for how long. Contact it first with questions or requests. We will pass on any request we receive.
1.6 This policy does not cover the networks or firewalls that connect to a TunnelYard server. Their operators have their own policies.
2. Data we handle
2.1 Data we control. We collect the following about visitors, account holders and team members.
| Category | Examples | Source |
|---|---|---|
| Account and team data | Name, work email, password hash, organisation, role, workspaces you can access | You, your account admin |
| Billing data | Plan, number of servers, invoices, billing address, VAT ID, and the wallet address and transaction ID of a USDT payment. Card details are held by Tranzila, not by us | You, payment processor |
| Dashboard activity | Sign-in times, IP address, browser, actions taken in the dashboard (audit log) | Dashboard |
| Contact and support | Name, email, company, topic and message from the contact form, support emails | You |
| Live chat | Messages, and any name, email or files you send in the chat; IP address, browser, approximate location and the page you were on when you opened it | You, your browser |
| Alert recipients | Email addresses that receive tunnel-down alerts | You |
| Website data | IP address, browser type and pages requested in server logs; essential cookies | Your browser |
| Website usage (only if you accept analytics cookies) | Pages visited, how you arrived at the site, buttons used, device and browser type, approximate location, and an online identifier set by Google Analytics | Your browser, Google Analytics |
2.2 Data we process for customers. Each customer's servers hold the following, which we handle as a processor.
| Category | Examples |
|---|---|
| Remote user records | Username, authentication method, certificate, networks the user may reach, status |
| Connection records | Device public IP address, assigned tunnel address, connect and disconnect times, traffic volume |
| Tunnel configuration | Peer gateway IP addresses and identifiers, subnets, proposals, pre-shared keys, certificates |
| Server logs | Technical events such as tunnel up and down and configuration errors |
| Traffic in transit | Decrypted on the customer's server to be forwarded, as IPsec requires |
2.3 Traffic content. We do not inspect, capture or store the content of traffic that passes through a server, and we do not log the destinations users visit or their DNS queries. We block some kinds of traffic, such as peer-to-peer and torrent traffic, using rules that do not inspect content.
2.4 Secrets. Pre-shared keys, private keys and remote user credentials are stored encrypted in our database and used only to run the customer's server and produce its configuration exports. Our staff cannot read them, and customers can rotate them at any time.
2.5 Sensitive data. We do not ask for special-category data such as health or biometric data. Please do not put it in forms or support messages.
2.6 Required data. Account and billing data are needed to provide the service. Without them we cannot open or bill an account.
3. How we use data and why
We use the data we control only for the purposes below. The legal-basis column applies where the GDPR or UK GDPR governs.
| Purpose | Data used | Legal basis |
|---|---|---|
| Open and run your account, launch and manage servers | Account and team, dashboard activity | Contract |
| Take payment, send invoices, keep tax records | Billing | Contract, legal obligation |
| Answer contact-form and support requests | Contact and support, account | Contract, legitimate interests |
| Answer your questions in the live chat, before or after you sign up | Live chat | Steps you ask us to take before entering into a contract, legitimate interests in answering enquiries |
| Send tunnel alerts and service notices | Alert recipients, account | Contract |
| Keep the platform secure, prevent abuse and fraud | Dashboard activity, website data | Legitimate interests |
| Understand how the website is used, and improve it | Website usage | Consent. You can withdraw it at any time with "Cookie settings" on the website |
| Fix faults and improve the service | Dashboard activity, aggregated usage | Legitimate interests |
| Send product news by email | Account | Consent. We send marketing only if you agreed, and you can withdraw in every email |
| Comply with law and respond to lawful requests | Any relevant data | Legal obligation |
3.1 Customer data. We use the data in section 2.2 only to run the customer's servers, show status and logs in the dashboard, give support the customer asks for, and keep the platform secure. We may also handle abuse complaints about a server's IP address.
3.2 We do not sell personal data or share it for advertising.
3.3 We do not make decisions with legal or similarly significant effects by automated means alone.
3.4 We do not use customer data to train machine-learning models.
4. Who we share data with and where it is held
4.1 Service providers. We use vendors that process data on our instructions under contract. For security reasons we do not publish the names of our infrastructure providers. Business customers can ask for them under the Data Processing Addendum.
| Service | Data | Location |
|---|---|---|
| Server hosting providers | Customer data in section 2.2 | The region the customer chose |
| Dashboard, database and backup hosting | All categories | Frankfurt, Germany |
| Card payments (Tranzila) | Billing | Israel |
| Invoicing (iCount) | Billing | Israel |
| Email delivery provider | Email addresses and the content of alerts and account messages | European Union |
| Website analytics (Google Analytics) | Website usage in section 2.1 | Google Ireland Limited and Google LLC; may be processed in the United States |
| Live chat (tawk.to) | Live chat data in section 2.1 | [TAWK.TO DATA LOCATION] |
4.2 Server regions. Each server runs in the region the customer picks from those offered in the dashboard, and traffic is processed in that region. Server configuration and technical logs, such as tunnel up and down events and configuration errors, are also stored centrally in Frankfurt, Germany, so the dashboard can show them.
4.3 Your organisation. Account admins and team members can see the remote users, connection records and logs of the workspaces they can access. If a managed service provider runs your organisation's server, its engineers can see them too.
4.4 Legal and safety. We disclose data where the law requires it, or where needed to protect rights, safety or the security of the platform. We review each request and share the minimum required. Where the request concerns a customer's data and the law allows, we tell the customer first.
4.5 Business transfers. If we merge, are acquired or sell assets, personal data may pass to the successor under this policy. We will tell you before that happens.
4.6 International transfers. We are based in Israel, and personal data may be processed in Israel, the European Union, the regions where customers run their servers, the United States for website analytics and, for the live chat, [TAWK.TO DATA LOCATION]. We transfer personal data to other countries only in accordance with applicable data protection laws. Where required, we put appropriate safeguards in place, such as approved contractual clauses or another transfer mechanism recognised by law. Contact privacy@tunnelyard.com for details.
5. How long we keep data and how we protect it
We keep personal data only as long as the purpose needs it.
| Data | Kept for |
|---|---|
| Account and team data | Life of the account, then deleted when it is closed |
| Billing records | 7 years, or the period tax law requires |
| Dashboard audit log | 24 months |
| Website server logs | 7 days |
| Website usage data in Google Analytics | 14 months |
| Tunnel and server logs, connection records | The log retention period of the customer's plan, and in any case deleted when the server is deleted |
| Server configuration, keys and remote user records | Until the customer deletes them. All are deleted as soon as the server is deleted |
| Contact-form, live chat and support messages | 2 years after the conversation closes |
5.1 Security. Every server is a dedicated, single-tenant instance, so one customer's tunnels and keys are not shared with another. Dashboard sign-in uses email and password and supports two-factor authentication. Keys and credentials are stored encrypted, and team members' actions are recorded in an audit log. We apply further technical and organisational measures suited to the risk. We do not publish their details, for security reasons.
5.2 Your part. No system is fully secure. Customers choose their own cipher suites, keys and access rules, and are responsible for them and for keeping dashboard credentials safe.
5.3 Breach notice. If a breach is likely to put your rights at risk, we notify you and the competent regulator as the law requires. Where the breach affects customer data, we notify the customer without undue delay.
6. Your rights
6.1 Depending on where you live, you can ask us to:
- confirm whether we hold your data and give you a copy;
- correct data that is wrong or incomplete;
- delete your data;
- restrict or object to our use of it, including for direct marketing;
- send your data to you or another provider in a portable format;
- withdraw consent at any time, without affecting earlier processing.
6.2 How to ask. Write to privacy@tunnelyard.com or use the dashboard. We may ask you to verify your identity. We answer within one month, or the period your local law sets. Requests are free unless clearly unfounded or excessive.
6.3 EEA, UK and Switzerland. You may complain to your local data protection authority. We would welcome the chance to resolve your concern first.
6.4 Israel. Under the Privacy Protection Law, 5741-1981, you may review the data we hold about you and ask us to correct or delete data that is inaccurate, incomplete or out of date. You are not legally required to give us your data, but we cannot provide the service without account and billing details. You may complain to the Privacy Protection Authority.
6.5 Marketing. Use the unsubscribe link in any marketing email. Service notices will still reach you.
7. Cookies, children, changes and contact
7.1 Cookies. The website and dashboard use essential cookies. They keep you signed in and keep the site and contact form working and secure, and they need no consent. If you open the live chat, our chat provider tawk.to also places its own cookies. If you accept analytics cookies in the cookie notice, Google Analytics places its own cookies too; you can change that choice at any time with "Cookie settings". We use no advertising cookies. Our Cookie Policy at https://tunnelyard.com/cookies gives the details.
7.2 Security filtering. We filter incoming traffic to the website and dashboard to detect and block intrusions and other malicious activity. This processes IP addresses and request data. We run this filtering ourselves, and no outside service receives this data.
7.3 Children. The service is for businesses. It is not directed at anyone under 18, and we do not knowingly collect their data.
7.4 Changes. We may update this policy. We post the new version at https://tunnelyard.com/privacy with a new effective date. We give notice by email or in the dashboard before material changes take effect.
7.5 Contact. E.M. Coperato Ltd., 26 Ba'alei Melacha Street, Haifa, Israel, privacy@tunnelyard.com, or the form at https://tunnelyard.com/contact.