Legal

Privacy policy

Last updated 13 November 2026. This page is public. No sign-in is required to read it.

This policy identifies the operator as CallVer and uses midoryad753@gmail.com as the contact address. It does not state a registered company name, a physical address, or a governing law. Those details are not settled and should be reviewed before commercial launch.

Who operates CallVer

CallVer is a commercial Android application for businesses that need employee telephone call reporting. In this policy, “CallVer” means the operator of the application and its licensing service, identified for now only by that name. “The company” means the business that licenses CallVer and chooses the email address that receives reports. “The employee” means the person who uses the app on an Android phone.

CallVer provides the software and the licensing service. The company decides to use call reporting with its workforce, tells its employees what the app does, and configures the reporting address. This policy describes the product as it is built. It is not a certification, and it does not say that Google has approved CallVer.

Information CallVer processes

CallVer processes information in two separate places: on the employee’s phone, where call reports are created, and in the licensing service, where accounts and company settings are kept.

On the phone

• The worker name the employee enters. This is the name printed on the report. It is stored on the phone and is not the same field as the Google account display name.
• Call details recorded during a tracking session: phone number, direction (incoming, outgoing, or missed), date and time, and duration.
• A status label the app attaches to a recorded call, and a short duration summary inside the workbook.
• A caller-name column in the workbook. The session report records this as Unknown. CallVer does not fill it from names saved in the phone’s contacts.
• The session’s start and stop times.
• The employee’s Google email address, a flag that send permission was granted, the company reporting address cached for that company, and the licensing session credential.
• The Excel file and a small send record, kept on the phone until Gmail accepts the report or the file remains because sending did not complete.

In the licensing service

• The Google account identifier, email address, and display name used to recognize the person.
• Company name, reporting email, employee limit, and whether the company is active or suspended.
• Membership: whether a person is an employee or a company administrator, and whether that membership is active.
• A hash of the company employee key and a hash of an administrator invitation. The licensing service does not store those secrets in plaintext.
• A hash of the employee session credential, when the session was created, when it was last seen, when it expires, and whether a tracking session is currently active. An employee session is currently issued for 30 days. That period describes the session credential. It is not a retention period for call reports, and it is not a promise that the period will never change.

The licensing service does not store call logs, call details, or Excel reports.

Phone and call permissions

CallVer asks Android for permission to read phone state and the call log. It uses those permissions to recognize telephone activity during a session the employee has started, and to record the number, direction, time, and duration of calls the phone provides. These details are call metadata. CallVer does not record conversations, listen to calls, or capture call audio.

The app can show a persistent notification while a session is running, and a notification about report delivery. On Android 13 and later it asks for notification permission. If the employee allows an overlay, CallVer can show a small indicator over other screens. The app may ask to be exempted from battery restrictions so a session is less likely to be stopped. If a session was still marked on when the phone restarts, CallVer attempts to start tracking again. Android can block that restart.

The report created at the end of a session does not look up saved contact names, and the runtime permission check that starts tracking asks for phone state, the call log, and, when required, notifications.

Call information is processed. It is written into the report on the phone and emailed to the company’s reporting address. It is not sent to the licensing service as call content.

Google identity

Employee identity and Gmail sending are separate steps.

To enroll, the employee signs in with Google. The phone receives a Google ID token and sends it to the licensing service, which verifies it. The service then stores the Google account identifier, email address, and display name. The employee enters the company employee key. The key is used to enroll that account with the company. The app is written so the key is not saved on the enrollment screen. The licensing service stores a hash of the key.

The enrollment exchange is for identity and licensing. It does not grant CallVer permission to read the employee’s mailbox.

The identity request uses these scopes:

• openid
• https://www.googleapis.com/auth/userinfo.email
• https://www.googleapis.com/auth/userinfo.profile

Gmail authorization

Sending a report requires a separate authorization on the employee’s own Google account. CallVer asks for permission to send mail. It does not ask for permission to read, modify, or manage the mailbox, and it does not request a restricted Gmail scope.

The send authorization requests:

• openid
• https://www.googleapis.com/auth/userinfo.email
• https://www.googleapis.com/auth/userinfo.profile
• https://www.googleapis.com/auth/gmail.send

gmail.send is required because the report is sent through the Gmail API from the employee’s account. CallVer calls Gmail’s send method with a message the app itself has built. It also asks Google’s userinfo endpoint for the verified email address, and it checks that the send permission was actually granted. If send permission is missing, the report is not sent that way.

CallVer does not read Gmail inboxes. It does not request full mailbox access. The Gmail permission stays with Google Play services on the phone. The app does not store the Google access token, refresh token, or client secret.

