Terms of Service

1. Who we are

V.P. Labs (trading as wawesome.io) is registered in the Netherlands with the Chamber of Commerce (Kamer van Koophandel) under number 76655180, based in Almere, the Netherlands.

In these terms, “we”, “us”, and “our” mean V.P. Labs (trading as wawesome.io). “You” means the person or organisation opening or holding a workspace.

Questions regarding these terms can be sent to legal@wawesome.io. For statutory contact points under EU law, see section 12.

2. What these terms cover

These terms govern your use of the wawesome platform, including the dashboard, the command-line tool, the API, and the functions and files you deploy.

By creating a workspace, signing in, or deploying code, you agree to these terms. If you act on behalf of an organisation, you confirm that you are authorized to bind that organisation.

3. Definitions

Workspace. The account that holds your apps, your billing relationship with us, and the people you invite.

App. A named group of functions that answers at its own hostname.

Function. A unit of code executed in response to incoming HTTP requests or a recurring timer.

Version. An immutable deployment of a function and its companion files. Once created, a version is never edited.

Your Content. Everything you upload or produce through the platform: source code, compiled WebAssembly modules, static files, environment variables, invocation responses, data handled on behalf of your visitors, what you write to the dashboard assistant, and the code and text it produces for you.

End User. Any person who accesses your content through the platform, including your clients and their visitors.

4. Your workspace and who may use it

You sign in through a supported identity provider. You are responsible for keeping your credentials secure, including any two-factor authentication you configure.

Everyone you invite to your workspace acts on your behalf. What they do in the workspace, you do.

You must be at least 18 years old to open or hold a workspace. If you are younger, you may use the platform through a workspace held by a parent, guardian, or school, who holds it and answers for it.

We welcome businesses, agencies, freelancers, students, and individual hobbyists. If you are an individual consumer resident in the European Union or European Economic Area, you retain all mandatory protections provided by the laws of your country of residence that cannot be waived by contract (see section 13 and section 15).

5. Your content, client hosting, and licensing

You keep all intellectual property rights in Your Content. We claim no ownership over anything you deploy. Where we hold any rights in the code or text the dashboard assistant produces for you, we assign them to you, to the extent the law allows.

You grant us only the limited rights necessary to operate the platform: storing your code and assets, compiling and executing them, routing requests to them, serving them to End Users, keeping backup snapshots, and purging caches upon updates or restrictions.

You are responsible for Your Content. You confirm that you have the right to publish it, that it is lawful, and that it does not violate third-party rights.

Hosting for clients. Agencies and developers may build, host, and manage apps on behalf of third-party clients. Your clients and End Users have no contract with us and have no direct claims against us. You remain our sole contracting party and are responsible for their use of the platform.

Transferring an app. If you send an app, you confirm that you hold the right to transfer it. If you receive one, you take it as it stands, with its code, its environment, and its history. We do not decide who an app belongs to, and a disagreement between a developer and their client over ownership is between the two of them.

We do not review your code or files before they go live. Deployments are automated.

6. What you may not do (Acceptable Use)

You may not use the platform to:

