PrimeBase

PrimeBase Privacy Policy

Last updated: March 22, 2026

At PrimeBase, your privacy is a priority. This Privacy Policy explains how we collect, use, store, and protect your information when you use our platform and services.

By using PrimeBase, you agree to the terms outlined below. If you do not agree, please do not use the Service.

1. Who We Are

PrimeBase is a unified business operations platform developed by VividSphere LLP, headquartered in Bangalore, India.

We are committed to safeguarding your personal and organizational data in compliance with global standards like GDPR and other applicable privacy laws.

2. What Information We Collect

We collect the following types of information:

a. Account Information

  • Name, email address, and organization name
  • Password (securely hashed and salted)

b. Business Data

  • Customer, vendor, project, appointment, and financial data that you or your team enter while using the platform

c. Usage Information

  • Log data, device info, and usage patterns to improve the product experience
  • Browser type, IP address, time zone, and pages visited

d. Communication Data

  • Feedback, support messages, and communications sent to us

e. Optional Google account data

If you connect Google Calendar or Gmail, we access limited Google user data as described in Section 7 below.

3. How We Use Your Information

We use your data to:

  • Provide and improve our services
  • Respond to your requests and support tickets
  • Send you important updates and feature notifications
  • Analyze usage trends and improve product performance
  • Maintain the security and integrity of the platform

We do not sell or share your personal data with third parties for advertising.

If you use our Google integrations, we use Google user data only as described in Section 7—to provide those features inside PrimeBase, not for advertising or unrelated purposes.

4. Data Security

We take data protection seriously:

  • Sensitive data is encrypted at rest and in transit
  • Role-based access control (RBAC) and audit logs are built in
  • Secure infrastructure hosted on trusted cloud platforms
  • Strict internal access policies

For more details, see our Data Security page.

5. Cookies and Tracking

We use minimal, privacy-friendly cookies for:

  • Session management
  • User authentication
  • Performance and analytics (anonymized and aggregated)

You can disable cookies in your browser, though some features may not function properly.

6. Your Rights

If you are located in the EU, UK, or jurisdictions with data protection laws, you may:

  • Access your personal data
  • Request correction or deletion
  • Withdraw consent
  • Request data export

To exercise any of these rights, email us at support@primebase.io.

7. Google user data (Calendar and Gmail)

PrimeBase is developed by VividSphere LLP and is available at primebase.io. This section explains how we access, use, store, and share Google user data when you optionally connect Google Calendar or Gmail. You are never required to connect Google to use PrimeBase.

7.1 Google Calendar

  • We use Google's OAuth scope for calendars created or managed for this application (Google "app-created" calendar access). We do not request access to your primary calendar or to calendars outside that limited scope.
  • We create a dedicated PrimeBase calendar in your Google account (when you connect) and sync appointments and related events you choose to sync—such as creating, updating, or removing events on that calendar so it stays consistent with PrimeBase.
  • Data involved may include event titles, start and end times, descriptions or notes you add through PrimeBase, attendees or metadata needed for sync, and technical identifiers used to match records between PrimeBase and Google.

7.2 Gmail (send only)

  • We request permission to send email on your behalf via the Gmail API (gmail.send scope). We do not access your inbox to read, list, search, or download existing messages. We use Gmail only to transmit messages you compose and send from PrimeBase, using the content and recipients you provide at send time.
  • We access your Google account email address (e.g. via userinfo) so you can see which account is connected and we can associate the integration securely with your PrimeBase account or organization.
  • When you send mail from PrimeBase through Gmail, we process recipients, subject, body, and attachments you provide only to deliver that message and to show send activity in PrimeBase (for example on a deal, project, or customer record), as part of the product you asked us to provide.

7.3 How we use Google user data

We use Google user data only to provide and improve the user-facing calendar and email-sending features you enable. We do not use Google user data for:

  • Targeted advertising, interest-based advertising, retargeting, or user advertisements
  • Selling personal information, data brokerage, or resale to information resellers
  • Determining creditworthiness or lending decisions
  • Building standalone user profiles unrelated to operating PrimeBase for you
  • Training generalized machine learning or artificial intelligence models (beyond what is necessary to provide or improve the specific PrimeBase features you use)

7.4 Sharing, transfer, and disclosure

We do not sell Google user data. We do not disclose Google user data to third parties for advertising or the prohibited purposes listed in Section 7.3.

Google processes OAuth authorization and API requests according to Google's own terms and privacy policies when you sign in and use their services. We may use subprocessors (for example secure cloud hosting) that process data only to operate PrimeBase, under confidentiality and data-processing obligations, consistent with the rest of this policy.

7.5 Security

We protect Google-related credentials and data with the same measures described in Section 4 (encryption in transit and at rest where applicable, access controls, and secure infrastructure). OAuth tokens and integration settings are stored securely and accessed only for the integrations you have enabled.

7.6 Retention and deletion

We retain Google OAuth tokens, calendar sync metadata, and related integration records while your PrimeBase account is active and the integration remains connected, so the features keep working. When you disconnect Google in PrimeBase settings, we stop using Google APIs on your behalf and remove or invalidate stored tokens according to our operational practices.

You can also revoke PrimeBase's access at any time in your Google Account security settings. For broader deletion requests, contact us at support@primebase.io as described in Section 6.

8. Third-Party Services

We use third-party services for hosting, authentication, and analytics. When you connect Google Calendar or Gmail, Google is also a service provider for those optional features, as detailed in Section 7. Other providers are selected carefully and are contractually bound to handle your data securely and compliantly.

9. Data Retention

We retain your data as long as your account is active or as necessary to fulfill legal, regulatory, or operational requirements. You may request deletion at any time. Google integration data and tokens are additionally covered in Section 7.6.

10. Children's Privacy

PrimeBase is not intended for use by individuals under 18. We do not knowingly collect data from minors.

11. Changes to This Policy

We may update this Privacy Policy as needed. If material changes are made, we'll notify you through the platform or via email.

12. Contact Us

If you have any questions about this policy or how we handle your data, please contact:

support@primebase.io