Skip to content

Privacy Notice

How Shanta Ltd uses account, journey, booking and recipient information.

Provisional version · 16 November 2026

Provisional — details still being completed

Shanta Ltd is the operator. Its company number, registered address and support/privacy email have not yet been provided for publication. This document remains subject to completion and review. Publishing it does not remove your statutory rights.

1. Who uses your information

Shanta Ltd is the operator and controller of personal information used to operate Shanta. Its company number, registered address and public support/privacy contact details are still pending publication.

This provisional notice covers visitors, account holders, senders, carriers and recipients whose details are supplied by a sender. A recipient does not need an account to have data-protection rights.

The production providers, retention periods, international-transfer arrangements and contact/request procedures below still need completion and confirmation. This notice does not certify that those outstanding arrangements have been implemented.

2. Information used by Shanta

  • Accounts: name, email, phone, account identifiers, login/session and contact-confirmation information.
  • Profiles: optional avatar and biography, membership history, verification status and review/completion summaries.
  • Journeys: origin/destination cities and countries, departure and optional arrival, capacity and guide prices. These can reveal travel plans.
  • Bookings: descriptions, category, weight, dimensions, bags/parcels, instructions, events and recipient names/contact details supplied by the sender.
  • Photos: images submitted through the booking feature. Avoid including faces, documents or unrelated personal information.
  • Payments: fee amount, currency, payment/refund status, provider references and timestamps. Stripe collects card and relevant billing/security information directly. The current integration does not give Shanta full card numbers or card security codes.
  • Reports and support: reviews, ratings, complaints, evidence, correspondence, moderation reasons and administrative history.
  • Technical information: cookies and authentication, service/security logs. Infrastructure/payment providers may also process IP addresses, browser/device and request information; the production supplier inventory is awaiting confirmation.

3. Where information comes from

Information comes from you, the sender or carrier connected with a booking, people submitting reports, and providers confirming account/payment activity. A sender may give us recipient information even when the recipient has no account.

Shanta does not provide direct messaging or delivery negotiation. It does not receive off-platform calls, messages or agreements through a Shanta messaging feature. Users may supply such material when making a report or contacting support.

The current software stores verification status and references but has no live identity-document/selfie provider connected. Any future provider and collection practices will need to be explained before use.

4. Purposes and legal bases

Information is used to operate accounts, publish journeys, process requests, supply paid introductions, confirm payments, send service messages, display reviews and investigate platform problems.

Processing necessary to supply a service requested by a contracting user can rely on contract. Recipient information needs its own justification: a recipient is not automatically a party to the sender’s contract.

Protecting users, preventing misuse, handling reports and supporting a public marketplace may rely on legitimate interests where necessity and balancing requirements are met. Relevant accounting/regulatory records can be processed to meet an applicable legal obligation. Consent is used where appropriate for a separately offered optional activity.

The final purpose-by-purpose assessment is still being completed. Reading this notice or accepting the Terms does not provide blanket consent for every processing purpose.

5. Public information and contact release

Public: profiles can show names, avatars, biography, membership history, verification status and review/completion summaries. Published journeys show route, timing, capacity, guide prices and public carrier information. Published reviews can be visible to visitors. Do not put private contact or recipient information into public text.

Before contact release: a carrier can review item and request details. The normal booking interface withholds the other party’s email/phone and the recipient’s contact details from the carrier.

After paid confirmation: the sender and carrier can access each other’s account email and phone. The carrier can also access the recipient’s name/contact details. Item photos are accessible to the booking parties under the feature’s access rules.

Authorised administrators can access relevant records for support, moderation and operation. A public profile does not give unrelated users access to private bookings.

Other people may retain information already disclosed to them. Account closure or removing an avatar cannot recall copies they obtained. Users must not repurpose contact information for unsolicited marketing or unrelated disclosure.

6. Providers and other disclosures

The software uses Supabase services for authentication, database records and storage, Stripe for checkout/refunds, and supports Resend for production booking emails. Actual production contracting entities, infrastructure, email and monitoring arrangements still need confirmation.

Relevant information may also be disclosed to advisers, insurers, courts, regulators or law-enforcement bodies when necessary and lawfully justified. Provider notices do not replace Shanta’s responsibilities or required processing agreements.

The final list will identify relevant roles and locations. Support for a provider in the software is not a claim that all its production services are active.

7. International use and transfers

Senders, carriers or recipients for a chosen journey may be abroad. Payment, email, hosting and support arrangements can involve other countries.

Production countries and mechanisms for any restricted transfers still await confirmation. These may require an applicable UK adequacy regulation, appropriate safeguards and assessment, or a specific lawful exception. Using Shanta does not give blanket consent to international transfers.

Shanta does not promise that all information stays in the UK. The final notice must describe the actual arrangements and how to obtain relevant safeguards.

8. Retention and deletion

The complete retention schedule is still being finalised. Relevant purposes include active accounts/bookings, support, complaints, legal claims, security and accounting duties. Recipient contacts should not automatically be kept as long as accounting records.

The photo feature has configurable cleanup defaulting to 30 days after a booking closes. This depends on the job and settings; it is not yet a verified production deletion commitment. An expired link is not evidence that the underlying file was deleted.

Account closure or a ban does not automatically delete all records. Continuing retention needs a lawful, justified purpose. Log/backup expiry and account, booking, review, report and transaction retention periods will be added when confirmed.

9. Cookies and similar technologies

Authentication cookies maintain and refresh sign-in. Their project-specific names and live maximum lifetimes still need verification; they may last beyond a browser session.

The shanta_pending_email cookie remembers the address awaiting confirmation for up to one hour. shanta_form_flash_* cookies return results and entered values after certain submissions without JavaScript, for up to five minutes. Relevant actions may clear them sooner.

Payment-provider technologies operate and secure hosted checkout. Production hosting and checkout still need a complete cookie/storage audit to confirm purposes, lifetimes and required choices. Blocking sign-in or form-function cookies may prevent requested functionality.

The reviewed app contains no advertising/marketing-tracking integration. That observation is not a completed audit of every deployed provider’s technologies.

10. Automated checks and moderation

Software checks eligibility, booking state, capacity, payment and submitted content. Checks may prevent an action or restrict content. Administrators use relevant records and reports for moderation.

An assessment of decisions with legal or similarly significant effects is still pending. The completed notice must explain applicable information and review safeguards. Signed-in users can use reporting tools to flag relevant platform problems.

11. Your rights and complaints

Depending on the law and processing, you may have rights to access, correction, deletion, restriction, a portable copy or safeguards for relevant automated decisions. Conditions and exceptions apply; accounting or legal-claims purposes may require limited retention.

Right to object: you may object to processing based on legitimate interests on grounds relating to your situation. Shanta must assess that objection under the applicable rules. You can object to direct marketing at any time.

Where processing relies on consent, you can withdraw it without affecting the lawfulness of earlier use. Requests must be handled within the legal time and any permitted refusal or extension explained. Recipients do not need to register to exercise rights.

The dedicated privacy contact and postal address are pending publication. Booking reports are not a complete substitute for a privacy-request channel. This is one reason this notice remains provisional.

You can raise data-protection concerns with the Information Commissioner’s Office where relevant. Contacting Shanta first does not remove your right to approach the regulator.

12. Required information, security and updates

Information needed for an account, request or payment may be required for that feature. Optional biography and avatar fields are not required for the underlying account functions.

Access controls and other safeguards support the service; no online service can promise absolute security. This notice does not waive your rights concerning security or incidents.

The completed notice will confirm outstanding contact and operational information. Significant changes will be explained as appropriate. See the Terms and Conditions for the introduction service.