• break the law or facilitate unlawful activity;
• publish or serve content that exploits or harms minors, including child sexual abuse material (CSAM);
• promote terrorism, incite violence, or threaten, defame, or harass individuals or groups;
• host or distribute pornography, sexually explicit content, or adult services;
• deceive or defraud people, including running fake shops, fraudulent payment pages, or support desks; impersonating persons, businesses, or public authorities; or harvesting passwords, credit card numbers, or identity documents under false pretenses;
• distribute malware, viruses, trojans, ransomware, or spyware, or operate botnet command-and-control infrastructure;
• scan, probe, or penetration test networks or systems you do not own or lack written permission to test;
• attack the platform, attempt sandbox escapes, access other tenants’ data, or bypass quotas and limits;
• use the dashboard assistant as a general-purpose language model: for anything other than work on your workspace, from anywhere other than the dashboard (for example by scripting its API or connecting it to another product), or across several workspaces to get more of it than one plan includes;
• make the dashboard assistant act outside your workspace or ignore its limits, extract its instructions, probe the model behind it, or produce anything the usage policies of our model providers forbid;
• send unsolicited bulk messages (spam) or operate open proxies, anonymizing relays, or VPN endpoints;
• mine cryptocurrency or run workloads whose primary purpose is consuming compute rather than serving an application;
• infringe intellectual property rights, including copyrights, trademarks, trade secrets, or patents;
• offer unlicensed gambling, illegal lotteries, weapons, or controlled substances;
• operate safety-critical applications where a failure or interruption could directly lead to death, personal injury, or physical environmental damage;
• resell raw compute, bandwidth, or storage as a standalone infrastructure service. (Building applications or client websites on wawesome is permitted and encouraged; reselling the platform itself is prohibited.)

These rules form part of these terms. They may move into a separate Acceptable Use Policy document as the platform grows.

7. Illegal content, notice-and-action, and moderation

Reporting illegal content. Anyone may report content on the platform they believe to be illegal by emailing abuse@wawesome.io or using our public notice-and-action form. Reports should detail the exact URL, why the content is believed to be illegal, and how we can reach the reporter.

Human review. Every report is reviewed by a person. We do not use automated content filters or automated scanning to restrict content.

Action on reports. If we determine that content is illegal, we disable access to it. We act expeditiously, especially where someone is in danger or where the law sets a fixed deadline (such as orders under the Terrorist Content Online Regulation).

Statement of reasons. If we restrict anything you deployed, we tell you what we restricted, the grounds for the decision, and the reasons on your dashboard and by email, in line with DSA Article 17.

Appeals. You can appeal any moderation restriction by writing to appeals@wawesome.io. A person will review your appeal.

Manifestly unfounded reports. Under DSA Article 23, we may suspend processing notices from reporters who repeatedly submit notices that are manifestly unfounded, after issuing a prior warning.

8. Suspending and closing workspaces

Narrowest effective restriction. When addressing illegal content, security threats, or serious breaches of section 6, we restrict the narrowest possible unit: a single function before an app, and an app before a whole workspace.

Edge cache purge. Disabling access to content also purges the copies held by our content delivery network, so a restriction reaches the edge and not only the origin. A network accepts a purge rather than confirming it object by object, so we check the address itself afterwards and treat a takedown as unfinished until it answers as restricted.

Separation from billing. Moderation and legal restrictions are completely separate from billing. Falling behind on payment never triggers an operator restriction or takedown.

Closing a workspace. The workspace owner may close the workspace at any time from its settings in the dashboard. It closes fourteen days after the owner asks. Until then nothing stops: your apps keep serving, every member is told by email, and the owner can cancel. When the fourteen days end, we cancel your subscription, detach your custom domains, delete your apps with their code and files, revoke your credentials and sessions, and end every membership. Our storage keeps an older copy of your code and files for recovery, in backups too. The last of those copies is gone about 31 days after the workspace closes, so about 45 days after the owner asks. We keep only what tax law obliges us to keep and the record of what you accepted, as the Privacy Policy describes. You can export your workspace until it closes.

Closing a workspace does not erase your account. You can erase your account from the dashboard. If you own a workspace, erasing your account closes it as described above, and your account is erased once it has closed. Otherwise it is erased within 30 days of the request.

If you cannot sign in, for example because you lost the account you signed in with, write to privacy@wawesome.io from the address on your account. We close the workspace or erase the account for you, on the same terms.

Misusing the assistant. Breaking the rules for the dashboard assistant in section 6 is a severe breach. We may turn the assistant off for the workspace at once, without notice. If the misuse is deliberate or happens again, we may close the workspace immediately and refuse a new workspace from the same person. A workspace that has never paid us may be closed on the first misuse.

