Deze privacyverklaring is op dit moment alleen in het Engels beschikbaar. De Nederlandse versie volgt.
1. Who we are and what this statement covers
HyperW is a service of Melya Holding B.V., trading as HyperW (“HyperW”, “we”), established in Papendrecht, the Netherlands, registered with the Dutch Chamber of Commerce (Kamer van Koophandel) under number 51872587.
This statement explains how HyperW processes personal data as controller: data about the people who work with HyperW as a customer, a prospective customer, a partner or an affiliate, about people who start a signup, and about visitors of our own website www.hyperw.net. It is the privacy statement referred to in article 12.5 of the HyperW Subscription Terms.
What this statement does not cover. HyperW personalises the websites and campaign pages of its customers. For the visitors of those pages (and the recipients of a customer’s campaign links) the customer is the controller and HyperW acts as its processor under a data processing agreement. That processing is described in the separate statement for visitors of pages powered by HyperW at https://app.hyperw.net/privacy and in the customer’s own privacy statement. Questions about it can be sent to the customer or to us; we pass them on where needed.
2. Contact
Questions and requests about data protection: privacy@hyperw.net.
Melya Holding B.V., trading as HyperW, Papendrecht, the Netherlands, Chamber of Commerce number 51872587.
HyperW has not appointed a data protection officer. Given the nature and scale of our processing this is not required; we reassess this every year and as our service grows.
3. What we process, why, on which basis and for how long
For each category below: the data, the purpose, the legal basis, the retention period and the recipients. Recipients are named by role; section 4 lists each of them with its location.
3.1 Visitors of www.hyperw.net
Data. When you open our website, our hosting provider (Vercel) receives the technical data of your request: IP address, browser user agent, the page requested and the time.
To understand how our website is used, we count page visits with PostHog, in a separate project for this website in PostHog’s EU region: your browser loads the PostHog script from eu-assets.i.posthog.com and sends the statistics to eu.i.posthog.com. PostHog is set up so that it places no cookies and stores nothing in your browser (it keeps its data in memory only for as long as the page is open), does not capture clicks or input automatically, does not record your session and does not link visits to a person. The IP address of your request is discarded by PostHog and not stored. Because nothing is kept in your browser and the IP address is discarded, the statistics carry no identifier that survives a page load: a later visit, or even a reload of the page, cannot be linked to an earlier one. Because of this setup we do not ask for your consent with a banner. This analytics has little or no impact on your privacy, so under article 11.7a(3)(b) of the Dutch Telecommunications Act it needs no consent.
The website sets no cookies and loads its fonts from our own domain. It has no forms. If you e-mail us through the link on the website, we receive your e-mail and its contents.
The website can show our live demo. It is loaded only when you click “Try it yourself”: opening the demo loads HyperW’s demo page from demo.hyperw.net inside the website, with its own consent banner. That page is covered by section 3.11.
Purpose. Delivering and securing the website; understanding how it is used in aggregate; answering your question.
Legal basis. Delivering and securing the website and measuring its use: our legitimate interest in a working, secure and useful website. Questions: our legitimate interest in answering the questions we receive (article 6(1)(f) GDPR).
Retention.
- Hosting request logs: 1 day.
- Website statistics in PostHog: 1 year. This is the fixed retention of the PostHog plan we use and cannot be shortened; the events hold no identifier of you (see above).
- E-mail correspondence: up to 2 years after the last message; where an e-mail is needed for the agreement or our administration, as long as section 3.3 or 3.6 states.
Recipients. Vercel (hosting), PostHog (website statistics), TransIP (e-mail).
3.2 People who start a signup
Data. On the signup page (app.hyperw.net/start) we ask for: your business e-mail address (which must be at your company’s website domain), your company’s website domain, its legal name, country, Chamber of Commerce (KvK) number and/or VAT number, the plan and billing period you choose and, if you came through a partner, a referral code. We do not ask for your name. To check that the form is filled in by a person, a security check runs in your browser (section 3.7).
We send you an e-mail with a verification link. If the company’s website already has a HyperW workspace, we send you an e-mail saying so instead of showing it on screen, so the signup page does not reveal which companies are customers.
If you sign up with a free e-mail provider (such as Gmail), your signup is placed on a list for a manual check; that list holds the stage, the reason, the company domain, your e-mail address, the referral code and the company name.
When you open the verification link and accept the Subscription Terms and the Data Processing Addendum, we keep a pending signup (“claim”) with your e-mail address, the company data, your plan and your acceptance (section 3.4) until your account is created.
Purpose. Verifying that you control the business e-mail address, preparing the agreement and creating your account; preventing abuse (section 3.7).
Legal basis. Our legitimate interest in entering into the agreement with the company you act for (article 6(1)(f) GDPR); if the company is your own sole proprietorship, steps taken at your request before entering into a contract (article 6(1)(b) GDPR). A KvK number identifies a natural person when the company is a sole proprietorship; it is then personal data.
Retention.
- Verification link and its data: 24 hours, deleted when used. If the signup is held for a manual security review: up to 7 days.
- Pending signup (“claim”): 26 hours, deleted when the account is created.
- If a signup is held for review, a reference to its verification link: 7 days (24 hours after approval).
- List of free e-mail signups for a manual check: 90 days after the entry is added; the list also holds no more than the most recent 500 entries.
- List of signups that need a manual step after payment (a failed account setup): 90 days after the entry is added, and removed earlier when the customer’s data is deleted.
- Counters against repeated signups: per IP address 1 hour and per company domain or e-mail address 24 hours; a monthly count of trial signups per IP address, kept 40 days. The IP address is used in these counters only as a hash with a secret key, never in readable form.
Recipients. Vercel, Upstash, Resend (e-mail), Cloudflare and Vercel (security checks, section 3.7), Stripe (when you continue to payment, section 3.6), Microsoft (an internal notice that a signup needs a manual check, with company domain and e-mail domain only).
3.3 Contact persons and Account users of customers
Data.
- Account login: e-mail address and password. We store the password only as a one-way hash (bcrypt); we cannot read it.
- Your login session: a session cookie on your device, valid 7 days for a customer login and at most 12 hours for a HyperW staff or support session.
- Failed login attempts, counted per IP address (and per e-mail address for HyperW staff accounts) for 15 minutes.
- A link to set or reset your password (a reset is requested on app.hyperw.net/login): 24 hours, single use; once one link is used, every other link sent earlier stops working.
- E-mails about your account and subscription: welcome and trial e-mails, a reminder three days before your trial ends, confirmation that your workspace is live, notices when your plan’s usage limit is reached, and the confirmation of your subscription with the accepted document versions.
- Who uploaded a document to the knowledge base (customer or HyperW), and records of what was changed in the admin panel (section 3.8).
- Your company data on your account: legal name, country, KvK number, VAT number.
Purpose. Providing the account and the service under the agreement, securing access, and informing you about your subscription.
Legal basis. HyperW’s legitimate interest in performing the agreement with the customer and in communicating with the persons the customer designates (article 6(1)(f) GDPR); if you are yourself the customer (a sole proprietorship), performance of the agreement (article 6(1)(b)). Securing access: legitimate interest (security of the service).
Retention. Account data is kept for the term of the agreement and deleted within 90 days after it ends; if the customer asks for an export within 30 days of the end, it is deleted after that export. Some records are kept longer: the acceptance record (section 3.4), the trial register (section 3.5), billing records (section 3.6) and security records (section 3.8).
Recipients. Vercel, Upstash, Resend, Stripe (billing contact, section 3.6), Microsoft (internal notices, section 3.9), Sentry (error reports, section 4).
3.3a Partner and affiliate users
HyperW works with sales partners (who serve a portfolio of customers, sometimes under their own branding) and affiliates (who refer customers for a commission).
Data.
- A partner login: the partner’s name, login e-mail address and password, stored only as a one-way hash (bcrypt); a session cookie valid 7 days; failed login attempts counted per partner and IP address for 15 minutes.
- Partner and affiliate user accounts in the HyperW admin: e-mail address, password (one-way hash), role, the partner portfolio or commission ledger the account belongs to, the two-factor authentication secret (encrypted) and recovery codes (hashed), who created the account, and the last login; a session cookie valid at most 12 hours; failed login attempts counted per e-mail address and IP address for 15 minutes.
- Partner branding shown on the partner’s customers’ pages and reports: a logo address, an accent colour, whether “powered by HyperW” is shown, and a free-text footer note (for example a contact line).
- For partner demos: the e-mail address of the partner user who created a demo, on the demo (14 days) and in a monthly demo counter (40 days).
- For affiliates: the commission ledger described in section 3.6.
- Records of their actions in the admin (section 3.8).
Purpose. Giving partners and affiliates access to their portfolio, reports or referral dashboard, securing that access, and settling commissions.
Legal basis. Performance of the agreement with the partner or affiliate (article 6(1)(b)); for the individual users of a partner or affiliate organisation, legitimate interest in communicating with the persons that organisation designates. Securing access: legitimate interest. Where the partner or affiliate is itself a natural person (for example a sole trader), the agreement with that person is the basis (article 6(1)(b)).
Retention. Kept while the partner or affiliate relationship and the user account exist; removed when HyperW deletes the partner or the user. After the partner or affiliate relationship ends, its user accounts and branding are deleted within 90 days. The commission ledger follows section 3.6.
Recipients. Vercel, Upstash, Microsoft (internal notices, section 3.9), Sentry (error reports, section 4).
3.4 Record of acceptance of the Subscription Terms and the Data Processing Addendum
Data. For each acceptance: the document titles, versions, file fingerprints (SHA-256) and addresses, the time of acceptance (UTC), the e-mail address of the person who accepted, the company’s legal name, the acceptance sentence as shown, and whether it was given at signup or later in the admin panel. Entries are added and never changed.
Purpose. Proving that, when and to what the customer agreed.
Legal basis. Our legitimate interest in being able to prove that, when and to what the customer agreed, and to establish or defend legal claims (article 6(1)(f) GDPR).
Retention. For the term of the agreement and 7 years after the agreement ends. The record is kept when the rest of the customer’s data is deleted. This matches the seven years for which we must keep our administration.
Recipients. Vercel, Upstash. A copy is part of the customer’s data export.
3.5 One-trial-per-company register
Data. When a trial starts, we record that the company had a trial: its KvK number, VAT number and website domain, each stored as a SHA-256 hash, with the workspace id and the date. A hash of a KvK or VAT number can be traced back by trying all numbers, so we treat the register as holding those business identifiers. For a sole proprietorship they are personal data.
Purpose. Offering a free trial once per company. A company that already had a trial can still sign up, as a paid start without a trial; it is told so before it accepts.
Legal basis. Legitimate interest in preventing repeated free trials.
Retention. 2 years from the start of the trial. Kept when the rest of the customer’s data is deleted.
Recipients. Vercel, Upstash.
3.6 Billing and invoices
Data. For billing we create a customer record at Stripe with: the account e-mail address, the company’s legal name, country and VAT number, the KvK number, and references to the HyperW workspace. In the Stripe checkout, Stripe collects the billing address and payment details; HyperW does not receive or store card details. Stripe issues the invoices. We store on the account: the Stripe customer and subscription references, the subscription status, the trial end and the end of the current billing period. For referral partners (affiliates) we keep a ledger of commissions, with references to Stripe events, invoices and payments and who approved or paid a payout.
Purpose. Invoicing, collecting payment, applying VAT (including the EU reverse charge) and paying referral commissions.
Legal basis. Performance of the agreement; legal obligation for keeping invoices and accounting records (article 6(1)(c) GDPR; article 52 of the General State Taxes Act and article 2:10 of the Dutch Civil Code).
Retention. Invoices and accounting records: 7 years after the end of the financial year they belong to, as Dutch law requires; the commission ledger also 7 years. Stripe records are not deleted by HyperW’s deletion of customer data.
Recipients. Stripe. Stripe is our processor for the payment processing, and an independent controller where it processes data for its own purposes: preventing fraud and other harm, complying with its legal obligations (such as anti-money-laundering and know-your-customer checks) and improving its services; see https://stripe.com/privacy.
3.7 Abuse prevention at signup
To keep automated scripts and abuse away from the signup, the following checks run on the signup and verification steps:
- Cloudflare Turnstile. A check in your browser on the signup page; to verify it, we send the check token and your IP address to Cloudflare.
- Vercel BotID (basic check). A check in your browser when you submit; to verify it, the request’s headers (including the browser user agent and the IP address known to the platform) are sent to Vercel. The form contents (e-mail address, company data) are not sent. The deeper “Deep Analysis” check is not used.
- Signup rate counter. We count signups per network block (the first three parts of an IPv4 address, or the first 48 bits of an IPv6 address), per network provider (ASN) and per company domain for 24 hours. The network block is stored only as a keyed hash, never in clear.
- Network provider lookup. To find the network provider (ASN) of your IP address, the IP address is sent to IPinfo and a reverse-DNS lookup is sent to Google Public DNS; the result is cached for 60 seconds. We keep only the ASN code.
- Company domain check. We look up whether the company domain receives e-mail (MX record) and whether its website answers. Only the domain is involved.
- Disposable e-mail check. Against a list kept in our own code; nothing is sent.
Based on these signals, a trial signup can be allowed, held for a manual review by HyperW, or refused. A held signup is reviewed by a person at HyperW and you receive the verification link again if it is approved. These checks currently record their outcome without blocking anyone. Apart from the browser checks against automated scripts, which can stop a submission so that you can simply try again, no check refuses a signup unless a person at HyperW has reviewed it first; you can always ask us at privacy@hyperw.net to look at a decision again.
What we keep. For a signup that was not simply allowed: the company domain, e-mail domain, workspace id, plan, reasons, the ASN code and counts, for 30 days. For a held signup: the same and the HyperW staff member who decided, for 7 days. Never your e-mail address, IP address or the verification link in these records.
Legal basis. Legitimate interest in preventing fraud and abuse and in the security of the service (recitals 47 and 49 GDPR). The checks in your browser are strictly necessary to secure the signup you ask to use, so they need no consent (article 11.7a(3)(b) of the Dutch Telecommunications Act).
Recipients. Cloudflare, Vercel, IPinfo, Google, Microsoft (an internal notice when a signup is held: company domain, workspace id, plan and reasons).
3.8 Security and audit records
Data. We keep records of actions in the service: who acted (the e-mail address of a HyperW staff member or partner user, or a customer or partner account reference), the action, the customer concerned, the outcome, the time and the IP address of the request. The full IP address is kept only for actions of HyperW staff and of partner users. Every other record (actions of our customers’ account users, signup and verification requests, failed logins, and requests refused or limited because of too many attempts, including those of visitors of our customers’ pages) holds only a shortened IP address: the first three parts of an IPv4 address, or the first 48 bits of an IPv6 address. Short-lived markers that prevent the same refused request from being recorded twice use a hash of the address with a secret key, never the address itself. Security decisions are recorded separately, without IP addresses or e-mail addresses of the people concerned, but with the HyperW staff member who set or confirmed them.
Purpose. Securing the service, detecting and investigating incidents and abuse, and accountability for access to customer data.
Legal basis. Legitimate interest in the security of the service (recital 49) and HyperW’s obligation to secure the processing (article 32 GDPR).
Retention.
- Activity log: 90 days, at most the most recent 5,000 entries.
- Security records: evidence at most 30 days; security audit 90 days; security actions until 30 days after they end; settings until they are changed.
- Short-lived counters against password guessing and abuse: 5 minutes to 24 hours.
- Server logs of the service: 1 day. These records are not deleted when a customer’s data is deleted, because they are the record of that deletion and of access to it.
Recipients. Vercel, Upstash, Microsoft (security alerts, section 3.9), Sentry (error reports, section 4).
3.9 Internal notices
HyperW receives internal notices about the operation of the service in Microsoft Teams channels of its own: a security and operations channel (for example: billing events, security alerts and a daily security summary) and an onboarding channel for new customers that need a check (for example: a signup held for review or parked for a manual check, a knowledge base waiting for review, or a failed account setup). In every internal notice, e-mail addresses are shortened to their first character and domain (for example d***@example.nl); in security alerts, IP addresses are shortened to their first three parts. Some notices name the customer’s workspace or company domain. The same shortening applies in both channels. If the onboarding channel is not configured, its notices go to the security and operations channel; if that channel is not configured either, they go to an internal HyperW Slack channel, with the same shortening.
Purpose and basis. Operating and securing the service: legitimate interest.
Retention. Messages in these channels are deleted 90 days after they were posted.
3.10 Data from the customer’s website used to set up the service
When a customer signs up, we read the public pages of the customer’s website (for example the home, about, team and contact pages) to generate the first version of the customer’s knowledge base and design with AI (Anthropic). If those public pages name people (for example team members), their names and the text about them can be part of what we send to Anthropic and store in the knowledge base. We do not send the signup e-mail address or account data to Anthropic. No screenshot service is used.
Purpose and basis. Setting up the service the customer asked for. After the customer has accepted the Subscription Terms and the Data Processing Addendum, we read these pages on the customer’s instruction, as its processor. When HyperW or a partner prepares a demo for a prospect before any agreement, HyperW is the controller, on the basis of its legitimate interest in showing the prospect the service with its own public content; a demo and its data are deleted after 14 days.
Retention. The knowledge base is kept for the term of the agreement and deleted with the customer’s data.
Recipients. Anthropic.
3.11 The HyperW demo (demo.hyperw.net)
On demo.hyperw.net HyperW demonstrates its own service on a page of its own; the consent banner there names HyperW. HyperW is therefore the controller of the visitor processing that the service performs on that page, as described in the statement for visitors of pages powered by HyperW (https://app.hyperw.net/privacy), with HyperW in the role of “the Controller” named there.
4. Recipients
We share personal data only with the recipients below and only as far as needed for the purposes in section 3. We do not sell personal data.
| Recipient | What for | Role | Where |
|---|---|---|---|
| Vercel | Hosting of the website www.hyperw.net, the signup and the service; the BotID check | Processor (also for the BotID check) | Server functions in Frankfurt (EU); the network edge that receives your request is global |
| PostHog | Statistics of www.hyperw.net (section 3.1), through eu.i.posthog.com and eu-assets.i.posthog.com | Processor | EU region |
| Upstash | Data store (Redis); message queue | Processor | Frankfurt (EU) |
| Stripe | Billing, payment and invoices | Processor for the payment processing; independent controller for its own legal obligations and fraud prevention | Ireland (Stripe Payments Europe, Limited); transfers to the United States under the EU-US Data Privacy Framework and standard contractual clauses |
| Resend | Sending service e-mails | Processor | EU region for the sending domain (Resend in the United States: Data Privacy Framework and standard contractual clauses) |
| TransIP | Hosting of HyperW’s mailboxes, including privacy@hyperw.net | Processor | Netherlands |
| Cloudflare | Turnstile check at signup | Processor; independent controller where Cloudflare uses the signals to improve its own bot detection | Global network; Data Privacy Framework, standard contractual clauses as fallback |
| IPinfo | Network provider (ASN) lookup at signup | Processor | United States (standard contractual clauses) |
| Google (Google Public DNS) | Reverse-DNS lookup of the signup IP address | Independent controller (a public service under Google’s own privacy policy) | United States (global network); Data Privacy Framework |
| Anthropic | AI generation of the knowledge base from the customer’s public website | Processor | United States (contracting party Anthropic Ireland, Limited; transfer under standard contractual clauses) |
| Microsoft (Teams) | Internal notices to HyperW (section 3.9) | Processor, under the Microsoft 365 processor terms | EU Data Boundary; Data Privacy Framework and standard contractual clauses for remaining transfers |
| Slack | Internal notices while the Teams channel is not configured (section 3.9) | Processor | United States; Data Privacy Framework and standard contractual clauses |
| Sentry | Error monitoring of the service; reports are stripped of IP addresses, cookies, headers, request contents and e-mail addresses, and storing IP addresses is switched off | Processor | EU region (Frankfurt) |
PostHog is not used in the signup or the admin panel.
Transfers outside the EEA. Some recipients are established in the United States or can reach data from there. For recipients certified under the EU-US Data Privacy Framework (Stripe, Cloudflare, Google, Microsoft, Slack, Resend, Vercel, PostHog, Sentry and Upstash), the transfer is based on the European Commission’s adequacy decision of 10 July 2023; their data processing terms also contain the European Commission’s standard contractual clauses. For IPinfo and Anthropic, which are not certified, the transfer is based on those standard contractual clauses (2021/914). You can ask us at privacy@hyperw.net for more information about these safeguards.
5. Your rights
You have the right to access your personal data, to have it corrected or erased, to restrict its processing, to object to processing based on legitimate interest, and to receive data you provided to us in a portable format. Where we rely on consent, you can withdraw it at any time. Send your request to privacy@hyperw.net. We answer within one month; we may ask you to confirm your identity first.
Some data we must or may keep despite an erasure request, for example the acceptance record and billing records (sections 3.4 and 3.6), for as long as stated there.
You have the right to lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens, https://autoriteitpersoonsgegevens.nl) or with the supervisory authority in your EU country of residence or work.
6. Security
We protect personal data with technical and organisational measures, including encrypted connections, one-way hashing of passwords, two-factor authentication for every HyperW staff account, separation of each customer’s data and the security records described in section 3.8.
7. Changes to this statement
We update this statement when our processing changes. The date at the top shows the current version. Earlier versions are available on request. We inform customers of material changes by e-mail to the account e-mail address before they take effect.