Privacy Policy

How Total Pharma Tech handles personal data — as the operator of this website, as a supplier to your organisation, and as a processor of field data that our customers upload to the platform on their own instructions.

This document is a working draft written in plain English. It has not been reviewed by a qualified lawyer, and it must be reviewed, completed and approved by your legal adviser before publication or before you rely on it.

Version 1.0. Last updated 18 September 2026. This policy applies to the website at totalpharmatech.com and to the Total Pharma Tech field force management platform.

Contents

  1. Who we are and what this policy covers
  2. Our two roles: controller and processor
  3. Personal data we collect
  4. Lawful bases for processing
  5. How we use personal data
  6. Cookies and analytics
  7. Sharing personal data and sub-processors
  8. International transfers and safeguards
  9. How long we keep personal data
  10. How we protect personal data
  11. Your rights
  12. Automated decision-making and AI features
  13. Children's data
  14. Customer field data and our Data Processing Agreement
  15. Changes to this policy
  16. How to contact us

1. Who we are and what this policy covers

Total Pharma Tech ("TPT", "we", "us") is a trading name used by a business based in Pakistan, and we operate the website at totalpharmatech.com and the platform application at app.totalpharmatech.com. We provide an AI-powered field force management platform to pharmaceutical, biotech, medical-device and life-science companies.

We have not yet incorporated a legal entity, so we are identified here by our trading name, the country we operate from, and the contact details in section 16. Where we sign an Order Form or other written agreement, the party named in that document is the contracting party, and is the controller for the purposes of that agreement.

This policy explains how we handle personal data when you:

  • visit our website or read our pages;
  • send us an enquiry, request a demo, or ask us to contact you;
  • work for one of our customers, or for a company evaluating us, and we hold your business contact details or platform account details; or
  • are an individual whose data appears in field data that a customer uploads to the platform — for example a healthcare professional, a clinic contact or a pharmacy contact.

It does not describe how our customers use personal data in their own systems, and it does not apply to third-party websites we link to. Marketing communications we send are covered here; the contractual terms on which we supply the platform are in our Terms of Service.

2. Our two roles: controller and processor

Two different roles apply to us, and it matters which one we are in.

  • We are a controller for our website, our marketing and sales activity, and the administration of our own business relationships. We decide why and how that personal data is used, and we are the controller responsible for it.
  • We are a processor for the field data our customers upload into the platform and for the personal data of their personnel held in their account. In those cases the customer is the controller and we act only on that customer's documented instructions, under our Data Processing Agreement. The customer decides what is collected, why it is collected and how long it is kept.

If you are an individual whose data sits in a customer's tenant and you want to exercise a privacy right over it, please contact that customer first. We will pass on any request we receive to the relevant customer without undue delay and assist them in responding.

3. Personal data we collect

We try to collect as little as possible. What we hold depends on how you interact with us.

Website visitors

Server logs that record your IP address, browser and device type, the pages requested, the referring page and the time of the request; aggregate usage statistics; page-performance metrics such as how quickly pages load; and cookie identifiers as described in section 6. We use these for security, troubleshooting, capacity planning and to understand which pages are useful. We do not use them to build advertising profiles.

Spam protection on the demo form

Our demo form is protected by Cloudflare Turnstile, which judges whether a submission is likely to come from a person rather than a script. When the form page loads, Cloudflare receives your IP address and signals about your browser and connection in order to make that judgement. We receive only the outcome: whether the check passed. The check is not used to track you across other websites, and it is not involved anywhere else on the site.

Demo requests and sales enquiries

Your name, email address, telephone number, company, job title, country, the size and structure of your field team, and anything you write in the message field of our demo form. If your enquiry becomes a customer relationship, we also hold correspondence, meeting notes and the contact details of the people involved in the evaluation and the contract.

Customer personnel

For named administrators and users of a customer account we hold name, work email, role and permissions, authentication events, and audit records of actions taken in the platform. Customers are responsible for keeping this information accurate and for telling their staff how their data is used.

