Skip to legal content
pullup Legal centre Back to Pullup
All documents/Privacy Policy

YOUR INFORMATION. IN CONTEXT.

Privacy Policy

How information moves through Pullup, who can see it, why we use it, and the choices and rights available to you.

Revision 2026-11-1626 min read30 sections
Reviewed
Approved month
February 2026
Effective
2026-11-16
Status
effective
pullupat

4th Floor 20 Fenchurch Street London EC3M 3BY United Kingdom

Country of establishment: United Kingdom

support@pullup.at

AT A GLANCE

  • Private Chat, communities and email have different privacy boundaries.
  • Optional AI permissions are separate from operational safety checks.
  • Account closure, content expiry, recipient copies and backups have different lifecycles.

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. Scope and the responsible operator

One notice for the connected services, with product-specific detail.

This notice applies to Pullup accounts, the website, discovery, tickets, hosting and service tools, workspaces, support, Pullup Chat at chat.pullup.at, Pullup Mail at inbox.pullup.at and any mail.pullup.at address officially designated for that product, and official mobile apps linking to this notice. The domain of an email address is separate from the hostname of a web application. Use the product links supplied by Pullup to access your account.

The operator information displayed with this revision identifies the organisation responsible for Pullup’s own processing. Pullup, we, us and our refer to that operator. Our privacy contact is support@pullup.at. Hosts, venues, service providers, workspace administrators, payment providers and external booking services may have their own responsibilities and privacy notices.

A feature is described when available, not promised on every account or release. Availability depends on role, permissions, country, device, subscription, event settings and deployment. Read the product notices alongside this policy.

Accepting Terms, choosing cookies, enabling optional AI, authorising an integration and consenting to sensitive processing are different decisions. Reading or accepting this notice does not itself consent to every activity.

2. Controllers, hosts and workspaces

Responsibility follows the activity, not just the location of a record.

Pullup generally determines the purposes and means of running accounts, authenticating users, operating its platform, administering its own subscriptions, maintaining necessary safety/transaction records and meeting its own legal obligations. For those activities it acts as a controller or equivalent responsible business.

A host or provider generally decides why it collects guest, booking, customer or business information for its event or service. Pullup may process that information on its instructions to provide tools, while separately using relevant records for its own necessary security, billing and legal purposes. The actual processing and applicable agreement determine the roles; using Pullup does not transfer all of a host’s responsibilities to us.

Workspace owners allocate access through roles and permissions. Calendar, finance, refunds, guest lists, scanner access, support and sensitive guest-support functions can have different permissions. Membership of a workspace does not mean every member sees every record. A business mailbox’s private notes are still records in that mailbox.

If a request concerns a host’s own use, contact the host as well as Pullup. We can identify the relevant records, coordinate and assist where required. A payment or booking provider may need to answer about information it controls independently.

3. Sources and required information

Data can come from you, another person, a business or a connected service.

We receive information through registration, sign-in, profiles, purchases, bookings, listings, messages, uploads, reports, verification, camera/microphone functions, connected services and support. Technical information also arises when a device and service communicate.

Others may supply information about you: a purchaser can name a guest, an organiser can add an attendee or door note, a workspace can invite a colleague, a correspondent can email you, and an attendee can submit content or a report. Suppliers of information must have authority and any permissions required, especially for another person’s sensitive details.

Providers can return payment/delivery status, permitted account details, import records or security information. Public event information can come from a listing or submitted link. Where information was obtained indirectly, you can ask about its source, subject to lawful protections for other people, investigations and security.

Required fields are identified in the relevant flow. Not providing information necessary to authenticate, fulfil a purchase or operate a requested feature can prevent it working. Optional information should remain optional. Do not put passwords, full card data, authentication codes or usable ticket QR credentials into public posts or general support messages.

4. Categories of information

The fields depend on the functions you actually use.

