Provider sign-in
Supported source authorisation opens the provider’s browser flow. Datplan does not ask users to type provider passwords into the public website.
Security and trust
Privacy-first reporting begins with a clear data boundary
Datplan keeps pulled provider datasets in the desktop reporting workflow rather than a Datplan-hosted analytics warehouse. It also explains the limited online account and service records that still exist.
Where data is handled
Source datasets and service records serve different purposes
On the customer’s Windows PC
- Pulled source datasets
- Local Datplan reporting data
- Dashboards and layouts
- CSV, JSON and BI export files
- User-created backups and reports
Datplan service controls may include
- User and sign-in identifiers
- Source-access and provider connection references
- Plan, billing and usage counters
- Run status and error state
- Support and service communications
Provider authorisation
Use the provider’s consent flow—not shared passwords
Connect only accounts you are authorised to use, review the provider’s permissions and revoke access from provider settings when it is no longer required.
Token handling
Authorised access and refresh tokens are handled for source requests and are not shown on public pages or routine app screens.
Provider limits
Permissions, endpoint availability, API quotas and service availability remain controlled by the source provider.
Customer controls still matter
- Protect the Windows account and device
- Use device encryption where appropriate
- Restrict access to export folders and backups
- Separate client and source folders
- Remove old exports under the organisation’s retention policy
- Review any later BI cloud publication separately
Local does not mean risk-free
Anyone who can access the device, backup or exported file may be able to read business data. Datplan cannot secure copies that users move into email, shared drives, BI services or other applications.
Security questions
The operational boundary in plain language
Where does Datplan store pulled source data?
Provider source datasets are stored in the local app data and user-selected export folders on the Windows PC. Datplan does not operate a hosted analytics warehouse for those reporting datasets.
Does local storage mean Datplan has no online services?
No. Datplan online services still handle the account, sign-in, source-access, billing, allowance, run-state and support controls needed to operate the product.
Who protects exported files?
The user and their organisation are responsible for the Windows account, device encryption, backups, folder permissions, file sharing, retention and any BI service to which files are later published.
What should I send to support?
Start with the source name, app version, run time, status, non-sensitive error text and a sanitised screenshot. Do not send passwords, tokens, authorisation codes, raw source data or full local databases.
See Datplan with real reporting data—without connecting a live account
The Windows app is free to download and includes Datplan Demo data, so you can test sync, dashboards, reporting grains and exports first.