Data we process on behalf of customers

Field activity records such as planned and completed visits, calls, group meetings and congress engagements; healthcare professional and organisation records such as name, specialty, practice address, contact details and engagement history; product, territory and target data; and any other content a customer chooses to upload. Some of this is personal data about people who are not our users, such as healthcare professionals. We do not collect it for our own purposes, we do not sell it, and we do not use it to contact those individuals on our own behalf.

We do not ask for special category data, and the platform is not designed to hold patient-level data. If a customer uploads data about patients or other special category data, that customer is responsible for having a lawful basis and any additional safeguards required by local law, and we process the data only as instructed.

4. Lawful bases for processing

Where the EU or UK General Data Protection Regulation applies, and we are the controller, we rely on the following lawful bases.

  1. Performance of a contract — providing the platform, creating and administering accounts, delivering support, onboarding and billing a customer organisation, and taking steps at your request before a contract is signed.
  2. Legitimate interests — running and securing our website, responding to business enquiries, understanding which content is useful, preventing abuse and fraud, and protecting our legal rights. We weigh these interests against your rights and expectations, and you can object to processing on this basis at any time.
  3. Consent — non-essential cookies, and marketing email to individuals where local law requires consent. Where we rely on consent, you can withdraw it at any time and we will stop that processing. Withdrawal does not affect processing carried out before it.
  4. Legal obligation — keeping accounting, tax and contract records, and responding to lawful requests from courts, regulators or other authorities.

Where we process customer field data as a processor, we do not rely on a lawful basis of our own. The customer identifies the lawful basis for that processing and gives us documented instructions.

5. How we use personal data

  • To answer enquiries, arrange and run demonstrations, and prepare proposals.
  • To provide, operate, secure and support the platform for our customers.
  • To authenticate users, enforce permissions and maintain audit trails.
  • To send service messages that are part of the contract, such as maintenance notices, security notifications and invoice reminders.
  • To send marketing email about our products where we are permitted to do so, with an unsubscribe link in every message.
  • To measure website performance and improve our content and product.
  • To detect, investigate and prevent misuse, fraud and security incidents.
  • To comply with legal, tax, accounting and regulatory obligations, and to establish or defend legal claims.
  • To plan our business, including aggregate reporting on enquiries, pipeline and platform usage that does not identify individuals.

We do not sell personal data, we do not rent it, and we do not share it with advertising networks or data brokers. We do not use customer field data to train AI models that are shared with other customers.

6. Cookies and analytics

A cookie is a small file a website stores in your browser. We use a small number of them and we keep the categories separate.

  • Strictly necessary. Cookies that protect forms against cross-site request forgery, balance traffic and remember your cookie choice. These cannot be switched off without breaking the site.
  • Analytics. Cookies that tell us which pages are visited and how visitors move through the site, in aggregate. These are set only if you accept them.

The cookies we set on this website

The table below lists every cookie this public website can set. It is kept accurate rather than approximate.

Cookie Category Purpose Lifetime
tpt-consent-v1 Strictly necessary Stores your cookie choice in your browser's local storage so we do not ask on every page. It records only the choice and the date; it is not shared with anyone. 6 months, then we ask again
ph_<project>_posthog Analytics — requires consent PostHog product analytics. Stores a random identifier and session state so we can count unique visitors and see which pages they move through. Set by PostHog only after you accept. Up to 1 year
Cloudflare challenge cookies Strictly necessary If the bot-protection check on our demo form needs to remember that a check was already completed on your device, Cloudflare may set its own cookie for that purpose. It is not used for advertising or analytics, and it is only involved when you use the demo form. Short-lived, set by Cloudflare

How PostHog is configured