4. Categories of information
CategoryExamples and context
Account and authenticationAccount ID, email, name/username, password hash, provider identifiers, email-verification status, sessions, passkeys, authentication factors and account settings.
Profile and socialAvatar, banner, bio, links, follows/friends, public badges, cosmetics, profile visibility, Passport and account-age display choices.
Listings and businessEvent/service details, venue, dates, calendars, tier/seat/room settings, workspace members and permissions, budgets, operational notes and audit records.
Booking and accessGuest/purchaser information, order and ticket references, payments/eligibility, selected options, QR validation information, check-ins, transfers and redemptions.
Financial and rewardAmounts/currency, provider references, invoices, subscriptions, instalment schedules, payout/bank information, refunds/disputes, credits, tokens, gifts and commissions.
CommunicationPrivate-message ciphertext and metadata, community posts, email content/headers, available attachment information, voice media, support cases and delivery records.
Verification and supportIdentity fields, document type/country, verification inputs/results, consent records, authorised accessibility/health reports and relevant incident evidence.
Technical and deviceIP/network location, browser/app/OS, device/public-key identifiers, push tokens, diagnostics, security/interaction records and privacy preferences.
AI interactionsQuestions, prompts, permitted context or message excerpts, generated outputs, choices, moderation results and approved-change records.

5. Purposes and lawful grounds

A purpose-specific basis applies; consent is not a universal explanation.

Where UK/EU data-protection law applies, we identify an appropriate ground for each purpose. Contract applies where processing is objectively necessary for a requested service. Legitimate interests can support necessary security, administration, fraud prevention and service improvement after considering necessity, proportionality and people’s rights. Legal obligations apply where a law requires records or disclosure. Consent applies where we ask for an optional choice and the law requires it.

Our legitimate interests include protecting people, accounts and payments, resolving disputes, running reliable services and communicating about existing transactions. They do not make every commercially useful use necessary. You may object where the law provides that right.

Special-category information needs an additional applicable condition; an ordinary contractual or legitimate-interest basis is not enough by itself. Contractual acceptance does not replace marketing/cookie consent. Withdrawing consent stops future processing on that basis, subject to activity already completed lawfully and records retained on another valid ground.

5. Purposes and lawful grounds
PurposeInformationTypical basis where applicable
Requested account and product functionsAccount, role and feature records.Contract; legitimate interests for necessary protection.
Bookings, subscriptions and settlementOrder, guest, payment and entitlement records.Contract and applicable legal obligations.
Chat and Mail deliveryRouting, content according to its encryption model, delivery/operational metadata.Contract and necessary safety/reliability interests.
Spam, fraud and abuse controlsTechnical/account/transaction signals, reports and available content.Legitimate interests and specific legal duties where applicable.
Optional personal AI or Mail intelligenceSelected prompts, permitted context/excerpts and choices.Consent for optional personal-context/mail-excerpt sharing; contract for a requested assistance session; legitimate interests for necessary safety/accountability records.
Marketing and advertisingPermitted audience information, consent/suppression records and device/ad data where enabled.Consent where required, or a narrowly applicable lawful exception.
Requests, complaints and evidenceRelevant records and communications.Contract, legitimate interests and/or specific legal obligations.

6. Shared sign-in and account security

A connected account is not unrestricted access to every product.

Official subdomains can validate the same first-party Pullup session. The session cookie can be scoped to pullup.at so Chat and Mail receive it, but server checks still determine which mailbox, conversation, account or workspace a request can access.

Security can involve password hashes, email verification, 2FA, passkeys, trusted sessions, device information and sign-in challenges. A passkey uses a public-key credential. Device-unlock biometrics are handled by the operating system; that is separate from a verification selfie.

IP-derived approximate location can support sign-in review without continuous device GPS. Closing a tab, signing out of one product and revoking the shared account session can have different effects. Follow the control’s stated scope and review registered sessions/devices.

Local keys, downloaded backups and recipient copies are not automatically erased by ordinary sign-out. Protect the device, credentials and recovery material and report suspected unauthorised access promptly.

7. Public visibility and social activity

Visibility settings have specific audiences and fields.

