Terms of service

WalletPassAPI is provided by [Company name], a company registered in [country of registration] with company number [company number], whose registered office is at [registered address] ("we", "us").

These terms are an agreement between us and the organization you use WalletPassAPI for ("you", the customer). By creating an account, accepting an invitation, or using the API or dashboard, you accept them on its behalf, and confirm you're allowed to. If you're using it for yourself as a business, "you" means you.

• For now, WalletPassAPI is invite-only: you can sign up if you've been invited or we've given you access.
• Your account is an organization, which holds the plan and contains one or more workspaces. You're responsible for who you invite as members and admins, and for everything done with your account and API keys.
• Each person signs in with their own email address. Keep API keys and sign-in codes secret, never forward a code, and sign out on shared devices. If you think something's wrong, rotate a key or remove a member straight away, and tell us too.
• Give us accurate details, and keep your email address up to date so our service emails reach you.

WalletPassAPI lets you design, issue, update and withdraw Apple Wallet and Google Wallet passes, with install pages for your pass holders. Passes are signed with your own Apple and Google credentials once you add them. You can work through:

• The API

  Create and update passes from your own systems.

• The dashboard

  Design, issue and manage passes in the browser.

• Templates

  One design, many passes, updated together.

• Spreadsheet imports

  Issue or update passes in bulk.

• Webhooks

  Hear about pass events in your own systems.

• Install pages

  A page for each pass, where holders add it to their wallet.

Until you add your own Apple and Google credentials, passes are signed with ours. Those are for trying the service out only:

We may change or end test passes, and withdraw ones that break these rules.

• You're responsible for what you put on passes and send to holders, and for making sure it's accurate and lawful.
• You must have the right to issue passes to your holders and to contact them through them, including any consent the law requires, and give them the information about their data the law requires.
• When you use your own Apple or Google credentials, you must follow the Apple Developer Program and Google Wallet terms that apply to you, and keep your membership and certificates current.
• Keep your credentials, API keys and webhook secrets secure, and only upload credentials you're entitled to use.
• Don't put sensitive data on passes, such as health information, full payment card numbers or government identity numbers.

You must not use WalletPassAPI to:

• send spam or messages people haven't agreed to receive;
• issue passes with unlawful, harmful, misleading or infringing content;
• impersonate another person, business or brand, or issue passes for a business you don't represent;
• defraud anyone, including with fake tickets, vouchers or offers;
• trick people into giving personal or payment details, through passes, install pages or sign-up forms;
• collect personal data through passes or sign-up forms without a lawful basis and the information the law requires you to give;
• upload malware, or anything designed to harm devices or systems;
• try to reach another customer's account or data, get round plan limits, the marking on test passes, or rate limits, or test, probe or attack the service without our written permission;
• resell the service, or let anyone outside your organization use it, without our agreement.

You own the content and data you put into WalletPassAPI. You give us permission to use it only to provide, secure and support the service for you.

For your pass holders' personal data, you're the controller and we're your processor. Our data processing terms [DPA: link, or "are available on request"] form part of these terms and apply to that data. Our privacy notice explains how we handle our own customers' and visitors' data. All of it is stored in the EU.

Plans are Free, Starter, Growth and Enterprise, and differ in how many operations you can make, how many Apple and Google identities and workspaces you have, and the support you get.

Paid plans aren't available yet. We'll publish prices before launch, and you won't be charged anything unless you choose a paid plan and agree to its price. [Payment, renewal, tax and refund terms, added with payments]

• We work to keep WalletPassAPI available and passes updating, but we don't promise it will be uninterrupted or error-free, and we sometimes need maintenance time. An agreed level of service is available on Enterprise.
• We improve the service and may change or remove features. If a change takes away something you rely on, we'll give you reasonable notice.
• We may update these terms. We'll give at least [notice period, e.g. 30 days] notice of changes that matter, by email or in the dashboard. If you keep using the service after that, the new terms apply.

• You can stop using WalletPassAPI at any time, and close an organization or delete a workspace from the dashboard, or ask us to close your account.
• We may suspend or end your access, or withdraw passes, if you seriously or repeatedly break these terms, if your use puts the service, other customers or pass holders at risk, or if the law requires it. Where we reasonably can, we'll warn you first and give you time to fix it.
• We may end the service for everyone with at least [notice period, e.g. 90 days] notice.

We own WalletPassAPI, including its software, documentation and design. We give you a right to use it under these terms while your account is open; it doesn't transfer ownership of anything to you. Example code in our documentation you may copy and use freely in your own systems.

If you send us ideas or feedback, we may use them without any obligation to you.

Apple Wallet is a trademark of Apple Inc. Google Wallet is a trademark of Google LLC. WalletPassAPI isn't affiliated with or endorsed by Apple or Google.

• We provide WalletPassAPI with reasonable skill and care. Beyond that, and as far as the law allows, it's provided "as is", without other warranties or conditions, including fitness for a particular purpose.
• Neither of us is liable for indirect or consequential loss, or for loss of profit, revenue, goodwill or data, however it arises.
• Each party's total liability under these terms in any 12 months is limited to [liability cap, e.g. the greater of the fees paid in that period and £100].
• You'll cover us against claims from third parties, including your pass holders, arising from the content you put on passes or from your breaking these terms or the law.

These terms are governed by the law of [England and Wales], and the courts of [England and Wales] have exclusive jurisdiction over any dispute about them.

• Neither of us is responsible for delays caused by things outside our reasonable control.
• You can't transfer these terms without our agreement. We may transfer them to a company that takes over WalletPassAPI, and we'll tell you if we do.
• If part of these terms can't be enforced, the rest still applies. Not enforcing a right straight away doesn't mean we've given it up.
• These terms, with the data processing terms and any order you agree with us, are the whole agreement between us about WalletPassAPI.