TicketTuck

Terms of Service

Last updated: October 10, 2026 · Version: 2026-10-10

TicketTuck is in beta. We may update these terms as we finalize them; we’ll tell you about material changes by email or in the app.

These terms are for organizations (colleges, schools, churches, nonprofits, venues and businesses) that use TicketTuck, and for the staff who use it on their behalf. If you bought a ticket, registered or donated on an organization’s page, these terms aren’t for you: you bought from that organization, under its own terms, refund policy and privacy policy. Our Privacy Policy explains how we handle your information.

1. Who we are and what this agreement covers

1.1 We’re TicketTuck (“TicketTuck”, “we”, “us”). We provide hosted, branded web pages for events, tickets, registrations, fees and donations, along with checkout, receipts, reporting, refunds and an event-day app for check-in and door sales (the “Service”).

1.2 These Terms of Service (the “Terms”) are an agreement between TicketTuck and the organization that uses the Service (“Organization”, “you”). The person who accepts these Terms for an Organization confirms that they have authority to bind it.

1.3 These documents are part of these Terms:

1.4 When your Organization’s first admin signs up, they accept these Terms for the Organization, and we record the version and the time. If we make a material change, we may ask an admin to accept the new version.

2. Definitions

3. Accounts and security

3.1 Staff accounts. Your admins invite Staff Users and choose their roles: admin (everything, including brand settings, team, refunds and payment applications), editor (build and publish pages, see sales, sell at the door) or viewer (see pages, sales and exports). Our servers enforce these roles.

3.2 Your responsibility. You are responsible for everything done through your Staff Users’ accounts and through any volunteer door links you create. Keep passwords confidential. Remove access promptly when someone leaves. Tell us at security@tickettuck.com if you suspect unauthorized access.

3.3 Two-step sign-in. Every Staff User can turn on two-step sign-in (an authenticator app plus one-time recovery codes). We strongly recommend it for admins. TicketTuck’s own administrators are required to use it.

3.4 Door links. An editor can create a link that lets a volunteer scan tickets for one event, and sell at the door if the editor allows it, without an account. Door links stop working the day after the event and can be turned off at any time. You are responsible for who you give them to.

3.5 Eligibility. Staff Users must be at least 18 years old. You may not use the Service if the law or a Processor bars you from doing so.

4. The Service

4.1 What we provide. We host your Pages and run checkout. We send receipts and refund notices to Buyers on your behalf. We provide sales reports and exports, a refund tool, and the event-day app (scanning, guest list, door sales and stats). Our pricing page and the Studio describe current features and plan limits.

4.2 Content we prepare for you. On some plans we build pages for you, for example a “starter catalog” of a year’s events, or done-for-you setup. These pages are drafts that we prepare from public sources and your input. They may include estimated prices, dates or details, and stand-in photos. You must review every page before you publish it, and you are responsible for what you publish. Replace stand-in photos with images you have the right to use.

4.3 Changes to the Service. We improve the Service continuously, and we may add, change or remove features. If we remove a feature that is central to your paid plan, we’ll give you at least 30 days’ notice. If the change materially reduces what you paid for, you may cancel and get a pro-rata refund of prepaid fees.

4.4 Test purchases. Before card payments go live, staff can make test purchases from a draft page’s preview link, using the Gateway’s test mode. Test purchases never charge a real card. Test orders are labeled as tests, never count as sales, and their tickets are never valid at the door.

4.5 Beta. TicketTuck is in beta. Features may change more often than they will later, and we may update these Terms as we finalize them (Section 19).

5. Plans, fees and billing

5.1 Plans. We offer four plans:

Plan Plan fee Card payments Card processing rate (charged under your Merchant Account)
Free $0, no card needed No (free events, RSVPs and complimentary tickets only) Not applicable
Starter $49/month or $490/year Yes 2.9% + 30¢ per transaction
Pro $99/month or $990/year Yes 2.7% + 30¢ per transaction
Institution Set out in your order form Yes Custom, set out in your order form and your Merchant Agreement

TicketTuck never adds ticket fees to your Buyers’ purchases. Each plan has limits, such as team members, deposit accounts, custom web addresses and reports, and our servers enforce them. Plan fees don’t include taxes (Section 5.7).