Public listings/profiles can display a username, name, avatar/banner, bio, links, business/event details, selected badges/cosmetics, follows and permitted Passport/stamp information. Public content can be copied, indexed and viewed beyond Pullup.

Hiding a public map or Passport does not erase the attendance/booking record needed by your wallet, organiser or security controls. A profile setting does not necessarily hide an existing community post, a transaction with a business or a recipient’s message copy.

Shares, reactions, follows and participation can be visible to the people involved. Main-site event/share conversations, communities, private Chat DMs and private support cases have different audiences. Check the destination before posting.

Profile/community artwork may use publicly deliverable asset URLs. A private invitation does not turn an already shared artwork URL into a confidential document store. Do not upload medical evidence, identity documents or secrets into public image fields.

8. Bookings, guest lists, tickets and services

Providers and authorised staff need information to fulfil a booking.

Booking, transfer, resale and redemption records can link purchasers, attendees, the event/provider, selected tiers/seats/rooms/add-ons, payment/eligibility and check-in state. Group purchasers need authority to supply other attendees’ details.

Organisers and staff can access the information needed for permitted duties. Guest lists, scanning, finance, sensitive support notes and refunds can have separate permissions. A ticket or membership alone does not grant administration access.

Ticket links, QR codes and claim/verification tokens can grant access or control. Sharing them may expose booking information or allow an action on the ticket. Treat them as credentials, not ordinary screenshots.

Guest/business exports create copies beyond Pullup’s direct controls. Recipients remain responsible for security, permitted use, retention and marketing. Closing an account cannot remotely erase a host’s already exported file.

9. Payments and financial records

A ledger, authorisation, bank transfer and completed refund are distinct records.

The processor and method shown at checkout handle the relevant payment. Stripe and, where offered or relevant to an earlier transaction, PayPal or SumUp can process checkout, authentication, settlement, fraud and legal information. They may act independently for some purposes.

Pullup receives operational information such as amounts/currency, order/provider IDs, payer/contact details where supplied, subscription status and refund/dispute references. Hosted or embedded processor checkout handles card entry. Never send full card numbers or security codes to support.

Bank-transfer and host-settlement tools can involve account-holder/bank details, references, payment evidence, IBAN/SWIFT instructions and reconciliation notes. A dashboard balance is not proof of a completed transfer.

Instalments, reminders, access restrictions, reward/credit changes, gifts/tokens, commissions and chargebacks create linked records. Financial, dispute, accounting and legal records can need retention after the visible account is closed.

10. Private Chat, keys and metadata

Content encryption does not hide every operational fact.

Private one-to-one Chat seals messages on participating devices for registered recipient-device keys. The service stores encrypted envelopes and operational metadata for that flow. Private photos/voice use client encryption; appropriate device/content keys are needed to decrypt them.

The service still processes account/profile identifiers, membership, public keys, device labels, timestamps, sizes, encrypted media references, request/block settings and permitted delivery/read/typing state. End-to-end encryption is not anonymity.

Keys, caches and pending work can be held on the device. Recovery backups or approved history transfers can enable another device to read content. Losing all usable keys/backups can make older plaintext unrecoverable; a newly registered device may not automatically read old envelopes.

This does not describe communities, ordinary email, main-site event/share messages or support cases. Those can be readable by the relevant service, audience or authorised staff.

11. Calls, voice and notifications

Device permissions and network metadata remain relevant.

Calls and recording features request the camera/microphone permissions needed for the chosen function. Browser/native transport, signalling, security fingerprints and STUN/TURN discovery/relay services can be involved. Peer connections can expose network information to the other participant; a relay carries protected media and receives connection metadata.

Media transport protection does not prevent an endpoint or participant from recording or disclosing a call. Compare a call security code where offered; it verifies a negotiated connection, not a legal identity. Voice messages are intentionally recorded clips, distinct from live calls.

Push services, including Apple APNs/PushKit where supported, receive device tokens, routing/delivery information and notification payloads. Private Chat notifications are designed not to copy message plaintext into native previews. Permissions, device state and providers can affect delivery.