A report is sent only from the Google address connected for that employee. CallVer will not send it from a different connected account.

How reports are generated and delivered

When the employee ends a session that recorded calls, and a worker name, a connected Google account, and a company reporting address are available, CallVer builds an Excel workbook on the phone. The email message includes the worker name, the date, the session start and stop times, and a line for each recorded call with the phone number, duration, and status label. The workbook adds the call direction, the date and time, the caller-name column recorded as Unknown, and a short duration summary.

The file is saved in the app’s private storage before it is sent. CallVer then submits the message to https://gmail.googleapis.com/gmail/v1/users/me/messages/send. The message is from the employee and to the company’s reporting address.

If the phone is offline, or Gmail does not accept the message yet, the Excel file remains on the phone so it can be sent later. If a send is interrupted and CallVer cannot tell whether Gmail already accepted it, that report is not sent again automatically. After Gmail accepts a report, the app deletes that Excel file and clears the on-device call-report list for the accepted send. The session list used to build the file is cleared once the file has been saved, which can be earlier than Gmail’s acceptance.

The delivered message then sits in the company’s mailbox and in the employee’s Sent mail, under Google’s and the recipient’s mail systems. CallVer does not control how long those mailboxes keep it. Acceptance by Gmail does not mean the recipient has opened the message.

What is transmitted to the licensing service

The licensing service, hosted on Cloudflare, receives and stores the account, company, and session information listed above. The phone tells the service when a tracking session becomes active or inactive. That signal is a yes-or-no work state. It does not include phone numbers, call details, or the Excel file.

The service is used for licensing, employee enrollment, authentication, and company administration, including the reporting address and whether a membership is active. A company administrator can update the reporting address through the app. Gmail access tokens are not sent to this service.

New employee enrollment requires an online licensing check. A previously verified employee can start or continue a tracking session offline for up to 72 hours from the last successful verification when the licensing service is unavailable. If the licensing service is reached and explicitly refuses the license, that refusal overrides the grace period and stops tracking.

Google user data and Limited Use

CallVer’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Google user data is used to provide the user-facing features of CallVer: recognizing the employee, enrolling that person with a company, and sending the report that employee generated. CallVer does not sell Google user data. It does not use Google user data for advertising. It does not use it to determine creditworthiness. It does not use it to train generalized models. CallVer personnel do not read the contents of an employee’s Gmail mailbox through the product. The report email is delivered to the company address as the feature the employee authorized.

This website does not use Google user data, and it does not include advertising or analytics scripts.

How Google account access can be revoked

The employee can sign out in CallVer. Sign-out asks Google to revoke the scopes CallVer requested and attempts to end the licensing session on the phone and at the licensing service. If revocation does not succeed, the app keeps the employee signed in and says so.

The employee can also remove CallVer from the Google Account permissions page at myaccount.google.com/permissions. Removing access there stops CallVer from sending further mail with that grant. It does not by itself delete a report already delivered to the company’s mailbox, and it does not by itself delete licensing records.

Retention, deletion, and security

CallVer does not publish a fixed retention period for licensing and account records. Those records remain while the account and company are kept in the service. There is no self-service deletion control in the app or on this website, and this policy does not promise automatic deletion or a deletion deadline.

On the phone, an accepted report’s Excel file and the on-device call-report list are removed after Gmail accepts the send, as described above. A report Gmail has not accepted remains on the phone. Android backup is enabled. The sign-in store and the folder of unsent reports are excluded from Android backup and device transfer. This policy does not claim that every other local setting is excluded.

The worker name, the on-device call list, and the saved sign-in record use Android’s encrypted preferences. The Excel file is stored in the app’s private file area. This is a description of the current implementation. It is not a security certification, and it does not describe protection of the email after it leaves the phone.

People whose information CallVer processes can write to midoryad753@gmail.com. CallVer will review the request and respond. Depending on where a person lives, applicable law may provide additional rights. This page does not promise a statutory response time and does not claim a compliance certification.

CallVer is a workplace tool for companies and their employees. It is not directed at children.

Changes

If this policy changes, the updated page will be published at this address with a new date. Continued use of CallVer after an update is subject to the commercial arrangement with the company and to the policy then published.

Contact

Privacy questions and requests go to midoryad753@gmail.com. Please describe the company, the Google account if the request is about one, and what you are asking CallVer to review.

Details still to confirm before commercial launch

• The registered name of the operator, if one will be used.
• A physical address.
• A governing law and venue.
• A published retention schedule for licensing records, if one is adopted.
• Any future deletion process. None is offered today beyond reviewing a request sent by email, sign-out, and the on-device cleanup described above.