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

YOUR MAILBOX. YOUR WORKSPACE. THE DETAILS.

Pullup Mail

Hosted email, delivery providers, mailbox organisation, optional intelligence, local drafts, forwarding and workspace calendar access.

Revision 2026-11-165 min read8 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

  • The app is at inbox.pullup.at; an email address can use a different domain.
  • Hosted mail is processed on servers and is not private Chat encryption.
  • Optional Mail intelligence and outbound safety moderation have separate purposes.

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. Website, address and mailbox control

A web hostname is not the email-address domain.

Pullup Mail is the product name. The designated application is inbox.pullup.at; references to mail.pullup.at describe Mail or an officially configured alias, not a guarantee that both hostnames are live. Existing hosted addresses can use @pullup.my. Check the address actually assigned in your mailbox.

Mail uses the main Pullup account/backend, ownership and activation checks. Switching mailboxes changes the authorised mailbox context; it does not grant access to another user's records. A plan, extra-mailbox purchase, pause or forwarding configuration can affect availability.

Billing/allowances follow the actual offer. An address is not a promise of perpetual ownership, unlimited storage or uninterrupted delivery. Contact support before changing an essential business address.

2. Information and processing

Email needs server-side delivery and storage.

We process sender, recipients, subject, body, thread/provider IDs, timestamps, delivery state, attachment information and relevant operational records. Mailbox settings, forwarding addresses, organisation state and safety outcomes can also be stored.

Resend supports enabled sending/receiving. AWS SES is used for enabled platform/campaign email paths. Processing can involve external sender/recipient providers and networks. Hosted mail is not end-to-end encrypted private Chat; do not rely on a website lock icon as a promise of that model.

Attachments can have provider-managed metadata/URLs and their own availability period. A message can contain tracking pixels, links or hostile content supplied by its sender. Avoid opening unexpected attachments or disclosing credentials.

3. Receiving, recovery and forwarding

Provider acceptance and inbox display are different states.

Inbound processing validates supported provider events, obtains the available message body and links the mail to an owned mailbox. Provider IDs support duplicate protection. Historical recovery can import provider-available messages for a selected owned mailbox with the original received time.

Recovery is a reconciliation tool, not a guarantee that a provider retains every historical body/attachment forever or that a missing item was never received. Recovery can suppress duplicate forwarding; routine forwarding creates another recipient/provider copy.

Sent, accepted, delivered, rejected, bounced, delayed and displayed states are different. Spam filtering, provider outages, DNS and mailbox state can affect delivery. An uncertain response should be checked before retrying to avoid duplicate sends.

4. Sending safety and abuse prevention

Operational checks are distinct from optional discovery AI.

Outbound moderation can send recipient information, subject and body to an OpenAI model through Vercel AI Gateway and return an allow, flag or block outcome. This supports fraud/spam/abuse controls and relevant evidence; it is not the optional meaning-search setting.

An unavailable moderation provider can result in a flagged fallback path rather than a guarantee that every message has been reviewed. Neither an allow result nor a block proves the message is safe or unlawful. Ask support about an erroneous restriction.

Send only lawful, authorised correspondence. Marketing needs its applicable consent or exception and opt-out process. Do not use Mail for phishing, impersonation, malware, bulk unsolicited messages or bypassing another provider's controls.

5. Search, labels, rules and knowledge answers

Read the original evidence before relying on an answer.

Structured search can combine the implemented people, words, dates, attachments and state filters. Optional Mail intelligence can interpret meaning, suggest organisation or synthesise permitted excerpts when enabled. It is not an unlimited permanent index of every historical message.

The reviewed discovery flow can assess up to 120 matching messages with excerpts up to 1,800 characters per message, using Groq. Search parameters and implementation limits can change with a release. A missing semantic result does not establish that no relevant message exists.

AI answers, proposed labels and sentiment are estimates. Check cited messages, participants, dates, attachments and later amendments before concluding what was agreed. Do not use sentiment as a reliable determination of a person's health, protected traits or intent.

Backend organisation can include labels, rules, stars, notes, archive/read state, snooze/follow-up state and the mailbox AI choice. Private notes are records in the authorised business mailbox; they are not an encrypted device-only diary.

6. Snooze, reminders and drafts

In-app organisation is not a guaranteed alert channel.

Snooze/follow-up controls can resurface messages in the app and cancel a waiting reminder when a new reply arrives. They depend on the implemented time/state checks; do not assume a background push or reminder email exists merely because a time was selected.

Draft recovery and signatures can be kept in account/mailbox-scoped localStorage on the device. Local browser storage is not the private Chat encryption model, may be accessible to someone using that browser profile, and can be cleared or unavailable.

Check recipients, mailbox, subject, attachments and signature before sending. A saved draft or an event inserted into one is not already sent. Archiving, marking read, snoozing and deleting have different effects.

7. Workspace calendar connection

Existing workspace permissions still apply.

Mail can show an authorised workspace agenda using calendar.view or events.view access. It does not grant calendar access to every mailbox user or automatically disclose sensitive guest-support/finance records.

An enabled calendar action can place event details into an unsent draft or export a calendar file. It does not necessarily create a workspace event, send an invitation, reserve a room or notify every attendee.

An exported .ics file or sent agenda details leave the immediate workspace access boundary. Share only what the recipients may receive and verify date, time zone, location disclosure and later changes.

8. Choices, copies, retention and help

Account closure cannot recall every delivered email.

Review forwarding, mailbox activation, AI choice, organisation rules and billing. Optional intelligence can be disabled without changing the technical need to route/store mail or operate relevant safety controls.

Message/organisation retention follows the Privacy Policy's purpose-based criteria, relevant mailbox/account action, provider availability and lawful record needs. Forwarded messages, external recipients, exported calendar files and device drafts require separate handling.

Use the privacy-rights process for records and erasure requests. The convenience account export is not a promise to include every hosted message/attachment or every private note. For delivery, recovery or safety disputes provide the mailbox and relevant message/time reference, not your password.