These services are not emergency dispatch, guaranteed alerts or guaranteed recordings. Local recording/playback information and app/system call information can exist independently of server message records.

12. Communities and official support

A community post and a private case have different audiences.

Community membership, posts, channels, roles, reactions, invitations and moderation records are processed to operate the community. Channels are not end-to-end encrypted; authorised moderators/administrators can manage content and access.

Private support cases can contain order/account references, explanations, evidence, messages, assignment/status, staff actions, internal notes and notification/delivery records. The case participant and authorised staff have different views. A normal channel post is not automatically a private case.

Staff may review evidence to resolve a request, investigate fraud or handle legal/dispute duties. Internal administrative notes are subject to appropriate access and lawful handling of rights requests, not a blanket exemption from data-protection duties.

Use the designated evidence workflow. Do not send passwords, full payment details, authentication codes or usable ticket QR credentials. An official support response is not confirmation that a bank refund or payout has completed.

13. Mail content and organisation

Ordinary email is server-processed correspondence, not private Chat encryption.

Mail can process addresses, subjects, bodies, headers, timestamps, provider/message identifiers, delivery/moderation records and available attachment information. Pullup’s backend, email infrastructure and intended recipients process correspondence to receive, display, reply, search, organise, forward and recover it.

The backend checks mailbox ownership and supplies the active sending address. Mailbox activation, pause, forwarding and billing depend on their own state. The application hostname and email-address domain are separate.

Draft recovery and signatures can be browser-local for the account/mailbox. Rules, labels, notes, stars, snoozes, follow-ups and AI choices can synchronise through Pullup’s backend where enabled. A local draft is not necessarily backed up on another device.

Recovery can import matching provider records with original received times and duplicate controls, without forwarding recovered mail again. Providers and recipients retain their own copies under their arrangements. Archiving is not deletion.

Optional Mail intelligence is separate from operational outbound safety moderation. Turning off optional answers does not itself turn off the sending-safety purpose.

14. AI purposes and choices

There is no single purpose or switch for every AI process.

General Pilot help uses your chosen messages and a broad page category. Personal Pilot can retrieve only the categories you enable, subject to existing permissions, and prepare supported changes for your confirmation. Its dedicated notice remains tied to its consent workflow.

Optional Mail intelligence sends a query/question and mailbox evidence excerpts for meaning search, sentiment or cited answers. It requires a mailbox choice. The implemented review is bounded to at most 120 matching messages with up to 1,800 characters of evidence each; results explain the scope rather than promising unlimited archive review.

Operational outgoing-email moderation can send recipient, subject and body through the configured gateway/model to assess spam, phishing or abuse, allow/flag/block delivery and keep an audit result. This is separate from optional Mail intelligence. Ask support to review a disputed restriction.

Discovery, event assistance, translation and poster/image tools process the information supplied to those features. A browser-based provider can receive a request directly and require a separate account. Review its explanation before supplying confidential material.

AI may be wrong, incomplete or biased. A source link does not certify an agreement remains current. Tools may intentionally exclude sensitive structured fields, but free text can still contain them. Avoid unnecessary sensitive information and obtain required authority for others’ records.

15. Campaigns, event updates and engagement tracking

Attendance is not blanket marketing consent.

Essential booking, payment, safety and security communications are distinct from promotion. Calling a message an update does not make unrelated marketing necessary. The sender must identify its actual purpose and applicable rules.

Electronic marketing needs valid consent where required or a specific lawful exception whose conditions are met. An existing-customer exception can require an opt-out at collection and in subsequent messages. Attendance, registration, a follow or accepting Terms is not unlimited permission for future campaigns.

Campaign tools can store audience membership, delivery, unsubscribe/suppression and engagement records. Open pixels and tracked redirects can record an open/click against a recipient/campaign ID. Image proxies, privacy protections and blocking can make these signals inaccurate. Tracking needs its own appropriate notice and permission where required.