We may terminate your workspace on 30 days’ notice, or immediately in the event of a severe breach of section 6 or where required by law. If we close your workspace, we provide a reasonable opportunity to export your data and code, unless legally prohibited from doing so.

9. Plans, payment, and the non-payment ladder

Plans. The platform offers a free plan and paid tiers. Each plan specifies limits on app slots, invocations, data transfer, concurrency, and scheduled jobs. Published specifications form part of these terms.

Soft allowances on paid plans. Paid plans are not charged surprise automated overage fees. If your usage materially exceeds your plan’s allowance on a sustained basis, we will contact you and give you 30 days’ notice to move to an appropriate tier. We never stop serving a paid plan for going over an allowance. Far past one we may suspend your scheduled jobs and reduce your rate limit, as a backstop against runaway usage rather than a limit at the figure you bought. We tell you when we do, and a new period or an upgrade lifts both. On the free plan, allowances are enforced as limits; excessive usage may be throttled or paused until the next period.

Monthly subscriptions. All paid plans are sold strictly on a monthly billing cycle and renew automatically each month until cancelled. You may cancel your subscription at any time via the dashboard. Cancellations and plan downgrades take effect at the end of the current paid monthly billing period. We do not issue pro-rata refunds for partial months, which complies with the Dutch Wet Van Dam notice limit of one month. There is one exception: an objection to a new subprocessor, which the Data Processing Agreement refunds pro rata. We do not offer fixed terms longer than one month without separate written agreement.

Upgrades and downgrades. Upgrading takes effect immediately, with the prorated difference billed for the remainder of the period. Downgrading takes effect at the end of the paid period. When you downgrade to a plan with fewer app slots than you currently occupy, or cancel your subscription, your existing apps remain online through the end of the paid period. To fit your new plan, delete the apps you no longer need before the period ends. Deleting an app is what frees a slot. An app you pause yourself stays yours, keeps its code and its files, and keeps its slot. If you still occupy more slots than your plan grants, we email everyone who owns the workspace, we say so in your dashboard, and we give you at least 30 days from that notice. You can upgrade, you can delete the apps you no longer need, or you can tell us which apps stay. After that notice runs out, we stop serving the apps past your allowance until the slots you occupy match your plan. If you have not told us which ones stay, we keep the apps you have held longest. Stopping serving keeps your code, configuration, files and data exactly where they are, and they start serving again as soon as you are back inside your plan. The 30 days start again from scratch if you come back inside your plan and later go past it.

Custom domains. Custom domains come with the paid plans, and the free plan does not let you attach one. On every plan, your apps keep answering at their platform-assigned addresses. When a workspace that holds a custom domain moves to the free plan, because its subscription ended or was downgraded, or when the free days of a handover end with no plan chosen, we email everyone who owns the workspace and give at least 30 days from that notice. After that notice runs out, the workspace’s custom domains stop answering. We do not detach them: the domains, their DNS records and their certificates stay in place, and they answer again as soon as the workspace is on a paid plan. A failed payment on its own never stops a custom domain. The 30 days start again from scratch if the workspace goes back to a paid plan and later moves to the free plan again. An app we have stopped serving under the paragraph above answers at no address at all, its custom domain included, until it starts serving again.

Payment and Merchant of Record. Payments are processed through Stripe Managed Payments, who acts as Merchant of Record for paid checkout transactions and handles applicable transaction taxes. Stripe’s terms apply to payment processing. Your hosting capacity and deployment pipeline are provisioned as soon as the purchase completes, which is what completing checkout asks us to do.

Fifteen days free. Every paid plan starts with a free trial of 15 days. Nothing is charged when you subscribe. The plan is yours from the first day, and the first payment is taken when the trial ends. Cancel at any point before that and you pay nothing. Your dashboard states the date of the first charge for as long as the trial runs. The trial runs on whichever plan you pick.