PostHog is our website analytics tool. It is configured narrowly, and these are deliberate choices rather than defaults:

  • Autocapture is off. We do not record every click, hover or keystroke. The only events we send are page views, the aggregate performance metrics described below, and the demo-request conversion when you submit the demo form.
  • Aggregate performance metrics. We record how quickly pages load — core web vitals and network timing. These describe the page rather than you: they are used to keep the site fast, and they are not used to build a profile of an individual visitor.
  • Session recording is off. We do not record your screen or your interactions on the site.
  • Anonymous by default. Visitors are not turned into stored person profiles unless they identify themselves — for example by submitting the demo form.
  • No surveys, no page-leave timing, no advertising use. PostHog data is used only to understand aggregate website usage.
  • Hosting and international transfers. Our PostHog project is hosted in the United States. Visitor analytics data is therefore transferred to and processed in the United States, under PostHog's data processing terms and the transfer safeguards described in section 8.

If we ever enable session recording or autocapture, we will update this policy and ask for fresh consent first, because those capture materially more than what is described here.

What we publish

Website analytics is PostHog only. If we add another analytics or marketing tool, this table and section are updated before it goes live — the list above is intended to be exhaustive, not illustrative.

How the choice works

On your first visit we ask whether you accept analytics. Until you accept, no analytics cookie is set and no request is made to PostHog at all — the analytics script is not loaded, because the consent gate loads it rather than the page. Declining has no effect on your ability to use the site and is remembered for six months.

You can change your mind at any time. Clear the site's data in your browser settings (or clear the tpt-consent-v1 entry in local storage) and the banner will appear again on your next visit.

We do not use advertising cookies, cross-site tracking pixels, remarketing or social media trackers on this website. PostHog acts on our behalf as our processor under PostHog's data processing terms, which may include transfers outside your country as described in section 8.

You can block or delete cookies in your browser settings; blocking the strictly necessary ones will prevent parts of the site from working.

7. Sharing personal data and sub-processors

We share personal data only with the categories of recipient below, only as far as needed for the purpose, and only under written terms that require confidentiality and appropriate security. Where we act as a processor, these suppliers are our sub-processors and their use is governed by the Data Processing Agreement.

Sub-processor category Purpose Data involved
Cloud hosting and infrastructure Running the platform and website, storage, regional hosting and backups All platform and website data, including customer field data
Bot and spam protection — Cloudflare Turnstile Deciding whether a demo form submission is likely to come from a person rather than a script IP address and browser or connection signals for demo form submissions
Email delivery and business email Sending transactional email, demo form notifications and support correspondence Contact details, message content
Product analytics — PostHog (US-hosted) Aggregate measurement of public website usage only, with autocapture and session recording disabled. Loaded only after you accept analytics cookies; see section 6 A pseudonymous identifier, page and event data, and technical request data such as truncated IP address. Never customer field data or platform data
Error monitoring and application performance Diagnosing faults and monitoring availability Technical logs, which may include user or account identifiers
AI and model inference providers Generating recommendations and summaries where AI features are enabled Only the field and account data needed for the request, configured by the customer
Customer support and ticketing Handling and tracking support requests Account details, correspondence, attachments
CRM and marketing automation Managing sales enquiries and business contacts Business contact details, enquiry content
Payment and billing providers Invoicing and payment processing where applicable Billing contact details, invoice and payment records
Professional advisers Legal, accounting, audit and insurance services Only what is relevant to the engagement

The current list of named sub-processors, including their locations and the categories of processing they carry out, is maintained in the Annex to our Data Processing Agreement and is available on request. Where we act as a processor, we give customers prior notice of intended changes to sub-processors and the opportunity to object, as set out in that agreement.

We may also disclose personal data where we are required to do so by law, by a court order or by a competent regulator, and to a prospective buyer in connection with a merger, acquisition or sale of assets, in which case we require the recipient to protect the data on terms no less protective than this policy.

8. International transfers and safeguards

We are a global business and some of our suppliers operate data centres outside your country. Where personal data is transferred out of the European Economic Area, the United Kingdom or Switzerland, we put safeguards in place before the transfer happens:

  • we rely on an adequacy decision of the relevant authority where one exists;
  • otherwise we put in place the Standard Contractual Clauses, together with supplementary measures such as encryption in transit and at rest, access controls and data minimisation; and
  • we assess the laws of the destination country and the practical risk to the data before relying on those clauses.