Use the sender’s unsubscribe control or contact support. A minimal suppression record may remain to respect the objection. Withdrawing promotion permission does not normally stop receipts, cancellations, security or essential messages about a booked service.

16. Workspaces, calendars and business notes

Permissions apply to the function; exports create separate copies.

Workspace tools can process staff membership/permissions, events and imported calendars, guests, budgets, financial/incident information, notes, promotions and audit records. Owners should limit access and remove it when roles change.

Mail calendar reads use existing calendar/events permissions. Placing event details into a draft does not send it. An exported meeting file does not itself create an event or invite participants. External calendar imports create copies outside Pullup.

Private labels or notes can be business records. Do not gather irrelevant health details, allegations or discriminatory profiles simply because a field accepts text. Incident and safeguarding records require careful purpose, access, accuracy and retention decisions.

Organisations must consider who receives an export or integration feed and whether they may share it. Later revocation does not recall already downloaded or transmitted information.

17. Optional health, accessibility and guest support

Use the designated flow for the named attendees and event.

Optional guest support can collect health/accessibility information for specified attendees at a specified event, with its separate consent statement and authorised host/staff access. Providing support information is not a condition of ordinary entry. Someone acting for another attendee needs that attendee’s explicit permission where required.

Designated reports use encrypted storage that the backend can decrypt for authorised use; that is not end-to-end encryption between attendees. The event’s configured support deadline controls report availability/expiry. Verification sessions, delivery and consent/audit records can have separate lifetimes.

Withdraw optional information through the available flow or contact the host and Pullup. Withdrawal can limit planned assistance but does not permit unrelated use. A separate incident, dispute or legal record needs its own justification.

This is not medical advice or an emergency service. Contact responsible venue staff or local emergency services for urgent assistance. Do not put medical reports into public posts, campaign notes or AI prompts as a workaround.

18. Identity, documents and biometrics

Transient raw inputs and retained identity/result records are different.

Verification may request name, birth date, address, nationality, document type/country, document number, document image, live selfie and OCR/liveness/face-comparison information. Parts run on-device; inputs/results also reach the server so it can validate the request and derive the result.

The implemented route is designed to use document numbers and document/selfie images transiently rather than write those raw inputs to its verification database or object storage. Extracted identity fields, document type/country, results, scores/checks and timestamps can remain in account/audit records. Transient handling is still personal-data processing.

Face comparison for identification can involve special-category biometric information and needs an applicable additional legal condition. Where consent is the relied-on condition it must be explicit; this policy does not itself give it. Contact support about the process, data use, available alternatives or an adverse result.

Public indicators should show the intended verification/age band, not a full birth date, home address or document number. A badge is a recorded process indicator, not government certification, creditworthiness, a guarantee against fraud or a replacement for venue admission duties.

19. Location, maps and accommodation

IP location, GPS, venue details and travel bookings are not the same activity.

IP information can support approximate location, language/currency defaults, fraud checks and sign-in review. Device geolocation is a separate permission for a chosen feature. Denying GPS does not stop an IP address being part of a network request.

Event/address visibility depends on the listing and access controls. Public descriptions, media and external links can reveal a location independently. Do not place a private home address in a public field and assume a ticket control hides it.

Mapping, geocoding, postcode and network-location services can receive network information and a location query. Implementations can involve map/tile providers, OpenStreetMap/Nominatim, Postcodes.io and enabled IP-location services. External directions have the destination’s own processing.

An accommodation referral, including Stay22-style links, is different from a room/service booking made through Pullup. For a direct platform booking, Pullup and the provider receive records needed to fulfil it; for a referral, the external booking site handles its own checkout and records.

20. Planning, photos, bids, vouchers and recruitment

Small workflows also create personal records.

Group/trip planning can store membership, invitations, proposals, votes, dates, destinations, budgets and booking states visible to authorised group members. A calculated group wallet/budget is not necessarily a regulated bank account or a guarantee that a provider booking is completed.

