Skip to content
MobiVista Pro by PortalOne
Features Reporting Industries Security Pricing Docs
Sign in Start for Free
Legal

MobiVista Pro Privacy Policy

On this page 1. Who is responsible for which data 2. Data from console users and account owners 3. Data from managed devices 4. Website visitors 5. Why we use the data and our legal basis 6. Where data is kept 7. How long data is kept 8. Who can see the data 9. Security 10. Cookies and browser storage 11. Your rights 12. Children 13. Changes Contact

DRAFT for legal review. Not yet in force.

Last updated: [DATE]

This policy explains what personal data MobiVista Pro handles, why, where it is kept, for how long, and what rights people have. MobiVista Pro is provided by [COMPANY LEGAL NAME], trading as PortalOne, of [REGISTERED ADDRESS] ("PortalOne", "we", "us").

Contact for privacy questions and requests: [PRIVACY EMAIL]. [DATA PROTECTION OFFICER: NAME AND CONTACT, IF APPOINTED.] [EU / UK REPRESENTATIVE, IF REQUIRED.]

1. Who is responsible for which data

MobiVista Pro is used by organisations ("customers") to manage Android devices they own. The people who use those devices are usually the customer's employees.

DataControllerOur role
Data about devices and device users, collected through the device appsThe customerProcessor, acting on the customer's instructions
Data about the customer's console users, held in their workspaceThe customerProcessor
Account owner and billing details, workspace registration, support ticketsPortalOneController
Website visitors, website chat and contact form enquiriesPortalOneController

If you use a managed device at work, your employer decides what is collected from it and why. Please send questions or requests about that data to your employer first. We will help them answer.

2. Data from console users and account owners

When an organisation registers and when its staff use the console we collect:

  • Registration: company name, website and size; the owner's name and work email; time zone.
  • Console user accounts: full name, username, email, role and status. Passwords are stored only as a one-way hash (bcrypt), never in readable form.
  • Sign-in and activity: sign-in times and the time of the last console activity. We use activity to detect inactive workspaces (see section 7).
  • Audit records: who did what in the console, for example who took remote control of a device, moved devices, restarted or unenrolled a device, or changed a setting.
  • Preferences: display settings and dashboard layout.
  • Notifications shown in the console and sent by email.
  • Console assistant: questions typed into the Ask panel, the answers given and any feedback, kept for 30 days to improve the guides. The assistant runs on our own servers; questions are not sent to an outside AI provider.
  • Support tickets: messages and attachments you send to our support team.
  • Billing: plan, term dates, invoice references and billing contact emails.

3. Data from managed devices

The device apps report to the customer's workspace. What is collected depends on how the customer configures the service. Items marked (if enabled) are only collected when the customer switches the feature on.

Always, while a device is enrolled

  • Identity of the device: serial number, IMEI, Wi-Fi and Bluetooth MAC addresses, manufacturer and model, the name the customer gives it and the user assigned to it.
  • Hardware: processor, memory, storage, screen, SIM slots, NFC.
  • State: battery level and health, free storage and memory, Android version and security patch, uptime, time zone, language, whether Wi-Fi, Bluetooth, location services, developer options and encryption are on.
  • Network: connection type, IP addresses, Wi-Fi network name (SSID) and access point (BSSID), signal strength, mobile carrier, SIM state and roaming, and where Android provides them the SIM phone number and SIM serial (ICCID).
  • Check-ins: when the device last contacted the service.
  • Apps: the managed apps installed, their versions, and install failures with the reason.
  • Commands and results: for example restart, lock, lost mode, unlock, and whether each worked.
  • Data use per device, to show the customer traffic and storage figures.