5.2 Free plan. The Free plan has no fee and no time limit, and you don’t need a card to use it. It runs free events, RSVPs and complimentary tickets. It doesn’t take card payments, so a page that charges money can’t be published on Free. We may change Free plan features with 30 days’ notice. We’ll never start charging a Free account without your agreement. If a Free account has had no sign-in for 24 months, we may close it, but only after emailing your admins at least 60 days ahead and giving you a chance to export your data.

5.3 Paid plan fees. Starter and Pro fees are billed in advance, monthly or yearly. You authorize us to charge your card on file for each renewal until you cancel. Your card is stored in our Gateway’s secure vault (the NMI Customer Vault). TicketTuck never receives or stores your full card number; we keep only the card brand, the last four digits and the expiry date. Institution fees, and any setup fee, are invoiced as set out in your order form. Unless your order form says otherwise, invoices are due within 30 days.

5.4 Upgrades. An upgrade takes effect right away. A new billing period on the new plan starts that day, and we charge the new plan’s price for it. Time left on your old plan isn’t credited. The new card processing rate applies to transactions after your Processor updates your Merchant Account pricing, which can take a few business days.

5.5 Downgrades. A downgrade, or a switch between monthly and yearly billing, takes effect at the end of your current billing period. Features beyond the new plan’s limits stop or can’t be added. For example, extra deposit accounts can’t take new payments, a custom web address stops serving your pages, and new team invitations beyond the limit are blocked. Your data is kept.

5.6 Renewals and price changes. Paid plans renew automatically for the same term until you cancel. We’ll give you at least 30 days’ notice of a price increase, and it takes effect at your next renewal. For yearly plans, we’ll also send a reminder before the renewal date.

5.7 Taxes. Fees don’t include taxes. You are responsible for any sales, use or similar taxes on our fees, except taxes on our income. If you are tax-exempt, send us your exemption certificate.

5.8 Failed payments. If a renewal payment fails, we’ll email your admins and try again 1, 3 and 7 days after it was due. You can update your card at any time, and if a payment is overdue we’ll charge the new card right away. If the last try fails, your Organization moves to the Free plan:

Choose a plan again at any time to turn payments back on. We don’t charge you for the time you spent on Free.

5.9 Off-season rate. If you’re on Starter or Pro and billed monthly, you can switch to the off-season rate of $25/month between seasons, for 1 to 6 months at a time. It starts at your next renewal. During the off-season, card payments are off and your Organization has the Free plan’s features, but your Pages stay visible, free events keep working, your data is kept, and your deposit account stays open, so you’re ready for next season. When the off-season ends, your plan comes back and is charged at its normal price. You can end the off-season early; your plan then comes back that day and is charged from that day.

5.10 Cancellation. You may cancel a paid plan at any time in the Studio or by emailing support@tickettuck.com. Cancellation takes effect at the end of the current billing period, and your Organization then moves to Free. If a payment is overdue when you cancel, the plan ends right away. If you want your account closed and your data deleted, rather than moved to Free, tell us (Section 12.4).

5.11 Refunds of plan fees. Monthly fees aren’t refundable. If you cancel a yearly plan within the first 30 days of a new yearly term, email us and we’ll refund the unused months, pro rata. Setup fees aren’t refundable once setup work has started. We also refund prepaid fees pro rata where these Terms say so (Sections 4.3, 12.2 and 19).

5.12 Billing disputes. Tell us within 60 days of a charge if you believe it’s wrong. We’ll work with you in good faith.

6. Payments to your Organization

In short: card payments go to your own Merchant Account, and TicketTuck never holds your money.

6.1 Your Merchant Account. Card payments on your Pages are processed under a merchant agreement between your Organization and the Processor (your “Merchant Agreement”). The Gateway connects the Service to your Merchant Account, and funds settle directly from the Processor to your bank account. TicketTuck isn’t a party to your Merchant Agreement. TicketTuck isn’t a payment facilitator, payment aggregator or money transmitter, and it never receives, holds or controls the funds your Buyers pay.

6.2 Applying for a Merchant Account. On paid plans we help you apply. You give us business information in the Studio, and we pass it to the Processor. The Processor decides whether to approve you, and sets any underwriting conditions, reserves, holds and termination terms under your Merchant Agreement. We can’t guarantee approval or timing. Owners’ Social Security numbers, dates of birth and bank details go directly on the Processor’s own secure application; the Studio doesn’t collect them.