Event albums, media approvals/reactions, collaborative playlist votes, recaps, stamps and collectibles can associate selected content/activity with an event or profile. Approved/shared media can expose people who appear in it. Use the relevant audience/moderation tools and obtain necessary rights.

Auctions can store bids, a chosen public alias, timestamps, allocation, payment consent, card setup/provider references and bank-approval records. A public alias does not make the bid anonymous to the authorised operator/backend. Event shops and bar vouchers create order, entitlement, redemption and staff-scan records.

Nearby discovery, where used, updates stored coordinates and a visibility/time record to show eligible nearby profiles and distance. The reviewed response exposes profile/distance/last-seen information rather than returning raw coordinates to the peer; repeated distances can still reveal location. Its 30-minute activity filter is not a promise that stored coordinates are erased after 30 minutes. Turning visibility off stops the implemented listing; it is distinct from erasure.

Journey tools can send origin/destination coordinates to Mapbox or TfL for directions. External event discovery can send search/location criteria to the configured listing provider. IP-based location estimation is different from browser/device GPS permission.

Safety reports and staff incident records can include a category, severity, description, location hint, reporter/guest linkage, status and actions. Marking a report anonymous can hide a name in an intended display/notification without making every underlying linked record anonymous. Relevant staff may need evidence and the report can inform account-risk review.

Job applications can collect the position/department, name, contact details, location, experience, cover letter, optional professional/portfolio links and a résumé URL, plus review status/timestamps. Authorised recruitment staff use this to assess and administer applications, communicate, maintain necessary recruitment/legal records and handle requests, on the applicable pre-contractual, legitimate-interest and/or legal-obligation grounds. It is not automatically a marketing subscription. Do not include unnecessary sensitive information; ask about correction/retention/withdrawal using the privacy contact.

21. Connected accounts, apps and webhooks

Scope limits future access; revocation does not recall all copies.

Sign-in, Gmail, social, advertising, event-import and developer integrations process the information authorised for their enabled functions. Backend access/refresh tokens may maintain a connection. API keys and webhook destinations can transmit permitted records to a configured service.

A read-only Gmail authorisation is different from a hosted Pullup mailbox and does not itself grant Gmail sending permission. Review the actual provider consent screen. Social connections can involve provider IDs and the profile/content scope needed by the chosen function.

External app operators and business administrators have responsibilities for records received. Revoke permissions in Pullup and at the provider where relevant. Future access can stop without erasing copies already held by the recipient.

Protect keys, signing material and tokens. Do not put privileged service keys or reusable credentials in public apps, public URLs or support screenshots. A webhook recipient must be one your organisation is authorised to use.

22. Recipients and disclosure

Disclosure follows purpose and audience, not an unrestricted right to share.

Recipients can include the organiser/provider fulfilling a booking, authorised staff, intended correspondents, a public/community audience you publish to, infrastructure/processors, payment/identity services, professional advisers and authorities where disclosure is legally required or otherwise justified.

Fraud, safety, disputes and legal requests can justify relevant disclosure under their applicable conditions. We assess scope and authority; a request is not permission for unrestricted access. Notification can be limited where law prohibits it.

A lawful business reorganisation or transfer can involve records necessary for continuity, subject to contractual, consumer and privacy protections and notice duties. It does not automatically authorise an unrelated purpose requiring a new basis or consent.

We do not offer private Chat plaintext or mailbox bodies for sale as an advertising dataset. Advertising choices can involve device/browsing disclosures. Legal definitions of sale, sharing and targeted advertising vary; use applicable choices and contact us about jurisdiction-specific rights.

23. International processing

A regional database is not an all-data residency guarantee.

Users, hosts, recipients and service providers can operate in different countries. Hosting/edge delivery, storage, email, AI, push, support and payments may process data outside your country. Sending correspondence abroad also makes it available to that recipient.

A restricted transfer under UK/EU law needs a lawful mechanism. Depending on the transfer, that can include applicable adequacy coverage or appropriate contractual safeguards, such as standard clauses and any required UK addendum/transfer agreement, with additional measures where needed.