If you are a consumer in the EU or EEA, the law gives you 14 days to withdraw from a distance contract, counted from the day the contract is made, which is the day you subscribe. Nothing in these terms takes that right away, asks you to waive it, or makes it conditional. The trial is longer than that period, so nothing has been paid while the right is open. Write to billing@wawesome.io to use it.

Stripe handles payments, disputes, and transaction-level support for those purchases under its own terms. Write to billing@wawesome.io either way and we will take it from there, whether the answer is ours or Stripe’s as Merchant of Record.

The non-payment ladder. If a subscription payment fails, your running client websites are not taken down during payment recovery:

1. Day 0 to 14: We display a reminder on your dashboard while Stripe retries the payment method on file. Deployments and serving continue unaffected.
2. Day 14: If payment has not cleared after 14 days, new deployments are refused with HTTP status 402 (Payment Required). All existing apps and functions continue serving uninterrupted.
3. Day 30: If payment remains unresolved after 30 days, your workspace drops to free-plan service: capacity scales down to free plan limits, and automated background schedules pause.

Service for unpaid and abandoned workspaces. An unpaid workspace whose subscription terminates operates under free-plan service. Because free-plan service is offered without a permanent commitment and may be withdrawn or modified on 30 days’ notice, we reserve the right to discontinue hosting an abandoned unpaid workspace after providing at least 30 days’ advance notice. Apps and app slots are never deleted or reclaimed during active payment recovery. A workspace whose subscription has ended and which holds more apps than the free plan covers is given the same 30 days’ notice described under Upgrades and downgrades above, after which the apps past the allowance stop serving. Its custom domains follow the rule under Custom domains above.

Cancelled subscriptions with unpaid balances. If a subscription is cancelled while an invoice remains unpaid, the subscription terminates at the payment provider, leaving no open invoice to pay in the portal. To settle an outstanding balance and restore full deployment privileges, contact billing@wawesome.io.

Price changes. We provide at least 30 days’ advance notice before any price increase takes effect. You may cancel your subscription prior to the effective date.

10. Data protection

Customer data in Your Content. For personal data processed by your deployed functions and files, you are the Data Controller and V.P. Labs is the Data Processor under the EU General Data Protection Regulation (GDPR). Our Data Processing Agreement (DPA) governs this processing and forms part of these terms.

Account data. For account information we collect about you (such as your name, email, and billing records), we are the Data Controller. Our Privacy Policy explains how this data is handled. Inquiries regarding personal data and GDPR rights should be directed to privacy@wawesome.io.

Operational records retention. Metadata for function invocations is retained for 35 days and then deleted. Captured execution log output is retained for 14 days and then deleted. A conversation with the dashboard assistant is deleted 30 days after its last message. Aggregated, anonymized billing counts are retained longer for accounting records.

Personal data must not be included in function slugs, app names, or public URL paths.

11. Availability and changes to the service

We strive to keep the platform reliable, but we do not offer a service level agreement (SLA) or guaranteed uptime under these standard terms. The platform is provided “as is” and “as available”.

We may update or modify platform features. If a planned change would break backwards compatibility for your running code, we provide at least 30 days’ advance notice, unless urgent security maintenance requires immediate deployment.

If we decide to end the service, we email every workspace owner at least 90 days before it ends. Until the service ends, export keeps working, so you can take your code, files and configuration with you.

You are responsible for keeping your own off-platform backups of your source code and data.

The dashboard assistant. The dashboard assistant uses a language model. It gives advice about your workspace and makes no decision about any person. Its answers and the changes it proposes can be wrong or incomplete.

It changes nothing in your workspace unless it is approved. A member approves one change, after the dashboard shows what it changes, or approves in advance every change a rule covers (“Always allow”). When a rule is set, the dashboard shows what it covers, such as one kind of change on one App, and for how long. A rule is the advance approval of the person who set it, and they can withdraw it at any time.

A change runs with the approving member’s own role and permissions, checked when the change runs. The assistant cannot give anyone more than their role allows, and a change is refused if the member no longer holds the permission it needs.

