Beta terms

1. Who this is between

These terms are between Flabbergast, the product studio in Zagreb, Croatia that operates wandkit, and the company that creates an organization and integrates the SDK. In this document that company is "you". If you are accepting on behalf of an employer, you are confirming you are allowed to.

These terms cover the dashboard, the API, the CLI and the iOS SDK. They do not cover your end users. Your relationship with the people who use your app is yours to define, in your own terms and your own privacy policy.

2. What the beta is, and is not

• wandkit works, but it is not finished. Endpoints, screens and payloads can change during the beta, sometimes without notice.
• There is no service level agreement, no uptime commitment and no committed response time. There is no uptime monitoring either. The metrics endpoint is an unimplemented placeholder, so treat any status claim you have not measured yourself as unproven.
• The SDK supports iOS 15 and later. There is no Android SDK and no React Native SDK. Android push tokens can be registered by the API, but nothing is ever delivered to them, so do not build on that.
• Beta data can be lost. Do not make wandkit the system of record for anything you cannot afford to lose. Keep your own copy of anything that matters, with wandkit responses export in the CLI.
• We may pause or end the beta. If we do, we will give you what notice we can.

Build the integration so a failed wandkit call never blocks your app. The SDK queues offline and fails quietly by design. Keep it that way.

3. Fees

There are none. wandkit contains no billing code, no pricing, no payment method on file and no way to charge you. You owe nothing for beta access.

One thing worth separating, because the word subscription appears in the product: wandkit can read your own users' subscription state from RevenueCat, and its reward fulfilment pipeline can grant campaign rewards back through your entitlement provider on your behalf, with retries and a recorded grant state. That is your users' billing, in your account, with your provider. It is never wandkit billing you.

If wandkit becomes a paid product, that will be a separate agreement that you have to accept before anything is billed. A beta account will not quietly become a paying one.

4. What your app sends us

You decide what goes into identify(), event() and survey answers. We store what you send, as you send it. You are the controller for that data and you are responsible for having a lawful basis and telling your users about it. wandkit does not collect consent on your behalf and shows no consent screen.

• Use a stable pseudonymous identifier in identify(), not a name or an email address, unless you have a specific reason and a basis for it.
• Do not send special category data, government identifiers, payment card data, credentials or health data through the SDK. Nothing in wandkit is built to hold any of it.
• Screenshot bug reports re-render your own window inside your app. They never touch the photo library and never trigger a photo permission prompt. Whatever is on screen at that moment is what gets sent, so keep sensitive screens out of it or leave the feature off.
• An organization admin can delete a project from project settings.

There is a right-to-erasure action for a single end user, available to organization admins. It runs in one transaction and returns a count of every row it touched, so you have something to file. Read what it actually does before you rely on it: that person's posts and comments are anonymized, not deleted, because other people's threads have to keep their context. Their votes and follows are rewritten to a placeholder, and their reports, push devices, any ban on them and their end-user record are deleted. If your obligation is to remove the content itself, erasure alone does not do it. Hide or delete the posts as well.

What does not exist, stated plainly so your compliance review does not have to guess: there is no SOC 2 report, no region or data residency choice, and no transfer mechanism beyond the processor sitting in the European Union. The data processing addendum is part of these terms; a countersigned copy is available on request. If your review needs any of those, raise it at info@wandkit.app before you integrate, not after.

5. End-user content and moderation

Pre-moderation is mandatory and cannot be disabled. Every post created through the SDK arrives with status pending and is invisible to your other users until a member of your team approves it in the dashboard.

• Approving is publishing. It puts the post in front of your users, and it notifies the author by push if they have a device registered. Read before you approve.
• You get the tools, not the service. Reports queue for you, posts and comments can be hidden after the fact, and end users can be banned per project. We do not moderate your board for you.
• Anonymous end users are read-only. Posting, voting and commenting require identify().
• Attachments are capped at 5 per post, images up to 10 MB and video up to 50 MB.
• Survey copy is server-driven. Titles, options and buttons live on the server, so you can change what your users read without shipping an app release. That is your responsibility. It sits outside app review and it is your name on the screen.

We may remove content or suspend a project when something is illegal or puts the service at risk. That is a safety measure for the platform, not a review service for you.

6. Your account and your keys

The dashboard signs in with Google. That is the only sign-in method wired up today. There is no SSO, no SAML, no SCIM, no MFA and no admin audit log. If your security policy requires any of them, wandkit does not meet it yet.

• wk_ SDK keys ship inside your binary. Treat them as public. Anyone with your app can extract one, so put nothing behind a wk_ key that you would not publish.
• wks_ server keys are secrets. They stay on your servers. Never in an app, a web page or a repository.
• wkp_ personal access tokens are scoped, expiring and revocable, for the CLI and the API. They belong to a person, not to a team.

You are responsible for everything done with your keys. Rotate or revoke a key the moment you think it leaked.

If you claim an email domain for auto-join, understand what it does. Someone signing in to wandkit for the first time with a verified address on that domain gets an account and a member seat in your organization, with no invitation and no approval step. It applies to new accounts only, so it will not re-add anyone an admin has removed. Set it deliberately, and only for a domain you control.

7. Acceptable use

• Do not use wandkit to break the law, distribute malware, harass anyone, or collect data you have no right to collect.
• Do not send push notifications or campaigns to people who have not opted in, and do not use them for advertising unrelated to your app.
• Do not try to reach another customer's project, probe or overload the API, or scrape the dashboard.
• Do not resell wandkit or run it as a service for third parties without a written agreement.
• Do not use the referral system to pay people for fake installs or fake conversions, and do not manufacture referrals to claim campaign rewards you are not entitled to.

Breaking any of this is grounds for suspension without notice.

8. Termination

You can stop at any time. Remove the SDK, revoke your keys, delete your projects. No notice, no exit process, nothing to cancel.

We can suspend or end your access at any time, with as much notice as the situation allows, for a breach of section 7, for risk to the service, or because the beta is ending. When access ends, keys stop working and SDK calls start failing, which is why section 2 asks you to make those calls non-blocking.

Export anything you want to keep before you go. If you want your project data deleted after you leave, write to info@wandkit.app.

9. Changes

The product changes during a beta, and so will these terms. When they change we post the new version on this page, so this page is the current one. Where we hold an email address for you we may also send a note, from noreply@wandkit.app. Do not rely on the email. Continuing to use wandkit after a change means you accept it. If you do not, stop using it and revoke your keys.

10. Warranty and liability

wandkit is beta software provided as is, with no warranty of any kind, express or implied. We do not warrant that it will be available, that it will be free of defects, or that data will not be lost.

To the fullest extent the law allows, we are not liable for indirect or consequential loss, lost profits, lost revenue, or lost or corrupted data. Because the beta is free of charge, there are no fees to refund and no fee-based cap to fall back on. Nothing here limits liability that cannot lawfully be limited, including liability for death or personal injury caused by negligence, or for fraud.

Needs review< Some jurisdictions do not allow every limit in this section; where a limit is not allowed, it applies to the fullest extent the law does allow.

11. Governing law

These terms are governed by the laws of Croatia, and the courts of Zagreb, Croatia have exclusive jurisdiction over any dispute arising from them.

12. Contact

Write to info@wandkit.app. That is the only address that reaches us. sales@, support@, hello@ and security@ do not exist, and mail sent to them goes nowhere.