When used

  • Kiosk sign-in records (if enabled): who signed in to a shared device, when, with what role, and whether the sign-in was checked against the server. Kiosk passwords are stored as a hash.
  • Location (if enabled): latitude, longitude, accuracy and time of each fix, the device's current position, and entries to and exits from zones the customer has drawn. While location tracking runs, Android shows a notification on the device.
  • Full app inventory (if enabled, through a helper app): every app installed on the device.
  • App usage analytics (if enabled): time each app was in the foreground per day, and mobile and Wi-Fi data used per app.
  • Remote control sessions (if enabled): the device screen is streamed live to the console user. The stream is not recorded. We keep a record of who started the session, which device, when, how long it lasted and the data used. Whether the device user is asked for consent, and whether an on-screen banner is shown, are settings the customer controls.
  • Remote file manager (if enabled): file names and folders on the device are listed in the console. Files pulled from or pushed to a device pass through our servers and are deleted 60 minutes after the transfer, whether or not they were collected. The session record (who, which device, files moved) is kept.
  • Live logs (if enabled): the device app's own diagnostic logs, streamed to the console while the view is open. Log lines are not stored as history; the session record is.

What MobiVista Pro does not collect

The device apps do not read the content of messages, emails, photos or calls, and do not record keystrokes. [LEGAL: CONFIRM WORDING WITH ENGINEERING BEFORE PUBLISHING.]

4. Website visitors

  • Website chat: before a chat starts we ask for name, mobile number and email, and record consent. We keep the questions and answers, a shortened (anonymised) form of the visitor's network address, the browser type and the landing page. Chat records are kept for 365 days. The chat assistant runs on our own servers.
  • Contact and support forms: the details and message you send become a support ticket.

5. Why we use the data and our legal basis

PurposeDataLegal basis (where we are controller)
Providing the service the customer configuredSections 2 and 3Contract with the customer. For device data we act on the customer's instructions; the customer chooses its own legal basis
Running accounts, billing and plan limitsRegistration, billing, device counts, usageContract
SupportTickets, and the workspace when we enter it to help (section 8)Contract; legitimate interests
Security, abuse prevention, auditSign-in and audit recordsLegitimate interests; legal obligation
Detecting and cleaning up inactive workspacesLast sign-in and last check-inLegitimate interests
Responding to website enquiriesChat and form detailsConsent; legitimate interests
Service emails (verification, password reset, plan reminders, alerts)Email addressContract

We do not sell personal data, do not use it for advertising, and do not use customer or device data to train AI models.

6. Where data is kept

  • MobiVista Pro is hosted with [HOSTING PROVIDER, e.g. Amazon Web Services] in [HOSTING REGION].
  • Each customer workspace has its own database. Account, billing, support and website data are kept in a separate platform database.
  • [INTERNATIONAL TRANSFERS: SAFEGUARDS TO BE DESCRIBED ONCE THE HOSTING REGION IS FIXED.]

7. How long data is kept

DataKept for
Device history: location history, zone entries and exits, kiosk sign-ins, unlocks, app failures, app usage, support session records, daily fleet figuresSet by the customer: 90 days by default, adjustable from 30 to 730 days
Current device details and current locationUntil replaced by a newer report, or until the device is removed
Console notificationsSet by the customer: 7 days by default, up to 90 days
Files moved with the file manager60 minutes
Console assistant questions30 days
Sent email copies30 days
Storage and bandwidth usage history12 months
Billing history and plan changesFor as long as needed as billing evidence [LEGAL: SET A PERIOD]
Support ticket attachments365 days after the ticket closes
Website chat365 days
Records of our staff entering a workspace[LEGAL: SET A PERIOD]

Inactive workspaces on the Free plan are deleted automatically:

  • email never verified: deleted 7 days after sign-up;
  • verified but no device ever enrolled: warned at 30 days of inactivity, suspended at 45, deleted 30 days after suspension;
  • used, then inactive: warned at 60 and 75 days, suspended at 90, deleted 30 days after suspension.

"Inactive" means no console sign-in and no device check-in. A suspended workspace can be reactivated in one click. Paid and trial workspaces are not deleted automatically.

When a workspace is deleted, its whole database, including uploaded apps and files, is permanently deleted and cannot be recovered. We keep only a minimal record that the workspace existed (its id, dates and the reason), with no personal data.