6.3 Our role and compensation. TicketTuck refers Organizations to the Processors we work with. TicketTuck receives compensation from the Processor in connection with your Merchant Account, which may include part of the card processing fees you pay.

6.4 Gateway keys. To take payments, you (or we, at your request) enter your Gateway keys in the Service. Each key belongs to one Merchant Account, and you may have separate keys for department accounts where your plan allows. You authorize TicketTuck to store these keys and use them for four purposes only:

We encrypt security keys separately from the rest of our database. We never show a key again after it’s saved; staff see only its last four characters. We never send a payment to any account other than the one assigned to the page, and a refund always goes back through the account that took the payment.

6.5 Your payment responsibilities. You are responsible for:

6.6 Processing fees and other Processor charges. The Processor charges card processing fees under your Merchant Agreement, usually by deducting them from your settlements. Our pricing page shows the rate for your plan. Other Processor fees, such as chargeback fees, apply as stated in your Merchant Agreement.

6.7 No ticket fees. TicketTuck doesn’t add service, convenience or ticket fees to your Buyers’ purchases. If you choose to charge Buyers a fee of your own, you must include it in the total price shown from the start, as the law and card network rules require. Card surcharges carry extra network and state-law rules, so don’t add one without checking with your Processor.

6.8 Uncertain payments. Sometimes the bank doesn’t answer during checkout. When that happens, the Service tells the Buyer not to pay again and checks the payment with the Gateway automatically, every few minutes. Once the Gateway confirms it, the Service either completes the order and sends the receipt, or tells the Buyer they weren’t charged. We aren’t responsible for outages or errors at the Gateway, the Processor, the card networks or the Buyer’s bank.

6.9 Tax forms for card sales. Any Form 1099-K for your card sales comes from your Processor, not from TicketTuck.

6.10 Embedding pages. We recommend linking to your Pages from your own website. If you choose to show a Page inside another website (admins can list allowed sites in the Studio), you are responsible for the security of that website. Embedding a payment page can change what your Processor expects of you for card security, so check with your Processor first.

7. Your events, your Buyers and your responsibilities

7.1 You are the seller. For every Page, you are the seller, organizer or recipient of the payment. Buyers contract with you, not with TicketTuck. You set prices, terms, refund policies and capacity. You deliver what you sell, and you handle cancellations, postponements, refunds and Buyer questions.

7.2 Information on paid pages. Before a page that takes money goes live, you must add a real support email and your refund policy in the Studio; the Service won’t publish a paid page without them. You must also add, in the Studio, your Organization’s address including country (it appears on receipts) and links to your own terms of sale and privacy policy (they appear at checkout).

7.3 Refunds. You decide your refund policy and apply it. The Studio’s refund tool cancels tickets, and voids or refunds card payments through your own Merchant Account. If the Gateway refuses a refund, nothing changes. If the Gateway doesn’t answer, the Studio tells your staff to check with the Gateway before trying again. TicketTuck doesn’t fund refunds.

7.4 Taxes on your sales. You are responsible for deciding whether sales, admissions, amusement or other taxes apply to what you sell, and for collecting and paying them. The Service doesn’t calculate taxes. For donations, you are responsible for the correct acknowledgment and tax-receipt wording (for example, quid pro quo disclosures) and for any charitable-solicitation registrations. The Service gives you a receipt note field for this wording.

7.5 Laws that apply to your events. You are responsible for complying with the laws that apply to your events and sales, such as ticketing and price-display laws, consumer protection law, raffle and gaming law, alcohol law, laws about events for minors, and accessibility law for your own content.

7.6 Buyer Data. For Buyer Data, you are the controller and TicketTuck is your processor or service provider, as set out in the DPA. You must:

7.7 Organization Content. You are responsible for your Organization Content. You confirm that you have the rights to use it, including logos, photos, music and video, and other people’s names and images. You confirm that event details are accurate and that your content follows the Acceptable Use Policy.

8. Acceptable use

You must follow the Acceptable Use Policy. In particular, you may use your Pages and Merchant Account only to take payments for your own Organization’s events, programs, fees and donations, not on behalf of others. Your Processor’s prohibited-business list also applies to you.