An owner controls the assistant in the workspace settings. They can stop it from making changes, so that it only reads, or turn it off entirely, so that nothing from the workspace is sent to the model providers. The assistant reads execution logs only once an owner or admin has allowed it.

On the Free plan, the assistant is offered as a courtesy, and we may limit or withdraw it at any time.

An approval is your instruction to make the change. You are responsible for checking a change before you approve it, and for its effects once approved, as with a change you make yourself. We do not promise that code or text from the assistant is correct, secure, original, or free of third-party rights, open-source licence terms included. Subject to section 13, we are not liable for a defect, security flaw, downtime, data loss or financial loss caused by a change a member approved, or by acting on the assistant’s answers.

What you write in the chat is sent to the model provider as written. Do not write passwords, keys or other secrets there, or personal data about other people. Section 8 says what happens when the assistant is misused.

12. Statutory contact points (EU Digital Services Act)

In accordance with Articles 11 and 12 of Regulation (EU) 2022/2065 (DSA), we designate the following points of contact:

• For EU Member State authorities, the European Commission, and the European Board for Digital Services (Article 11): abuse@wawesome.io. Accepted languages: Dutch and English.
• For recipients of the service and legal notices (Article 12): legal@wawesome.io. Accepted languages: Dutch and English.
• For moderation appeals: appeals@wawesome.io.
• For illegal content notices (Article 16): abuse@wawesome.io and our public Notice and Action web form.
• For privacy and data protection inquiries: privacy@wawesome.io.
• For payment recovery and billing dead-ends: billing@wawesome.io.

13. Liability and indemnity

Nothing in these terms limits or excludes our liability for intentional misconduct (opzet), deliberate recklessness (bewuste roekeloosheid), death or personal injury caused by negligence, or any other liability that cannot be lawfully limited under Dutch law.

Subject to the paragraph above and to the extent permitted by law:

• Neither party is liable to the other for indirect, incidental, special, or consequential damages, including loss of profits, loss of revenue, loss of business goodwill, or loss of data beyond our operational retention periods.
• Our total aggregate liability to you arising out of or relating to these terms or the service in any 12-month period is capped at the total fees paid by you to us in the 12 months preceding the incident, or €100, whichever is greater.

Indemnity. Business customers agree to defend, indemnify, and hold harmless V.P. Labs and its operators from any third-party claims, liabilities, damages, or costs (including legal fees) arising from Your Content, your End Users, or your breach of section 6.

Consumer protection carve-out. If you are an individual consumer resident in the EU or EEA using the platform outside a trade or business:

1. The limitations in this section apply only to the extent permitted under Articles 6:236 and 6:237 of the Dutch Civil Code (Burgerlijk Wetboek) and the mandatory consumer protection rules of your home jurisdiction.
2. The indemnity clause above does not apply to you.

14. Changes to these terms

We may update these terms from time to time. We will provide at least 30 days’ advance notice of material changes by email or via a notice on the dashboard.

Continuing to use the platform after updated terms become effective constitutes acceptance of the new terms. If you do not agree to the changes, you must close your workspace before the effective date. Immediate changes may occur only where required by law or to address critical security emergencies.

15. Governing law and dispute resolution

These terms and any disputes arising out of or in connection with them are governed by the laws of the Netherlands.

Any dispute that cannot be resolved amicably shall be submitted to the exclusive jurisdiction of the competent court in Amsterdam, the Netherlands.

Consumer jurisdiction. If you are an individual consumer resident in the EU or EEA, nothing in this clause deprives you of the protections of Regulation (EU) No 1215/2012 (Brussels I bis). You may bring proceedings against us in either the courts of the Netherlands or the competent courts of your country of residence, and proceedings against you may only be brought in the courts of your country of residence.

If any provision of these terms is held to be invalid or unenforceable, that provision will be modified to the minimum extent necessary to make it enforceable, and the remaining provisions will remain in full force and effect.