8. Who can see the data

  • The customer's console users, limited by their role and, where set, by device group.
  • Our support staff, who can enter a workspace with the same view as its owner, to give support or investigate a problem. Every entry is recorded in a log the customer cannot alter.
  • Sub-processors that help us run the service:
Sub-processorWhat it doesData involved
[HOSTING PROVIDER]Hosts servers and databasesAll service data
Google Firebase Cloud MessagingDelivers push messages that wake a device or tell it to check inDevice push token; short commands, and the text of a message an admin sends to a device
[EMAIL PROVIDER FOR PLATFORM EMAIL]Sends platform emails (verification, password reset, support, and alerts for workspaces without their own mail server)Recipient email address and message content

Customers can set their own mail server for their workspace's alert emails. Those emails are then sent through the customer's own provider, which is the customer's choice and not our sub-processor.

Services your browser contacts directly. Pages load some files from other services, which see your IP address:

  • Google Fonts (fonts on the console and website);
  • unpkg.com (open-source libraries for the console);
  • OpenFreeMap (map tiles in the console);
  • OpenStreetMap Nominatim (place search when drawing zones; receives the text typed into the search box).

[LEGAL: DECIDE WHETHER TO SELF-HOST THESE OR LIST THEM AS SUB-PROCESSORS.]

We may disclose data where the law requires it. We will tell the customer first unless the law forbids it.

9. Security

In plain terms, the service is protected by:

  • encryption of traffic between devices, the console and our servers (HTTPS);
  • a separate database for each customer workspace;
  • passwords stored only as one-way hashes;
  • each device authenticating with its own secret, issued at enrolment;
  • role-based access for console users, with optional limits by device group;
  • audit records of sensitive actions, including remote control and staff access;
  • automatic deletion of temporary files and expired history.

No system is perfectly secure. We will notify affected customers without undue delay if we become aware of a personal data breach affecting their data.

10. Cookies and browser storage

Console

NamePurposeLasts
mobivistapro_authKeeps you signed in8 hours, extended while you are active
Antiforgery cookie (.AspNetCore.Antiforgery.*)Protects forms against cross-site attacksBrowser session

The console also stores display preferences in your browser's local storage.

Website

NamePurposeLasts
Antiforgery cookie (.AspNetCore.Antiforgery.*)Protects the chat and contact formsBrowser session

All are strictly necessary. Neither the console nor the website uses analytics, advertising or tracking cookies.

11. Your rights

Depending on where you live you may have the right to access, correct, delete or export your data, to object to or restrict its use, and to withdraw consent.

  • Device users and console users of a customer: contact the customer (usually your employer). We will help the customer respond.
  • Account owners, website visitors and anyone whose data we control: email [PRIVACY EMAIL]. We will reply within [ONE MONTH / STATUTORY PERIOD].
  • Customers can export every report to CSV from the console at any time. A full workspace export or deletion can be requested at [PRIVACY EMAIL].

You can also complain to a data protection authority, for example [SUPERVISORY AUTHORITY].

12. Children

MobiVista Pro is a business service and is not directed at children. [LEGAL: ADD WORDING IF CUSTOMERS MAY ISSUE DEVICES TO UNDER-18S, FOR EXAMPLE IN EDUCATION.]

13. Changes

We will post changes here and update the date at the top. We will email workspace owners about material changes at least [30] days before they take effect.

Contact

[COMPANY LEGAL NAME], [REGISTERED ADDRESS], [PRIVACY EMAIL].

MobiVista Pro

A cloud console for the Android devices your business owns. Android only. Cloud only.

Product Features Reporting Pricing
Company Industries Security Contact
Support Documentation Support Sign in to the console

© 2026 PortalOne FZE. Terms of Service Privacy Policy mobility-web.portalonewifi.com
Ask about MobiVista Pro
Answers from our documentation, not a sales script.

Tell us who you are and ask anything about MobiVista Pro. We will only use these details to reply to you.

Your details and this conversation are kept for up to 12 months so we can follow up, and are not shared with anyone else.

AI assistant. Check anything important with us.