9. Data protection and privacy

9.1 Buyer Data, and Staff User data we process for you, is governed by the DPA. We use it only to provide the Service to you, as you instruct. We don’t sell it, and we don’t use it to market to your Buyers.

9.2 Data we handle for ourselves is covered by our Privacy Policy. This includes your staff’s TicketTuck accounts, billing contacts, inquiries and security logs.

9.3 Aggregated data. We may create aggregated, de-identified statistics from use of the Service, such as total ticket fees avoided across all customers, and use them to operate, improve and promote the Service. They never identify you, your Buyers or any individual, and we won’t try to re-identify them.

9.4 Security. We keep administrative, technical and physical safeguards appropriate to the data we handle, as described in the DPA and on our Security page. If we confirm a breach affecting your data, we’ll tell your admins without undue delay, and within 72 hours.

9.5 Support access. A small number of TicketTuck administrators can access your account to support you and keep the Service running. When one of them views your Buyer Data, it shows in your activity log.

10. Suspension

10.1 We may suspend your Pages’ ability to take payments, or your access to the Service, if we reasonably believe that:

10.2 When we suspend an Organization, card payments stop immediately. Pages normally stay visible with a notice, but we may take down a Page that is unlawful or harmful. Where practical and lawful, we’ll tell you why in advance, or promptly afterward, and work with you to fix the problem.

10.3 Non-payment of plan fees doesn’t lead to suspension. It moves your Organization to the Free plan (Section 5.8).

11. Your content and our intellectual property

11.1 Yours. You own your Organization Content and your Buyer Data. You give TicketTuck a worldwide, non-exclusive, royalty-free license to host, copy, display, adapt (for example, resize images or format pages) and send it, only as needed to provide the Service and as these Terms describe.

11.2 Ours. TicketTuck owns the Service, including its software, page styles and designs, templates, starter catalogs (other than your Organization Content in them), the event-day app, documentation and our trademarks. These Terms don’t transfer any of our intellectual property to you. You may use the Service only as these Terms allow. You may not copy, resell or reverse engineer it, except where the law allows despite this restriction.

11.3 Custom design. If you pay us to design custom pages, you own the final page content and the assets you supply. TicketTuck keeps the rights to the underlying code, templates and reusable design elements, and gives you a license to use them with the Service. A separate statement of work may say otherwise.

11.4 Customer references. We may list your Organization’s name and logo as a customer. Tell us if you’d rather we didn’t, and we’ll stop.

11.5 Feedback. If you send us suggestions, we may use them without any obligation to you.

12. Term and termination

12.1 These Terms apply from the time you accept them until your account is closed.

12.2 Ending the agreement.

12.3 When your account closes, your Pages stop being published and card payments stop. Pending refunds should be completed first.

12.4 Your data after closing. Before we close your account, we’ll give you a full export on request: your pages, images, orders, check-ins and activity log. For 30 days after closing, you can still ask us for it. After that, we delete or de-identify your Organization Content and Buyer Data within 60 days, unless the law requires us to keep something. Deleted data leaves our database backups within 30 days. Two records stay: your activity log, for 12 months after closing (card-security rules require a year of security logs), and our invoices for your plan, for as long as tax and accounting law requires.

12.5 Sections 5 (for amounts owed), 6.5, 7, 9, 11, 12.4 and 13 to 21 survive the end of these Terms.

13. Third-party services

The Service relies on third parties: Cloudflare (hosting, database, storage and bot checks), NMI (the Gateway), your Processor, and Resend (email delivery). Our subprocessor list names them. Your Merchant Agreement governs your relationship with your Processor and the Gateway. We aren’t responsible for third-party services we don’t control, but we remain responsible for our subprocessors as the DPA describes.

14. Confidentiality

Each party will protect the other’s non-public business information with reasonable care, and use it only for this agreement. This doesn’t cover information that is public, already known, independently developed or rightly received from someone else. Either party may disclose information when the law requires it, with notice where lawful. We respect public institutions’ obligations under open-records laws (Section 21.4).

15. Warranties and disclaimers

15.1 Each party confirms that it has authority to enter into these Terms.

15.2 We’ll provide the Service with reasonable skill and care, substantially as described in our documentation.