Provider account settings, contracts, locations and subprocessors affect actual handling. We do not promise universal EU-only processing or universal zero retention. Ask the privacy contact about recipients, locations and applicable safeguards or available copies, subject to legitimate security/confidentiality redactions.

24. Retention, expiry and closure

No single deadline accurately describes every record and independent copy.

We keep personal information for its purpose, considering the requested service, user controls, transactions, disputes, legal duties and security needs. Hiding an expired record from a normal view can precede background deletion. Necessary retained records should be restricted to the purpose justifying them.

The account-deletion workflow currently includes a 30-day scheduled grace period in which reactivation can cancel deletion. It is not a promise that every provider, recipient, business record and backup is erased at the end. Product data, legal/financial records, shared records and technical completion/failures need separate handling.

Genuinely anonymous aggregates may be retained longer. Replacing a name with an ID does not automatically anonymise a record. Backups follow the relevant lifecycle and are not necessarily individually editable. Contact us for a product-specific explanation or erasure request.

Host exports, email recipients, downloaded key backups, local drafts and external-calendar copies require handling by the person or organisation holding them.

24. Retention, expiry and closure
RecordRetention approach and limits
Account/profile/settingsActive-service purposes, then the closure/erasure process and justified exceptions; cancelling billing and deleting local storage are separate.
Private Chat and mediaConversation/account lifecycle, clear/auto-delete choices and cleanup where enabled; independent screenshots, recordings and backups are not remotely erased.
Communities and supportOperational, case-resolution, safety, dispute and legal needs; content, evidence, internal notes and audit records can have different lifetimes.
Mailbox and saved organisationMailbox/account lifecycle and available controls; archiving is not deletion and provider/recipient copies remain separate.
Drafts, signatures and device keysDevice-local until changed/cleared under the relevant controls; browser/OS backups and downloaded files need separate handling.
Optional guest-support reportsThe configured event deadline and withdrawal/deletion flow; challenge/session/delivery/consent records have separate purposes.
Identity verificationTransient raw inputs as described above; justified identity, result and audit records are retained separately.
Financial and legalThe applicable record-keeping, tax, payment, reconciliation and dispute periods; duration depends on jurisdiction, record and unresolved matters.
Security and operational logsPurpose-specific configured cleanup; a short rule for one log table is not a platform-wide guarantee.
Marketing suppressionMinimal information needed to respect objections and demonstrate permission; unsubscribe need not delete the suppression entry.
AI recordsFeature-specific local/session history, necessary consent/change/safety audit records and the provider’s applicable controls.

25. Security and its limits

Different protections address different risks.

Controls include secure transport, account/session protections, access restrictions, password hashing, permission checks and purpose-specific encryption. Private Chat encryption, server-decryptable support storage and ordinary email/business records do not have the same model.

We do not describe all data as end-to-end encrypted or guarantee perfect security. A compromised/unlocked device, malicious recipient, excessive staff permission, public upload or exposed credential can defeat a confidentiality expectation.

Staff access should be limited to authorised support, operational, safety or legal duties. Infrastructure responsibilities are distinct from ordinary product-user access and do not necessarily provide the keys for private-message decryption.

If a personal-data breach occurs, we assess it and make the notifications and remedial steps required by law. Report suspected privacy/security issues through official support with only the necessary evidence.

26. Cookies, device storage and advertising

A cookie choice is not the same as deleting every product’s local work.

Storage can support sessions, security, choices, requested functionality, Chat device material and Mail drafts/signatures, alongside optional analytics/advertising where enabled. Storage for a requested service has a different purpose from advertising profiles.

Where consent is required, optional processing follows the relevant choice rather than acceptance of Terms. Laws have technology/purpose-specific exceptions; a limited exception is not permission for unrelated tracking.

Google AdSense and enabled integrations such as Snap can process advertising/measurement data. External maps, embeds, link destinations, extensions and operating systems can have separate settings. A choice on one origin does not necessarily clear all cookies or local data on another.

