PairMotion

PairMotion Privacy Notice

Effective date:

Operator and contact

PairMotion provides business applications for organisations and their authorised users, including the PairMotion Mobile app. The current operator is Lorik Manaj, based in Kosovo. PairMotion is not yet a registered company. A registered operator and the corresponding service agreement will be identified before paid customer service begins.

Contact privacy@pairmotion.com for privacy questions, requests about personal information, or an authorised organisation data-return or deletion request.

Organisation accounts

Accounts are provisioned by PairMotion or authorised organisation administrators; there is no public self-registration. Access depends on the organisation's enabled products, memberships, roles and resource permissions. A person can belong to more than one organisation.

Organisations normally determine the purposes and permitted users of their business and personnel information. We process that information to provide their selected service and carry out authorised instructions. We separately handle account administration, service security, enquiries and operational diagnostics for the purposes described here. An organisation's own privacy notice may also apply to its employees, customers, suppliers and other people in its records.

Information and purposes

We receive information that users and organisations enter, upload or send through the service. Depending on the enabled applications, this can include:

We use this information to provide the selected workflows, authenticate users, enforce access, store authorised records and files, provide available in-app notices, answer enquiries, investigate failures and protect the service. For our own processing, the relevant basis under applicable law depends on the activity: providing a requested or agreed service, legitimate service/security interests, legal obligations, or consent where an optional activity requires it. The organisation is responsible for its basis for information it controls.

The current service has no advertising or usage-trend analytics programme, public signup or payment-card processing. Customer-supplied content may nevertheless contain personal or sensitive data. An upload's filename or category does not determine its actual contents.

Optional Connected Mail

When Connected Mail is enabled for your organisation and account, you choose whether to connect a supported mailbox. Google or Microsoft authorisation takes place with that provider; PairMotion does not ask for your Google or Microsoft account password. Other supported mail services, including the Hostinger preset, may require an app password and incoming/outgoing server settings. Available operations depend on the provider permissions you approve and the capabilities enabled for your connection. An account or organisation membership alone does not give PairMotion access to a mailbox.

We process the mailbox address and provider account identity, message identifiers, sender/recipient details, subjects, dates, unread information and observed mailbox counts to show your mail and keep the connection working. Where enabled and authorised, message bodies and attachments pass through PairMotion to display or download the message you select. Composing and sending processes the recipients, subject, content and files you choose; a message is submitted when you explicitly choose Send. Enabled read/unread controls change that state with your provider. Your provider and the recipients you select receive data needed for those operations under their own arrangements.

Provider tokens and supplied mail passwords are encrypted in the server credential store. We also retain connection/account/organisation identifiers, mailbox address, capabilities, preferences, counts, encrypted synchronisation positions and deduplication fingerprints. These other fields are not all encrypted merely because access is restricted. Message subjects, recipients, bodies, attachment contents and outgoing drafts are not kept as a mailbox archive in our Mail database. Message views and unsent client drafts are temporary working data; explicit downloads can create copies on your device. Your provider continues to hold its mailbox and sent-message copies.

Your connected mailbox is private to your user and organisation context, not automatically shared with colleagues or every organisation administrator. You can use the same connection through your assigned applications where Mail is available; another app entry point does not create another mailbox owner. Generic incoming-mail alerts do not include the sender, subject or body. Existing in-app notification records have their own lifecycle, separate from the mailbox connection.

When you choose a PairMotion mail favorite, we retain a private favorite identifier, encrypted message lookup data and a mailbox-specific encrypted lookup key so the same favorite can be shown through your assigned apps. This does not save a message body or attachment and does not change your provider's stars, flags or read state. A favorite stays until you remove it or disconnect, not merely until a short-lived link expires. We retrieve current permitted metadata to show the list; favorites remain removable even if the provider message is no longer available.

Preparing a favorite can create its mailbox-specific lookup key even if you do not save a favorite. Removing a favorite deletes its private association from the active Mail store; the mailbox-specific lookup key can remain while the connection exists, including when no messages remain favorited. Disconnect removes the favorite associations and their lookup key from the active Mail store. The other history and backup limits below still apply.

A confirmed Disconnect deletes the active stored credential, releases its mailbox slot, clears its active mailbox identity and removes local synchronisation state, deduplication records and pending arrival intake. Minimal connection/request history and minimal command and status records remain to prevent duplicate setup or accidental resends. Additional encrypted per-send verification material has a 30-day cleanup schedule after the send attempt closes, or after an abandoned attempt's deadline; downtime or a backlog can delay processing. This does not make your mailbox connection expire every 30 days. Backups have their separate restricted-access and expiry arrangements, and in-flight, provider and deliberately downloaded copies are not recalled by Disconnect.

Where the Google Disconnect confirmation includes Google cleanup, local removal and provider cleanup are separate outcomes. We keep the Google permission while it is still needed by another PairMotion connection for the same Google account and app registration. When no such connection needs it, we request removal of that Google permission. This does not delete your Google mailbox. Google revocation covers all permissions granted to that PairMotion Google project, not just one device. The app distinguishes pending, unconfirmed and acknowledged cleanup; an acknowledgement is not a guarantee of immediate effect or a statement about a later connection you authorise.

For that coordinated Google cleanup, we may keep a separate encrypted copy of the token needed for cleanup, together with the original request and account binding, after deleting the active mailbox credential. This journal material is not used to read or send mail. We erase that journal token when the original provider acknowledgement is recorded, while keeping minimal status and no-repeat records. If cleanup is pending or unconfirmed, encrypted material can be retained for reconciliation without a fixed automatic expiry; an uncertain request is not automatically resent. This is not covered by the 30-day per-send verification cleanup. The journal contains no message bodies or attachments. Backups retain their separate limits.

