DriveView Privacy Policy
Last updated: 15 September 2026
Who we are
DriveView is a marketing analytics platform operated by Astra Digital Internasional. It presents advertising, analytics and search performance data to the agency staff who manage a client's campaigns and to the client stakeholders granted access to that client's workspace.
DriveView is not a public service. There is no sign-up: every account is created by an administrator or by a single-use invitation issued to a named person. This policy covers the DriveView application and its product pages on librum.id.
What we collect
| Category | What it includes | Where it comes from |
|---|---|---|
| Account data | Name, email address, job title, role, and the workspaces you are a member of. | Given to us by you or by the administrator who invited you. |
| Advertising and analytics data | Campaign, ad group, ad and creative performance; spend, impressions, clicks, conversions and conversion value; search queries; page-level performance; and the change history of a connected advertising account. | Retrieved on your instruction from the platforms you connect, or from a data warehouse you point us at. |
| Credentials | OAuth tokens and warehouse credentials for the sources you connect. | Entered by an administrator, or issued by the platform during an authorisation flow you complete. |
| Technical data | Session identifiers, and application errors reported by your browser. | Generated as you use the service. |
| Activity records | An append-only log of actions taken in a workspace, in particular who approved a change to an advertising account and what that change was. | Generated as you use the service. |
The advertising data we hold describes campaigns and their performance. We do not collect or store the personal data of the people who saw or clicked an advertisement, and we do not build or hold audience lists, profiles or identifiers for individuals.
Why we hold it
- To show you your own performance data, at the level of detail and over the period you ask for.
- To generate optimisation recommendations for the campaigns we manage, and to record the decisions taken on them.
- To answer the questions you ask the built-in assistant.
- To produce the periodic reports and media plans a client engagement calls for.
- To keep the service secure, and to be able to reconstruct who changed what.
We do not sell your data. We do not use one client's data to serve another, and we do not pool data across clients to build benchmarks, models or training sets.
Google user data
DriveView's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
When an administrator connects Google Ads, DriveView requests only the Google Ads scope
(https://www.googleapis.com/auth/adwords).
With that access, DriveView:
- reads each account's name, currency, time zone and manager account hierarchy; each campaign's status, serving status, type, bidding strategy type and daily budget; and each ad's approval and policy status;
- applies only changes that a person with approval rights has reviewed and approved in DriveView: pausing a campaign, resuming a paused campaign, or changing a campaign's daily budget;
- never creates or removes campaigns, and never manages Google Ads users or billing.
Data retrieved from Google APIs is:
- used only to display and report on your own advertising performance, and to apply changes you explicitly approve;
- never transferred to others except as needed to provide or improve those features, to comply with applicable law, or as part of a merger or acquisition following notice to you;
- never used for advertising, and never sold;
- never used to train generalised artificial intelligence or machine learning models;
- never read by a human except with your explicit consent, to resolve a specific support issue you have raised, where required by law, or in aggregated and anonymised form for internal operations.
The assistant, and the AI providers behind it
DriveView includes an assistant, Vision AI, that answers questions about a workspace's own data. To produce a reply, the relevant rows and your question are sent to our AI provider, under a commercial agreement that prohibits using our data to train their models. The assistant can read your workspace's data and draft documents and recommended changes; it cannot change anything in a connected advertising account.
How long we keep it
DriveView holds a rolling window of platform data rather than a permanent copy. Retention is configured per connected dataset and is capped at 190 days; a nightly job deletes rows past the window. Account data is held while your account is active. Records of who approved a change are retained for as long as an accurate history is needed, because that is the point of them.
Who we share it with
- Within your workspace. Members of a workspace see that workspace's data. Agency staff see the clients their agency manages. One client cannot see another's data.
- Our AI provider, for the assistant, as described above.
- Our hosting and infrastructure providers, who process data on our instructions in order to run the service.
- Nobody else. We do not share your data with advertisers, data brokers or analytics networks.
How we protect it
- All traffic is served over HTTPS.
- OAuth tokens and every other third-party credential are encrypted before they are written to the database, and are never displayed back to any user.
- Access is by named login only; there is no shared or anonymous access, and no public sign-up.
- Every query for a client's data is scoped to the workspaces you belong to, enforced in the data layer.
- Credentials can be entered only by administrators, never by a client user.
Your rights
You may ask us for a copy of the personal data we hold about you, ask us to correct it, or ask us to delete it by writing to hello.there@librum.id. You may also withdraw DriveView's access to a Google account at any time at myaccount.google.com/permissions, which immediately ends our access to it.
Changes to this policy
We may update this policy. The date at the top of this page always reflects the current version, and we will tell administrators before a material change takes effect.
Contact
Questions about this policy, or about the data we hold, go to hello.there@librum.id.