Privacy Policy
This policy describes how Olamide at sip.dobhrap.com handles information when you use its calling, messaging, meetings, contacts, and payment features. Your organization or workspace administrator may also apply its own policies. Features depend on your workspace configuration and permissions.
1. Information we process
- Account and profile details you provide, including name, email, username, phone number, address, workspace membership, and authentication information.
- Communication data, such as message contents, contact relationships, meeting details, call history, routing and usage records, and status or presence settings.
- Imported contact names, email addresses, and phone numbers from Google, a permitted phone address book, or files you choose.
- Invoices, subscriptions, wallet transfers, payment requests, and payment-provider references. Hosted checkout collects payment details with the configured provider; do not send card information in messages or support tickets.
- Security, support, device, and activity information needed to operate the service. Device permissions may include microphone, camera, screen sharing, notifications, contacts, or location when you use a relevant feature.
2. Google Contacts
When you choose Import Google Contacts, Google asks you to select an account and approve the contacts.readonly scope. The app reads contact names, email addresses, and phone numbers through the People API. It does not edit or delete your Google contacts. Access tokens are used in browser memory for that import and are not saved in our application database or browser storage.
Imported contacts are stored in your private Olamide address book. If automatic saving is enabled, import occurs after authorization; turn it off before importing if you prefer to review a selection first. The Google import screen indicates its contact limit. Repeated imports update matching address-book records.
Google-derived contact data is used to provide the contact-import and address-book features. We do not sell it, use it for advertising, or use it to train general-purpose AI models. Our use and transfer of information received from Google APIs must comply with the Google API Services User Data Policy, including its Limited Use requirements. Read Google's policy.
3. Phone contacts and automatic import
Supported browsers require a user action and a system contact selection. The native mobile app requests OS permission before reading contacts. Once permission is granted, automatic import may run at later logins and reads only the contacts the OS allows, including any limited selection. Revoke Contacts permission in your device settings to stop native access. You can turn off automatic saving before an import to use preview and selection instead.
Importing a contact does not send an invitation or message, make that person an Olamide user, or automatically enable SIP calling to them. Names and phone numbers may be personal information about other people; import only contacts you are permitted to use.
4. How we use information
We use information to authenticate users, provision SIP accounts, deliver communications, show presence where enabled, maintain the private address book, process authorized transactions, provide support, and prevent abuse. Optional AI support may process the questions you submit through a configured AI provider. Contact-import data is not automatically submitted to AI support.
5. Sharing and access
Messages and meeting information are shared with the participants you choose. Presence and searchable-directory details follow your settings. Workspace administrators can manage users, policies, and the administrative records their role permits. Authorized infrastructure operators may access stored information to operate, support, or protect the service.
Configured service providers may process information needed for hosting, telecom routing, email delivery, push notifications, payments, or optional AI support. Google receives OAuth and Contacts requests when you connect it. Legal disclosure may occur where required, or to address fraud, security, or protection of rights. Imported contacts are not published in the workspace directory merely because you imported them.
6. Storage, retention, and protection
Account data, messages, imported contacts, and transaction records are stored in the service's databases. Authentication and authorization controls restrict application access; some credentials are encrypted, and network connections use HTTPS where deployed. These controls do not make all stored content end-to-end encrypted or eliminate security risks.
Retention depends on the record type, workspace configuration, operational needs, and legal requirements. Removing a visible item or revoking permission may not immediately remove backups, required billing records, or previously imported contacts. Ask your administrator about the retention rules that apply to your workspace.
7. Your choices and requests
- Manage visibility, presence, forwarding, and profile settings in your account.
- Revoke Olamide's Google access from your Google Account connections. Revocation stops future Google access; it does not erase contacts already imported.
- Revoke phone Contacts, camera, microphone, location, or notification permissions in your device or browser settings.
- Request access, correction, deletion of imported contacts, or account closure through Olamide Support or your workspace administrator. Requests are subject to identity verification and applicable retention obligations.
8. Cookies and local device data
The app uses session cookies and device/browser storage needed for sign-in, preferences, and app operation. Disabling essential cookies may prevent sign-in. The contact-import code does not persist Google access tokens in browser storage.
9. Children and international processing
Olamide is not intended for children under 13. Contact your workspace administrator if a child's information was submitted. Depending on configured hosting and providers, information may be processed in countries different from your location.
10. Contact and updates
For privacy questions, use Support in your Olamide account or the contact information supplied by your workspace administrator. If you cannot sign in, contact that administrator directly. We may update this policy as features or practices change; material changes should be communicated before new uses of Google-derived data.