The storage notice explains categories, examples and controls. We do not claim certified consent-framework compliance merely because code exposes a similarly named software API.

27. Automation, profiling and review

Some automation helps a task; some can restrict an action.

Automation can support recommendations, translation, rewards/eligibility, spam/fraud/security checks, verification, expiry and reminders. It can affect ranking, additional verification, holds or a message/transaction being allowed or flagged.

Results may be mistaken. A generated answer or sentiment is an estimate, not a legal, medical, credit or identity determination. A reminder or attempted notification is not proof that someone read or accepted a message.

Ask support to review an adverse result. Where law gives safeguards for solely automated decisions with legal or similarly significant effects, the applicable human-intervention, explanation and challenge protections apply. UK and EU rules are not identical, and a general consent statement does not waive safeguards.

28. Rights, exports and requests

Statutory rights are not limited to a convenience export.

Depending on the applicable law, rights can include information, access/copy, correction, erasure, restriction, objection, qualifying portability, consent withdrawal and regulator complaint. Their conditions and lawful exceptions apply rather than an absolute promise to erase every record.

The reviewed convenience account export currently permits one request every 15 days and can depend on the export-email preference. It includes a limited set of account/hosted-event records, not a complete Chat, Mail, ticket, attachment or device-key archive. That operational limit does not restrict a statutory request made through our privacy contact.

Self-service exports cover the records that tool includes; they are not necessarily a complete cross-product response. A convenience feature’s operational cooldown or email preference does not remove a statutory right to contact us for a data request.

For encrypted Chat, we can address records/metadata held by the service but may not possess the keys to return plaintext. We do not bypass another participant’s rights or promise recovery without keys. Device-local records need local handling.

Contact support@pullup.at or official private support, identify the products and describe the request. We may need proportionate identity checks or clarification. Do not send passwords, full card details or a document image merely to start a request. Host-controlled data may require coordination with that host.

Where UK/EU time limits apply, the ordinary response period is generally one month, with any lawful extension or adjustment handled and explained under the applicable rules. We do not apply a blanket fee or export cooldown to every rights request. Where we cannot fully act, we explain the applicable reason and complaint route unless law restricts that explanation.

29. Age and other people’s information

Account eligibility and venue admission are separate.

The published account Terms are intended for adults aged 18 or over. Events, services and transactions can impose additional eligibility or age restrictions. An account, ticket or age/verification indicator does not override admission rules or law.

Adults supplying group/guest or support details need the relevant authority and permissions and should provide only what is necessary. A feature displaying an age band does not establish eligibility for every service.

Contact support if you believe a submission/account involves a child contrary to the rules. We assess safety and applicable duties when restricting, correcting or removing information. A child’s acceptance is not blanket permission for marketing, sensitive processing or an otherwise ineligible transaction.

30. Complaints, changes and contact

You can raise a concern without giving up another lawful remedy.

Use support@pullup.at or an official private case, identifying the product, approximate date and type of information. Do not publish sensitive evidence in a community. We may request relevant references to locate the record.

You can complain to a competent data-protection authority where law permits. The UK ICO provides a complaint route; in the EEA, the relevant national authority or authority connected with your residence/work or an alleged infringement may apply. Contacting us first can help but does not remove a complaint right.

This policy is versioned. Material changes are explained and a further choice is obtained where required. Publishing a new notice does not retrospectively turn an unrelated use into consent. Operator details, effective date and the previous published version are shown in the Legal centre.

COMMON QUESTIONS

Can every message be treated as end-to-end encrypted?

No. Private Chat DMs have a device-encrypted flow; community posts, support cases, ordinary email and main-site event/share messages have different boundaries.

Does disabling Mail intelligence stop outbound moderation?

No. Optional mailbox search/answers and operational sending-safety processing are separate purposes.

Does deleting an account erase recipient copies?

No. Recipient files, exports, local backups and justified retained records need separate handling.