THE SERVICES. THE RESPONSIBILITIES. THE DETAILS.
Terms of Service
The platform agreement for accounts, events, business tools, Chat, Mail and official apps, with product-specific obligations and consumer protections.
- Reviewed
- Approved month
- February 2026
- Effective
- 2026-11-16
- Status
- effective
4th Floor 20 Fenchurch Street London EC3M 3BY United Kingdom
Country of establishment: United Kingdom
support@pullup.atAT A GLANCE
- The actual offer and checkout identify what you are buying.
- Features, permissions and billing channels have different limits.
- A later webpage does not rewrite an accepted purchase or mandatory consumer rights.
A reading guide. Read the full clauses for their conditions and scope.
On this page
Use your browser’s Find control to search the full text on mobile.
1. Agreement, scope and operator
One platform agreement, with transaction and product-specific detail.
These Terms govern the official Pullup services that link to them: the website/account, discovery and ticket tools, hosting and services, workspaces, Chat, Mail, official support and mobile applications. The operator’s legal name, business address and country are displayed with the effective revision. Pullup is the service name; we, us and our refer to that operator.
An organiser’s offer, provider booking terms, processor checkout, external accommodation booking, app-store purchase or separately signed business agreement can also apply to its part of a transaction. Unless expressly identified as the provider, Pullup is not the organiser of every listing or party to every external contract.
An account or acceptance flow can record agreement. Acceptance by use applies only where legally effective. A draft or future revision is not already effective. Earlier published notices remain available through the Legal centre.
Privacy, optional cookies/marketing, AI permissions and sensitive-data choices are not all authorised by accepting these Terms. Their applicable notices and separate choices remain relevant.
2. Offers, precedence and material changes
Mandatory law and the accepted offer matter.
Mandatory law takes priority. Subject to it, expressly agreed transaction-specific terms or a signed business agreement govern their particular subject, with applicable product terms and these Terms governing the wider service. A third party’s agreement governs its independent service, not an unrelated Pullup function.
Review the seller/provider identity, event/service, date/time, location/disclosure rules, inclusions, restrictions, total price/currency, fees/taxes, recurring period and cancellation conditions before paying. A demo, marketing summary or estimated dashboard figure is not a substitute for the offer you accept.
We may change services/Terms for product development, law, security, provider changes or commercial administration. Material changes require the notice or renewed acceptance that law and the existing agreement require. A price or policy does not apply retroactively merely because a page changes.
Changes do not remove an accrued claim, mandatory right, refund entitlement or express purchase promise. If an ongoing paid service is materially affected, the notice explains the effect and available lawful remedies. A new data purpose requiring consent needs its own valid choice.
3. Eligibility, age and authority
An account does not authorise every event or organisational action.
The published account services are intended for adults aged 18 or over. You must also satisfy local law and event, venue, service, payment and feature-specific restrictions. Do not use another person’s account to evade an eligibility restriction.
You must have authority to act for a business, organiser or workspace and to use its information/payment instructions. Staff act within assigned permissions; friendship, community membership or a ticket does not grant administration powers.
A purchaser or submitter providing another attendee’s information needs the appropriate authority and permissions. The actual attendee remains subject to lawful admission conditions.
Verification results or age bands are limited process indicators. They do not replace the law, a venue’s checks or accurate information. A feature may require proportionate verification or be unavailable when eligibility cannot be established.
4. Accounts and security
Protect the account, devices, keys and recovery material.
Keep information accurate enough to deliver necessary notices, provide services and administer payments. Do not impersonate another person, misrepresent a business, sell an account or share an owner login to bypass staff roles.
Protect passwords, passkeys, codes, sessions, recovery links, device keys and ticket credentials. Review access when staff or devices change. Report suspected compromise without including the secret in the report.
Official subdomains can use a shared Pullup session. Product sign-out, shared account sign-out, local data removal and session revocation are distinct. Closing a browser, deleting an app or removing a shortcut does not cancel a subscription or erase server records.
We can investigate suspicious use and require proportionate checks. An account holder is not automatically responsible for a platform security failure or every unauthorised act regardless of fault; applicable law, the agreement and the facts determine responsibility.
5. Platform role and availability
Descriptions do not prove live availability on every release.
Pullup provides software to discover/administer events and services, communicate and handle related workflows. Unless expressly identified in the offer, it is not the venue operator, event organiser, personal service provider or guarantor of another business’s performance.
Features vary by role, plan, device/app version, geography, eligibility, permissions and deployment. A repository, prototype or test screen is not proof of a live, approved or generally available service.
We aim to operate reliably but do not promise uninterrupted access, exact delivery timing, permanent storage or compatibility with every device. Technical and provider failures can affect service; express paid-service promises and mandatory remedies still apply.
Test and live modes must not be confused. A pending operation or ledger entry is not confirmation of completed payment, delivery, attendance or settlement. Keep appropriate authorised business copies and recovery backups.
6. Listings, organisers and service providers
Publish an accurate offer and fulfil it lawfully.
Providers must accurately identify and describe their offer, have authority to operate it and meet applicable licensing, insurance, safety, capacity, admission, accessibility and consumer-information duties. State material restrictions, dates/times, inclusions, location conditions and the price accurately.
Do not publish an event you cannot operate, a misleading tier, unauthorised branding or a concealed material limitation. A badge or discovery listing is not certification that all facts or legal obligations have been independently checked.
Communicate material changes and honour lawful cancellation/refund obligations. Editing a schedule in a dashboard or preparing an AI change does not necessarily notify every affected guest.
Organisers remain responsible for staff and on-site operations. Scanner, incident and support software do not replace qualified personnel, emergency arrangements, professional judgement or safeguarding duties.
7. Orders, tickets, admission and credentials
Payment, entitlement and admission state must be checked separately.
A purchase/reservation can depend on payment, availability, verification or approval. A checkout screen, attempted payment, claimed bank transfer or pending order is not by itself a valid entitlement.
Tickets can be locked, unpaid, cancelled, refunded, transferred, used or otherwise ineligible despite an old screenshot. Current validation and the applicable offer govern use. Report apparent errors before attending where reasonably possible.
Protect QR, claim and ticket links. Do not duplicate a sale, alter a pass or use another person’s entitlement contrary to its conditions. Sharing a credential can reveal information or allow someone else to act on the ticket.
Admission remains subject to lawful venue/event rules, age, safety and capacity. A verified account does not independently guarantee entry. Refusals must still respect applicable consumer and equality rights.
8. Seats, rooms, queues and holds
A selection or queue position is not an indefinite guarantee.
Temporary holds may expire when their time ends, payment fails, verification fails or checkout is abandoned. A selection does not indefinitely reserve stock or fix a price before an accepted offer.
Do not manipulate holds, use bots/multiple accounts to evade limits or interfere with another purchaser. Invalid holds can be released and misuse restricted, while rights already acquired in a completed lawful purchase remain relevant.
Waitlists, presales and early access provide what the offer states, not a guarantee of stock or immediate notification. Messages may be delayed; check the sale conditions and current availability.
If payment is taken but an entitlement cannot be supplied, the responsible parties must investigate and provide the remedy required by the offer and law. A technical expiry does not automatically justify retaining the payment.
9. Auctions, event shops and vouchers
A bid, allocation, payment and redemption are distinct.
Before bidding, check the item/ticket, currency, increment/ceiling, closing rule, payment method, payment deadline and any card mandate/consent. Use a lawful public alias; an alias does not conceal the bid from the authorised backend/operator.
A bid can create obligations under the displayed rules. A winning allocation does not prove card collection or bank-transfer approval succeeded, and a pending allocation may not yet be an admission entitlement. Do not shill bid, manipulate timing/inventory, collude or submit false payment proof.
Event-shop purchases and bar vouchers have their own items, quantity, fulfilment and redemption rules. Keep claim/QR credentials private. A used or cancelled entitlement may not be reused; payment confirmation alone does not prove stock has been delivered.
Providers must describe restrictions, redemption period, age requirements and availability accurately and honour required remedies. An auction or voucher label does not itself remove consumer rights or authorise an unlawful regulated product.
10. Prices, fees, currency and taxes
Checkout records the accepted price for the purchase.
Read the final total, currency, fees, tax treatment, recurrence and optional extras before confirming. Prices/allowances can change for future offers but these Terms do not fix an old price forever or replace pre-contract information.
Conversions, forecasts, face values and ledger entries can differ from cleared payments or net settlement. Provider charges, exchange rates and lawful tax adjustments may matter. A fee required to be disclosed before purchase cannot be concealed by a later dashboard adjustment.
Businesses remain responsible for their tax/invoicing/reporting obligations unless a specific task is expressly assigned otherwise. Contact support about a duplicate, unauthorised or incorrectly calculated charge.
Do not misrepresent a transaction to evade a disclosed fee or submit false payment evidence. An abuse restriction does not extinguish a lawful refund or dispute right.
11. Payment methods and processing
An authorisation, submission and cleared transfer are distinct.
Checkout identifies the relevant method/processor and its authentication/security conditions. Earlier or feature-specific transactions may use a different integrated processor or bank-transfer workflow.
Bank transfers can require reconciliation or approval. Use the official destination/reference. A screenshot, claimed payment or internal balance is not evidence that money cleared or was settled to a host.
Payments can be declined, delayed, reversed or require further authentication. Check an uncertain order/provider state before blindly retrying and creating a second purchase.
Labelled test-mode transactions do not take real money or create a claim to live settlement. A payment integration is not authority to sell a product restricted by law or provider rules.
12. Subscriptions, seats, add-ons and renewals
Stopping renewal and refunding a past charge are different operations.
An ongoing offer states its recurring amount, billing period and cancellation conditions before confirmation. It can relate to a host/buyer plan, workspace seat, extra mailbox, email allowance, Chat feature or other benefit. Eligibility can depend on the linked account/workspace.
Cancel through the applicable account, provider or store billing control; contact support if unavailable. Cancellation normally stops the next renewal at the effective time stated in the offer/flow, not automatically an earlier charge or existing obligation.
Trials, introductory prices, metered extras, plan changes and allowance rollover depend on the accepted offer. Do not assume an extra address remains active after the linked entitlement ends or that a store subscription is cancelled by a web-account action.
Mandatory withdrawal rights and express money-back promises remain applicable. An earlier accepted guarantee is not silently removed by a new general policy. Starting digital access does not by itself prove that a required express request, acknowledgement or lawful waiver was obtained.
13. Instalments and staged payments
The displayed schedule governs the locked-ticket workflow.
Eligible checkout can offer staged payment with the total, service fee, amounts and due dates shown before agreement. Eligibility varies by event timing, product, tier, currency and payment conditions.
The current wallet-based flow requires approval of later payments. A reminder is not an automatic debit, and these Terms do not authorise a charge absent from the actual checkout or valid mandate. A different future arrangement must be explained/agreed as required.
A ticket can be created but stay locked until the required balance clears. Locked/incomplete entitlements may not be admitted, transferred or resold. Early or later payments adjust the recorded remaining balance according to their actual outcome.
Missed-payment handling must follow the applicable notices. A reminder alone is not necessarily a formal recovery notice or cancellation deadline. Treatment of amounts paid after non-payment cancellation depends on the lawful offer, circumstances and mandatory rights, not an absolute forfeiture overriding law.
The name instalments does not establish regulatory classification or exemption from financial/consumer-protection rules. These Terms do not claim that every arrangement has identical legal consequences or that a label determines whether regulation applies.
14. Refunds, cancellations and consumer rights
The reason and product matter.
A dated leisure/event booking can have different change-of-mind rights from a recurring digital service or ordinary distance sale. Do not assume a universal 14-day ticket cancellation right, or that a non-refundable label removes rights for cancellation, misdescription, non-performance or other protected reasons.
Organisers must meet the refund duties applying to their events. Postponement, material change or service failure must be considered under the offer/law. A voucher, new date or resale route is not automatically the only remedy.
Use the supported refund form or official support, identifying the purchase/reason without full payment security details. Submitted, approved, pending and completed provider refunds are different states.
The eligible host card-refund flow returns the remaining refundable card amount and adjusts the host ledger, including the actual original processor fee retained as disclosed to the host. Pullup adds no separate refund fee in that flow. This does not authorise an unlawful buyer fee or automatic debit of an external host bank account.
Disputes, reversals and chargebacks can interact. Tell support about parallel processes to avoid duplicate recovery. Processing time varies without removing a right to challenge an incorrect or overdue result. Read the dedicated notice for product distinctions.
15. Earnings, holds, payouts and early release
A ledger is not a bank account or completed settlement.
Gross ticket value, fees, net earnings, pending holds, available balance, advances, requested withdrawals and provider status are different figures. Release rules, minimums, fees and methods are those applicable to the offer/dashboard or settlement agreement.
Post-event release, risk holds, identity checks, reconciliation and disputes can affect access. Early payout has only the eligibility/release treatment actually offered; it is not a guarantee of immediate money or removal of chargeback risk.
A host accepting early release remains responsible for the lawful refund/dispute/reconciliation obligations agreed. Actual fees and the advanced amount must be disclosed. Recovery or offset against future earnings must follow the agreement/law; this does not create an undisclosed bank/card-debit mandate.
Reversals can reduce a ledger or make it negative. Hosts must cooperate with legitimate reconciliation and supply accurate instructions, while retaining the ability to challenge an error and obtain the available record/explanation.
16. Transfers and resale
Only transfer what you are entitled to transfer.
Resale/transfer must be permitted by the entitlement, organiser conditions, platform eligibility and law. Describe the actual ticket, restrictions and price; do not list a used, cancelled, conflicting or unauthorised entitlement.
Completion can invalidate the old credential and assign/issue access to the buyer. An old QR screenshot does not override current state. Payment and transfer can remain pending until provider confirmation and the entitlement update finish.
Fees, refunds and seller proceeds follow the accepted resale offer and supported process. A resale option does not remove an organiser’s separate cancellation duties. A disputed or duplicated payment must not lead to double recovery.
Validation controls reduce specific risks, not all fraud or venue refusal. Use official flows, inspect the current entitlement and report an apparent problem promptly.
17. Stamps, Passport, badges, cosmetics and gifts
Display features are not all the same as money or admission.
These features record/display attendance and customisation. Some are earned, granted, gifted or purchased under their offer; they are not all transferable, redeemable or interchangeable.
A badge does not certify a person’s intentions, legal compliance, venue ownership or guaranteed admission. Providers are responsible for designs and claims they submit. Visibility and moderation affect public display.
Paid cosmetics, coins or gifts must identify their price, quantity, permitted use and restrictions. A displayed balance is not a deposit, investment or cash-redemption promise without an express lawful entitlement.
Store-billed digital purchases have the relevant store billing/renewal/refund relationship. A web cancellation and a store cancellation may be different. Mandatory consumer remedies and purchase promises still apply.
18. Referrals, credits, boosts and host tokens
Use the particular programme and issuing host’s rules.
Qualification, rewards, limits and use follow the displayed programme. Self-referrals, fake accounts/orders, collusion, automated exploitation and retaining an unearned reward after reversing its qualifying purchase are prohibited. A genuine refund/correction can require a reward adjustment.
Promotional credit may be restricted by purchase type, currency, account or expiry, and need not be withdrawable or usable for every service. A boost consumes the allowance described by its offer, not a guarantee of sales or ranking.
Host tokens/reward passes relate to the issuing host and stated programme, not a general cross-host currency or cash claim. Check quantity, price, reward, availability and redemption deadline. Test-mode purchases do not create live proceeds.
Returning tokens is different from refunding money. A host must still supply a promised lawful reward or the required remedy. Do not use these tools for unlawful gambling, cash-prize chance schemes, investments or misleading value claims.
Programme adjustments for error/abuse should be proportionate and open to an appropriate challenge. Future changes do not rewrite an accepted paid offer or remove mandatory rights.
19. Gift cards, memberships and support payments
Check the issuer, benefit and billing channel.
Read who issues the benefit, its recipient/value, redemption rules, recurrence, validity and cancellation conditions. A payment called a donation is not automatically charitable or tax-deductible.
Use only authorised payment credentials and content. Do not misrepresent a campaign or use gifts/memberships to evade provider restrictions. A gift photo/message must be content you may share.
Credit, redemption, membership access and a money refund are distinct. Contact the issuer and support if a promised benefit fails or a payment was duplicated/unauthorised. Earlier promises and mandatory rights remain.
A host membership does not automatically give access to unrelated events, mailboxes, communities or paid platform tools. A badge alone is not proof that a recurring subscription is active.
20. Workspaces and staff authority
Owners allocate access and staff must stay within scope.
Invite the right people, grant necessary permissions and remove access when roles change. Do not share owner credentials, evade role boundaries or export business data for an unrelated purpose.
Calendar, events, guests, scanning, marketing, finance, refunds and sensitive support can have separate powers. A page link does not grant authority, and a calendar read does not authorise a refund or medical-record access.
Notes, budgets, incidents and audit records must be relevant, accurate and lawful. A private field is not an ungoverned health, allegation or criminal-record database.
Leaving a workspace does not automatically erase business records lawfully retained. Organisations remain responsible for privacy, employment, safeguarding, exported records and integrations.
21. Personal data, marketing and sensitive records
A tool does not create permission to use someone’s information.
Businesses must have authority and a lawful basis to collect, use, import/export and share information, give required notices, follow applicable processing terms and limit access/purpose.
Attendance, a booking, following someone or accepting platform Terms is not blanket promotion consent. The sender needs the consent or specific exception applicable to its audience/message, must honour objections and must not disguise marketing as an essential notice.
Optional guest-support/accessibility records may need explicit consent and an additional sensitive-data condition. Acting for another attendee requires appropriate permission. Such optional information must not become a condition of ordinary entry or unrelated marketing.
Use designated private verification/support flows. Do not place identity, medical or confidential records in public artwork or an AI prompt because it accepts text. Duties continue after an export or outside Pullup.
22. Private Chat, devices and calls
Keep keys and understand the limits of clearing and encryption.
Private DMs use device-encrypted envelopes. Communities and support cases do not use the same DM encryption model. Check the Chat notice and destination before posting.
Keep usable keys or a recovery backup if you need history. We cannot promise to reconstruct plaintext after all relevant keys are lost. New device registration, restored keys and approved history transfer can have different effects.
Request/block, receipt/typing, clear and expiry controls affect their stated functions. A local clear need not erase another participant’s view. Expiry does not prevent screenshots, recordings, recipient downloads or backups.
Use required camera/microphone permissions and a suitable connection. Another person can independently record or disclose a call; obtain any recording consent required. Chat is not emergency calling, guaranteed alerts or a guaranteed archive.
23. Communities and official support
A public post is not a private support case.
Operators/moderators manage permitted members, channels, roles, invitations and content. Channels are not end-to-end encrypted, and an authorised participant may copy what they can see.
Do not post ticket credentials, private evidence, identity documents, medical details or third-party allegations in public channels. Official support has a distinct private-case workflow with authorised staff review.
Community rules must respect these Terms/law and cannot authorise abuse, exploitation, discrimination, spam or bypassing controls. Pullup can intervene under its legitimate platform/safety duties.
Do not impersonate staff or another organisation. Verify support through the published link before sharing relevant evidence; unsolicited badges or payment demands do not prove official authority.
24. Pullup Mail
Use only addresses, content and audiences you are entitled to control.
Mail’s enabled sending/receiving, forwarding and organisation rely on backend ownership and activation. The email-address domain and the application hostname are different. Pending or paused state can limit sending/receiving.
Do not send spam, phishing, malware, fraudulent demands, impersonation or unlawful content. Authority for a recipient list and marketing must come from the applicable rules. Safety checks can allow/flag/block and record a result, not guarantee every message is safe or every block correct.
Email is server-processed correspondence, not private Chat encryption. Providers, spam filters, forwarding and recipients affect delivery. A timeout is not proof a send failed; check the result before retrying an uncertain action.
Draft/signature data can be local; saved organisation and reminders can use the backend. Back up essential work. Archiving is not deletion and a reminder is not a guaranteed push. Recovery can import provider records without promising that provider history lasts forever.
Forwarded and external recipient copies remain separate. Optional meaning/answer AI has its own choice and scope; it is not the same process as operational outbound moderation.
25. AI, translation and generated content
Review outputs, evidence and actual saved changes.
AI can explain, translate, interpret a search, generate art, retrieve permitted context or search mailbox excerpts. General help, personal Pilot, optional Mail intelligence and operational moderation have different purposes and choices.
Do not treat outputs as verified legal, medical, financial, safety or admission advice. Check dates, amounts, recipients, permissions and original messages. A citation is not certification that an agreement remains current; sentiment is an estimate.
A prepared assistant change is not saved until the required confirmation succeeds. Personal Pilot cannot approve its own change, refund/pay out money, buy items, send guest mail, delete events or change permissions merely because a prompt asks.
Share only what you may lawfully disclose to the provider. Optional permission does not eliminate duties to guests/correspondents. External image tools can require another account and their own terms/charges.
Review published output and obtain the necessary rights. We do not guarantee originality, factual accuracy, exclusivity, copyright protection or suitability. Depicted people’s rights and required licences still apply.
26. External bookings, maps and integrations
An integrated link does not make every third-party service a Pullup contract.
An accommodation referral can lead to an external provider’s contract. A booking made through Pullup’s own room/service workflow is different; identify the actual offer and provider.
Maps, directions and translations may be inaccurate. Verify important venue/travel details independently. A public description can reveal an address regardless of a separate ticket-location control.
Connected apps and webhooks operate under their authorised scopes. Have authority to connect business data, protect tokens/keys and choose an appropriate recipient. Do not bypass scopes or use an allowed function to retrieve unrelated records.
Provider terms/availability affect the connection. Revocation normally prevents future access, not copies already obtained. Report suspected unauthorised apps, leaks or misuse.
27. Official apps and app stores
App version, billing channel and account state are distinct.
Apps may combine native screens with a protected web/transport layer. Permissions, local storage, push/call services and feature support depend on the app/release. Some functions open a web flow rather than being fully native.
Use supported software and appropriate device security. Declining camera, microphone, photo, location or push access can disable the dependent feature without disabling every other service. Device biometric unlock is not the document/selfie verification process.
Where a store bills an eligible digital purchase, use its relevant cancellation/refund route. Real-world event/services can use an external checkout. Check which merchant/channel took the payment.
A preview/source repository is not a promise of release, app-store approval, every feature or a fixed supported lifetime. Store licences and mandatory paid-service rights remain.
28. Group planning, albums, music and discovery
Shared planning and expressive features need clear permissions.
Group plans, votes, budgets and a calculated wallet help coordinate people. They do not alone make a regulated payment account, reserve every proposed item or confirm an external booking. Verify the actual provider, offer, payment and booked state.
Do not invite people or publish another person's plans/location without appropriate authority. Members may see permitted dates, destinations, votes, budgets and selected booking context; share only what the intended group should receive.
Event albums, recaps, playlist requests/votes, reactions and collected stamps can make content/activity visible to their selected audience. Obtain the necessary rights and consent for people shown, recordings and music use. A music-service connection does not grant an organiser a public-performance licence.
Discovery listings, nearby distances, maps, directions and generated suggestions may be incomplete or wrong. Use location visibility controls knowingly; a recent-activity filter is not a guaranteed erasure timer. Do not use these functions to track, stalk or infer a private home address.
Job application tools administer recruitment and do not guarantee an interview, offer or employment contract. Submit accurate relevant information and avoid unnecessary sensitive details.
29. Content rights and service permission
You keep your rights and must have the rights needed to share.
You retain the rights you hold in submitted content. You grant the non-exclusive permissions necessary to host, store, transmit, display, deliver, format and back up it for the requested service, your visibility choices, necessary safety and legal duties.
For public content this includes the selected public audience and normal listing/sharing functions. For private/encrypted content the function and technical boundaries still apply. This is not a licence to sell private messages or disregard the Privacy Policy.
Respect copyright, trade marks, privacy, publicity, confidentiality and other rights. Obtain necessary rights for photographs, music, art, logos and other people’s content. Neither AI generation nor uploading establishes permission automatically.
Content can be restricted/removed under applicable Terms/law and legitimate rights/safety processes, subject to notice/redress obligations. Termination does not require perpetual public display or permit remote deletion of every independent lawful copy.
30. Acceptable use
The rules apply across public/private products and roles.
No unlawful conduct, exploitation, child sexual abuse material, threats, harassment, hate/unlawful discrimination, non-consensual intimate content, doxxing, phishing, malware, fraud or unauthorised access. Encryption and community privacy do not exempt prohibited conduct.
Do not scrape/republish personal data without authority, flood mail/channels, manipulate orders/queues/rewards, evade blocks/permissions, falsify verification, impersonate support or expose someone’s credentials. Security testing requires appropriate lawful authorisation.
Respect privacy and marketing objections. Do not use sensitive event/support records for unrelated profiling. A good-faith complaint, lawful criticism, legitimate payment dispute or privacy request is not prohibited abuse.
The detailed Acceptable Use Policy explains reporting, review and proportionate enforcement.
31. Restrictions, reports and appeals
Address the actual risk and allow the applicable review.
We may restrict content, a feature, transaction or account where reasonably necessary for safety, credible abuse, contract enforcement or law. Restrictions can be temporary or scoped. A venue/community decision can be separate from a platform restriction.
Where appropriate/permitted we explain the reason, scope and challenge route. Urgency, a legal prohibition or an investigation can limit notice/explanation without creating a blanket right to ignore mandatory duties.
Use the relevant account-status/report/support workflow with accurate, relevant evidence. Do not fabricate reports or use them to harass or gain improper advantage.
A pending appeal need not restore a risky function immediately. A restriction does not by itself extinguish a lawful refund, payout, privacy or complaint right. Ask for review of an incorrect automated outcome or administrative error.
32. Ending access and account closure
Closure, subscription cancellation and erasure are separate.
Use the account-deletion control or support to request closure. Cancel renewals in the applicable billing channel. Deleting an app or clearing cookies does not itself cancel a subscription.
The workflow can deactivate access and schedule deletion after the stated grace period, currently 30 days, with reactivation in that period. Outstanding transactions, shared records, lawful retention and technical completion still need handling.
Save the records and usable key backups you are entitled to keep before losing access. Secure the resulting files. Encrypted content is not guaranteed recoverable without usable keys.
Earlier legitimate settlement, refund, confidentiality, record-keeping and consumer-remedy duties can survive termination. Retention and restrictions must still comply with law and the agreement.
33. Support and necessary communications
A response or approval is not necessarily a completed financial outcome.
Use official support or support@pullup.at. Any priority/service level follows the actual offer, not a guarantee of immediate resolution or emergency response.
Case replies, proposals, approvals, provider authorisations and ledger adjustments can precede a final refund/payout/delivery. Check the completed status and ask about an ambiguity. A normal community post is not automatically a private case.
Keep a usable contact method for necessary security, booking, billing and service/policy messages. Marketing/notification choices remain separate where the purpose/law requires.
These Terms do not force support as a prerequisite to a statutory right where another lawful route is available. Tell us about parallel disputes to avoid duplicated outcomes.
34. Standards, limits and mandatory rights
Broad disclaimers do not waive rights the law protects.
We provide the care required by law and an express agreement. We do not guarantee a third party’s event, exact delivery, every AI output, uninterrupted service or protection against every possible incident. These limits do not remove a remedy owed for our own breach.
Nothing excludes liability that cannot lawfully be excluded, including fraud/fraudulent misrepresentation, death/personal injury caused by negligence where exclusion is prohibited, or mandatory consumer rights.
Consumer compensation restrictions must be fair and consistent with the applicable remedies. Describing technical limits does not waive reasonable-care duties, a contractual refund or legally required compensation.
For business use, any lawful allocation of indirect/consequential business loss remains subject to the agreement and facts. A signed business agreement may set additional lawful terms. This public revision does not invent a universal money cap or indiscriminate consumer indemnity.
35. Law and dispute routes
Mandatory protection is not displaced by a platform label.
The operator’s establishment is shown with the effective revision. Applicable law follows the contract and relevant legal rules; mandatory protection may apply because of the consumer’s location, service or transaction even if another law is chosen lawfully elsewhere.
Nothing requires a consumer to surrender a mandatory local court, regulator or statutory remedy. This public revision does not impose mandatory arbitration, an exclusive foreign court or an unlawful waiver of representative remedies.
Another organiser/provider/store can have a route for its own part of the issue. Contacting one party does not automatically resolve another’s duties or extend a legal deadline.
Ask support to investigate with relevant references. Exercising a genuine right is not itself abusive conduct.
36. Remaining provisions and contact
Summaries help navigation; the full agreement and mandatory law still matter.
If a provision cannot be enforced, the remainder applies only so far as it can lawfully and fairly operate. A delay is not automatically a permanent waiver. We do not use severability to rewrite an unfair consumer term more broadly than allowed.
Do not transfer an account/contract to evade eligibility, security or payment duties. A lawful business transfer must respect relevant contract, consumer and privacy obligations.
Headings, cards and summaries do not hide qualifications or override mandatory law. If a summary and accepted transaction record conflict, seek clarification rather than assuming a later page silently changes a purchase.
Contact support@pullup.at or official private support for Terms questions, and identify privacy requests as such. Never publish passwords, codes, identity images or full payment details in a public channel.
COMMON QUESTIONS
A little more clarity.
Do Terms provide every privacy permission?
No. Marketing, optional storage, personal AI and sensitive processing can require their own choices and lawful conditions.
Can a later policy change an accepted purchase?
A webpage change alone does not rewrite it. The actual offer, lawful change process and mandatory rights apply.
Is an approved refund already in my bank?
Not necessarily. Request, approval, provider processing and completed return are separate states.