For Microsoft and app-password connections, Disconnect does not revoke the provider's authorisation. Where Google cleanup is not available, the confirmation describes local-only removal instead. You can separately revoke PairMotion access in your Google or Microsoft account settings, or revoke an app password with its provider; doing so can interrupt other connections using that permission. An unconfirmed removal is not permission to repeat removal: use Check original request where offered. Disconnect cannot delete your provider mailbox or cancel a message already accepted for sending. Personal-information and organisation-closure requests follow the verification, retention and completion limits described below; we do not promise automatic all-copy erasure.

Google API data is handled under the Google API Services User Data Policy, including its Limited Use requirements. We use mailbox data to provide the connected-mail operations you choose, not for unrelated business analysis. We do not sell mailbox data or use it for advertising, credit decisions or training general-purpose AI models. We do not permit routine staff reading of connected mail; human access requires your specific affirmative permission for the relevant data or is limited to necessary security or legal reasons. These limits also apply to data derived from the Google API information.

Access and service providers

Authorised users receive information according to their memberships, permissions, document sharing and conversation participation. An administrative role does not make every private conversation or personnel document available to that person. One organisation does not gain access to another organisation's records.

Hostinger supplies hosting and company email infrastructure. The website also loads Google font resources; those requests can disclose connection metadata, including an IP address, to Google. We use a restricted operator logging service for technical diagnostics. We do not make that dashboard or its credentials available to ordinary organisation users.

Where phone notifications are available, enrolment is optional. After you choose to enrol and grant the device permission, PairMotion processes an app-installation identifier and notification token to associate that installation with the authorised account and organisation. On iOS, notifications are routed through the Expo Push Service and Apple's Apple Push Notification service (APNs). These services process the delivery token, notification payload and delivery information. PairMotion's phone alerts use generic text and an opaque destination handle, rather than private business messages, documents or financial amounts. Opening the destination still requires current account, organisation and resource access.

You can withdraw notification consent in the app or manage notification permission in your device settings. Withdrawing in-app consent prevents future eligible sends for that scope; device permission controls whether the device displays notifications. Neither can recall a notification already handed to a provider or erase an existing device copy. Push delivery and device-binding records have a separate lifecycle from routine operator logs and organisation business records.

Firebase Crashlytics reporting remains disabled in the current mobile release configuration. The app can still send bounded first-party error/status and timing diagnostics to PairMotion, as described above; this is separate from Firebase reporting. There is no Google Analytics usage-trend programme.

We may disclose information when required by law or necessary to address security incidents or abuse, within applicable legal limits. When a user deliberately exports, shares or opens a file in another application, that application or chosen recipient receives the selected copy under its own arrangements.

Device storage and permissions

The clients use local storage for settings, account/session continuity and temporary working files. Mobile credentials use protected platform storage. Temporary viewer files are separate from original organisation files. Logging out or removing a remembered account is not deletion of server business records or copies deliberately saved outside PairMotion.

File selection and supported local biometric unlock use the relevant platform facilities and permissions. PairMotion does not maintain a biometric-template database for local unlock. Declining an optional capability does not authorise additional collection or grant another person access to private information.

Security and retention

We use access controls, protected credentials and secure public transport. Organisations must manage their authorised users and keep credentials private. No system guarantees perfect security. We do not claim universal encryption at rest, end-to-end encryption of all business content or a compliance certification.

Organisation records and original files remain available for the authorised service unless removed through the applicable workflow or an agreed closure. Retention is determined by their purpose, organisation instructions, applicable obligations and any agreed need to preserve records. Account memberships, sessions, business/audit records and files are different categories.

The shared operator dashboard has a 14-day policy for routine technical events. Source container logs rotate by size, not by that same age limit. Durable business/security history is separate. Temporary working files are cleared by their applicable lifecycle; deliberate external exports remain with their recipient. Backups and service-provider copies can remain after active-data removal and are subject to their own restricted-access and expiry arrangements.

An authorised departing organisation may request return or deletion of its data. We verify authority and agree the scope, available formats, timing, any lawful retention and residual-copy handling. We explain limitations and confirm only the scope actually completed. There is no automatic, instant all-copy deletion or promise that ordinary report downloads are a complete organisation export. Closed organisations are not intended to become indefinite free archives.

Requests and rights

Email privacy@pairmotion.com with the nature of your request and enough account or organisation information to help identify the relevant scope. Do not email passwords, authentication tokens or unnecessary sensitive documents. We may ask for proportionate verification of identity or authority.

Depending on applicable law, you may have rights of access, correction, deletion, restriction, objection or portability, withdrawal of consent for consent-based processing, and complaint to the relevant supervisory authority. In Kosovo, the Information and Privacy Agency is the data-protection supervisory authority.

We coordinate with the organisation when it controls the information and respond within applicable legal requirements. A person's information request is distinct from terminating an organisation's service or erasing other people's records. Lack of public signup does not remove applicable personal-information rights.

International processing and audience

PairMotion is operated from Kosovo, with United States hosting selected for the initial service. Infrastructure providers may process information in additional locations under their service arrangements. Applicable processing/transfer terms must be established before relevant real-customer onboarding; we do not claim an unexecuted certification or transfer arrangement.

The service is for business organisations and their authorised adult users, not a children's consumer service. This does not mean every organisation record is non-sensitive or relates only to adults. PairMotion has no clinical-record module or claim of suitability for specially regulated data. Such use requires a separate assessment and appropriate agreements, not merely an innocuous filename.

Updates

We update this notice when relevant practices change and identify its effective date. Where a change requires a particular notice or choice, we provide it through the applicable process. The privacy contact remains privacy@pairmotion.com.