For customer field data, regional data residency options are available — European Union, United States and Asia-Pacific hosting are offered, and the region that applies to your tenant is recorded in your Order Form. Where residency is specified, the primary storage and processing of that tenant's data takes place in that region. You can ask us for the current hosting regions and transfer impact assessment for your configuration at hello@totalpharmatech.com.

9. How long we keep personal data

We keep personal data only as long as we need it for the purpose we collected it for, or as long as the law requires. The table below shows our standard periods. Customer tenants can configure shorter periods, and the period that applies to a customer's data is set out in the Data Processing Agreement.

Data category Typical retention period Why
Website server logs Up to 30 days, then deleted or aggregated Security, troubleshooting and capacity planning
Analytics and cookie data Up to 14 months from collection Measuring which pages are useful
Demo requests and sales enquiries 24 months from the last contact, then deleted or anonymised Following up an enquiry and keeping a record of our sales activity
Business contacts at prospects and customers Duration of the relationship plus 24 months Account management and legitimate business records
Customer account and user records Duration of the subscription plus 90 days Providing access, support and an accurate record of who had it
Customer field data processed by us Duration of the subscription, then deleted or returned on the customer's instruction, usually within 90 days Delivering the service and honouring the customer's instructions
Support tickets and correspondence 36 months from closure Resolving recurring issues and evidencing the support we provided
Invoices, contracts and tax records As required by local accounting and tax law, typically 6 to 10 years Legal obligation
Audit logs of platform activity Configurable, typically 12 months Security investigation and audit readiness
Backups Rolling 35 days, then overwritten Recovery from failure or data loss

Where a legal claim, investigation or a legal hold requires it, we may keep relevant records for longer, and we restrict access to them until the matter is closed. When a retention period ends we delete the data or irreversibly anonymise it.

10. How we protect personal data

The platform holds commercially sensitive data and personal data about healthcare professionals, so security controls are part of the product rather than an add-on.

  • Encryption of data in transit using TLS, and encryption of data at rest.
  • Role-based access control and least-privilege permissions, so staff and users see only what their role requires.
  • Unique named accounts, support for single sign-on through SAML and OIDC, and configurable session and password policies.
  • Audit logging of changes and access to customer data.
  • Logical separation between customer tenants.
  • Backups with tested restore procedures.
  • Dependency and vulnerability review, and a documented process for applying security fixes.
  • Confidentiality obligations for all personnel, and background checks where local law permits them.
  • A documented incident response process. Where we act as a processor, we notify affected customers without undue delay after becoming aware of a personal data breach, with the information they need to meet their own notification duties.

We choose these measures to be reasonable and proportionate to the nature of the data and the risks involved. That is the standard data protection law asks of us, and it is the standard we hold ourselves to. We are an early-stage business and we describe our controls accurately rather than generously: we do not claim certifications we do not hold — ISO 27001 and SOC 2 are on our roadmap, and we will tell you the current status if you ask.

No system is perfectly secure, and we cannot promise that a security incident will never happen. What we commit to is applying the measures listed above, following the incident response process described in them, and giving affected customers what they need in order to meet their own obligations. Our security questionnaire responses and current control documentation are available to customers and to organisations in evaluation — write to hello@totalpharmatech.com.

11. Your rights

Depending on where you live, you may have some or all of the following rights over personal data we hold about you as a controller.

  • Access — to be told whether we process your data and to receive a copy of it.
  • Rectification — to have inaccurate or incomplete data corrected.
  • Erasure — to have your data deleted where we no longer have a good reason to keep it.
  • Restriction — to limit how we use your data while a question about its accuracy or our lawful basis is resolved.
  • Portability — to receive data you gave us in a structured, commonly used, machine-readable format, or to have it sent to another organisation where technically feasible.
  • Objection — to object to processing based on our legitimate interests, and to object at any time to direct marketing.
  • Withdrawal of consent — where we rely on consent, to withdraw it at any time.
  • Automated decisions — not to be subject to a decision based solely on automated processing that produces legal or similarly significant effects, without human involvement.
  • Complaint — to lodge a complaint with a supervisory authority.