15.3 Except as these Terms say, the Service is provided “as is” and “as available.” To the extent the law allows, TicketTuck disclaims all other warranties, express or implied, including merchantability, fitness for a particular purpose and non-infringement. We don’t promise uninterrupted or error-free service, that a Processor will approve you, or any level of sales. We don’t give tax, legal or accounting advice, and the Service’s reports and receipt wording aren’t advice.

16. Limitation of liability

16.1 No indirect damages. Neither party is liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, goodwill or data, even if it was told they were possible.

16.2 Cap. Each party’s total liability under these Terms is limited to the fees you paid TicketTuck in the 12 months before the claim. For Free plan accounts, the cap is $100. An Institution order form may set different limits.

16.3 Exceptions. The limits in 16.1 and 16.2 don’t apply to:

16.4 Card payments your Buyers make are not fees paid to TicketTuck, and they don’t count toward the cap.

17. Indemnity

17.1 By you. You will defend TicketTuck against third-party claims arising from:

You will pay any resulting damages and reasonable costs that a court awards or that you agree to in a settlement.

17.2 By us. We will defend you against third-party claims that the Service, as we provide it, infringes a U.S. patent, copyright or trademark, or misappropriates a trade secret. We will pay any resulting damages and reasonable costs that a court awards or that we agree to in a settlement. This doesn’t apply to claims caused by your Organization Content, or by combinations or changes we didn’t make.

17.3 Process. The party asking for indemnity must give prompt notice, reasonable cooperation and control of the defense. The indemnifying party may not settle in a way that admits fault for the other party without its consent.

17.4 Public institutions. If state law prohibits your Organization from giving an indemnity, Section 17.1 applies only to the extent that law allows. Your order form may say more.

18. Governing law and disputes

18.1 These Terms are governed by the laws of the state where TicketTuck’s operating company is organized, without regard to conflict-of-laws rules.

18.2 Before either party files a claim, we’ll both try in good faith to resolve the dispute for 30 days, starting from written notice.

18.3 Disputes go to court, not arbitration. The state and federal courts located in the county where TicketTuck’s principal office is located have exclusive jurisdiction, and both parties agree to their jurisdiction.

18.4 If your Organization is a public institution, its required governing-law and venue terms apply if they are set out in its order form.

19. Changes to these Terms

19.1 We may update these Terms. For a material change, we’ll give at least 30 days’ notice, by email to your admins and in the Studio, before it takes effect. If you don’t agree to the change, you may cancel before it takes effect and get a pro-rata refund of prepaid fees for the rest of your term. Otherwise, continuing to use the Service after the effective date means you accept the change.

19.2 We may make changes that the law or a Processor requires, or that don’t reduce your rights, on shorter notice.

19.3 Changes don’t apply to an Institution order form’s current term unless the order form allows them; they apply from its next renewal.

20. Notices

We send notices by email to your account admins and, where relevant, in the Studio. Send legal notices to TicketTuck at support@tickettuck.com, with “Legal notice” in the subject line. We’ll send our mailing address on request.

21. General

21.1 Assignment. Neither party may assign these Terms without the other’s consent, except to a successor in a merger, acquisition or sale of substantially all of the relevant business, with notice.

21.2 Force majeure. Neither party is liable for delays caused by events beyond its reasonable control, such as outages at internet or cloud providers, card network or bank outages, natural disasters or government action. This doesn’t excuse payment obligations.

21.3 Order of precedence. If documents conflict, this order applies: (1) a signed order form, (2) the DPA (for personal data), (3) these Terms, (4) the Acceptable Use Policy, (5) other policies.

21.4 Public institutions. If your Organization is a public entity, its required contract terms apply to the extent set out in a signed order form or addendum. Examples include open-records obligations, limits on indemnities, appropriations or fiscal-funding clauses, and sovereign immunity.

21.5 Relationship. The parties are independent contractors.

21.6 Entire agreement. These Terms, with the documents in Section 1.3, are the whole agreement on this subject. A waiver must be in writing. If any part of these Terms is unenforceable, the rest still applies. Electronic acceptance and signatures are binding.

21.7 Export and sanctions. You confirm that you aren’t on a U.S. sanctions list, and that you won’t use the Service where U.S. law prohibits it.

Contact

TicketTuck · support@tickettuck.com. We’ll send our mailing address on request.