To exercise any of these rights, email hello@totalpharmatech.com. We will respond within one month. If a request is complex or you have made several, we may extend that by up to two further months and we will tell you if we do. We may ask you to confirm your identity before we act. Exercising your rights is free, and we will not treat you differently for doing so.

Where we are a processor, the customer that controls the data decides how a request is answered. We will forward your request to them and assist them in responding.

Complaining to a supervisory authority

You have the right to complain to a data protection authority in the country where you live, where you work, or where you believe an infringement took place. In the European Union and the wider EEA these are the national supervisory authorities listed by the European Data Protection Board; in the United Kingdom the authority is the Information Commissioner's Office. We would ask you to raise the matter with us first, because most concerns are resolved faster that way, but you are not obliged to.

12. Automated decision-making and AI features

Where AI features are enabled, they produce recommendations, prioritisation scores, suggested call plans and summaries that support decisions taken by people. They do not make decisions that produce legal or similarly significant effects on individuals on their own. A manager or representative can review, accept, override or reject each recommendation, and that action is logged.

AI features are modular. A customer can disable them per affiliate, per role or per country, and can choose which model provider is used. Customer commercial data is not used to train models that are shared with other customers. If you are an individual affected by a customer's use of AI features and want to understand how a recommendation about you was produced, contact that customer in the first instance.

13. Children's data

Our website and platform are business tools intended for use by professionals. They are not directed at children, we do not market to children, and we do not knowingly collect personal data from anyone under 16. If you believe that a child has provided personal data to us, write to hello@totalpharmatech.com and we will delete it.

Customers are responsible for ensuring that any data about minors in their tenant is collected lawfully and with whatever additional safeguards local law requires.

14. Customer field data and our Data Processing Agreement

Data that a customer loads into the platform is handled separately from our own marketing and website data, and this section explains how.

  • We process customer field data only on the documented instructions of that customer, including for transfers to another country, unless the law requires otherwise.
  • We do not use customer field data for our own purposes, sell it, share it with other customers, or use it to contact healthcare professionals on our own behalf.
  • Our personnel who can access customer data are bound by confidentiality obligations and are subject to access controls.
  • We assist customers in responding to data subject requests, in meeting their security and breach notification duties, and in carrying out data protection impact assessments where required.
  • At the end of the agreement we delete or return the data as the customer instructs, subject to any legal retention obligation.

These commitments are set out formally in our Data Processing Agreement, which forms part of the subscription agreement and covers the subject matter, duration, nature and purpose of processing, the types of personal data and categories of data subjects, technical and organisational security measures, sub-processor rules and notice of changes, breach notification, audit rights, and deletion or return of data on termination.

A Data Processing Agreement is available for review and signature before any customer data is uploaded. Request it from hello@totalpharmatech.com or through your account manager.

15. Changes to this policy

We review this policy at least once a year and whenever our processing changes. The version and the last updated date are shown at the top of the page. If a change is material — for example a new category of processing or a new purpose — we will announce it on this page before it takes effect and, where we hold your contact details and the change is significant, we will tell you by email.

Where we act as a processor, changes that affect customer field data are handled through the Data Processing Agreement and the customer's instructions, not by updating this page alone.

16. How to contact us

For any question about this policy, or to exercise a privacy right, contact us at hello@totalpharmatech.com.

We do not currently operate a postal address for privacy correspondence. If you need to write to us on paper, contact us by email first and we will provide a correspondence address. Formal legal notices are dealt with under section 19 of our Terms of Service.

If your data was uploaded to the platform by one of our customers, please contact that customer first. We will support them in answering your request.

Questions about data handling before you buy

We will complete your security and privacy questionnaire, share our Data Processing Agreement and confirm the hosting region for your configuration.