BugPort Privacy Policy

Effective Date: June 23, 2026  ·  Last Updated: June 23, 2026

BugPort is provided by Gurushi Global Solutions LLP (“BugPort,” “we,” “us,” or “our”). This Privacy Policy explains how we collect, use, store, disclose, and protect information when you use BugPort, including our website, web application, Chrome extension, support services, and related products or services.

BugPort is a bug reporting tool that helps users capture and submit browser-based bug reports with screen recordings, screenshots, logs, network metadata, browser and device information, and related debugging context. Because BugPort is designed to capture technical issue reports, some reports may contain personal information, website content, or other sensitive information depending on what the user chooses to capture.

By using BugPort, you agree to the practices described in this Privacy Policy.

1. Scope of this Privacy Policy

This Privacy Policy applies to:

• The BugPort website at bugport.ai
• The BugPort web application at app.bugport.ai
• The BugPort Chrome extension
• BugPort support pages and help resources
• BugPort APIs and backend services
• BugPort-related communications, support requests, and account services

This Privacy Policy does not apply to third-party websites, services, or applications that BugPort does not own or control.

2. What BugPort Does

BugPort helps users create bug reports by capturing relevant debugging context. Depending on how a user uses BugPort, a bug report may include:

• Screen recordings
• Screenshots
• Console logs
• Network request metadata
• Page URL and page title
• Browser and device information
• Display and screen information
• User-provided descriptions, notes, attachments, and comments
• Workspace, project, and team context
• Authentication and account information needed to submit the report

BugPort uses this information to help users, developers, support teams, QA teams, and product teams reproduce, understand, and fix software issues.

3. Information We Collect

We collect information in several ways: information you provide directly, information captured when you use BugPort features, information generated by your browser or device, and information processed through integrations.

3.1 Account and Profile Information

When you create or use a BugPort account, we may collect:

• Name
• Email address
• Account ID
• Workspace or organization name
• Team membership information
• Role or permissions within a workspace
• Authentication provider information
• Profile image, if provided
• Account settings and preferences

We use this information to create and manage your account, authenticate you, provide workspace access, and associate bug reports with the correct user or team.

3.2 Authentication Information

BugPort may process authentication information such as:

• Login session tokens
• Refresh tokens
• OAuth tokens
• Authentication provider identifiers
• Session metadata
• Sign-in status
• Workspace authorization state

This information is used to keep you signed in, verify account access, connect your browser extension to your BugPort account, and allow you to submit reports to the correct workspace or project.

BugPort does not ask for or intentionally collect your passwords for third-party websites. You should not include passwords, API keys, private keys, payment information, or other secrets in BugPort reports or support messages.

3.3 Bug Report Content

When you create a bug report, BugPort may collect the content you choose to capture or submit, including:

• Bug title
• Bug description
• Steps to reproduce
• Expected result
• Actual result
• Comments and notes
• Labels, tags, project names, workspace names, and assignees
• Attachments uploaded by you
• Files associated with a report
• User-generated text or metadata submitted with the report

This information is used to create, organize, store, and display bug reports.

3.4 Screen Recordings and Screenshots

When you start a BugPort capture, BugPort may collect:

• Screen recordings
• Tab recordings
• Window recordings
• Desktop recordings
• Screenshots
• Visible page content
• Images, text, videos, UI elements, and other content visible in the captured area
• Cursor movement, clicks, scrolling, or visual interactions visible in the recording
• Annotation data, such as drawings, highlights, blur areas, or notes

Screen recordings and screenshots may include personal information or sensitive information if it is visible on your screen or browser page at the time of capture.

BugPort only uses this information to provide bug reporting, recording, review, storage, export, sharing, and related product functionality.

3.5 Browser Page and Website Context

When you use BugPort to capture a bug report on a webpage, BugPort may collect page-level context such as:

• Current page URL
• Page title
• Domain name
• Tab ID or browser tab metadata
• Browser window state
• Selected tab or selected screen
• Page metadata needed to associate a report with the correct website or application
• User-selected page content included in screenshots or recordings

BugPort collects this information so developers can understand where the issue occurred and reproduce it more easily.

3.6 Console Logs

When you create a bug report, BugPort may collect browser console information such as:

• Console messages
• JavaScript errors
• Warnings
• Error stack traces
• Log timestamps
• Source file references
• Error metadata

Console logs may include information printed by the website or application being tested. Depending on the website, console logs may accidentally contain personal information, identifiers, tokens, or other sensitive information. BugPort attempts to support debugging workflows, but users and teams should avoid logging secrets in websites or applications.

3.7 Network Metadata

When you create a bug report, BugPort may collect network request metadata to help developers diagnose failed requests or broken application behavior.

This may include:

• Request URL
• Request method
• Request status code
• Request timing
• Request headers
• Response headers
• Request type
• Resource type
• Error messages
• API endpoint metadata
• Network failure information
• Request and response size metadata
• Timestamps

Depending on product configuration, BugPort may also capture limited request or response body information where necessary for debugging. BugPort may redact or exclude sensitive values where possible, such as passwords, authorization headers, cookies, API keys, and token-like values.

Network metadata is collected only to support BugPort’s bug reporting and debugging functionality.

3.8 Device, Browser, and Environment Information

BugPort may collect technical environment information such as:

• Browser name and version
• Operating system
• Device type
• Display size and screen resolution
• Monitor or display information
• Timezone
• Language or locale
• Memory or storage availability
• Extension version
• Capture settings
• Recording configuration
• Media device availability, such as microphone or camera permission state
• Error diagnostics related to recording or upload failures

This information helps developers reproduce issues and helps BugPort troubleshoot product performance.

3.9 Location and IP-Derived Information

BugPort may collect approximate location or network context derived from your IP address, such as:

• IP address
• Country
• Region
• City-level approximation
• Timezone
• Internet service provider or network metadata, where available

BugPort may use a third-party IP geolocation provider, such as ipapi.co, to obtain approximate location or timezone context for diagnostic purposes.

We use this information to help developers understand environment-specific issues, timezone-related bugs, region-specific failures, and diagnostic context. BugPort does not use IP-derived location data for advertising, creditworthiness, or unrelated tracking purposes.

3.10 Google Drive and Google Account Information

If you choose to use Google Drive export or Google account features, BugPort may process:

• Google OAuth authorization information
• Google account identifier
• Google Drive file metadata
• Files created or saved by BugPort in your Google Drive
• Google Drive folder information needed to save recordings or exports

BugPort uses Google Drive access only to provide user-requested Google Drive functionality, such as saving recordings or exported bug report assets.

BugPort does not use Google Drive access to read unrelated files in your Drive.

3.11 Local Browser Storage

The BugPort Chrome extension may store information locally in your browser, including:

• Authentication state
• Session tokens
• Extension settings
• Workspace and project selection
• Recording state
• Temporary recording chunks
• Screenshots
• Draft bug report data
• Capture metadata
• Upload state
• Recovery data for interrupted recordings
• User preferences

Local storage is used to make the extension work reliably, preserve recording state, support large uploads, and recover from browser or network interruptions.

Some locally stored data may remain on your device until you delete it, clear browser storage, uninstall the extension, or complete an upload or deletion workflow.

3.12 Support Communications

When you contact BugPort support, we may collect:

• Name
• Email address
• Workspace or company name
• Issue description
• Browser and operating system details
• Screenshots or files you attach
• Support conversation history
• Diagnostic details you choose to provide

We use this information to respond to support requests, troubleshoot issues, improve BugPort, and maintain customer records.

3.13 Payment and Billing Information

If BugPort offers paid plans, we may collect billing-related information such as:

• Billing name
• Billing email
• Company name
• Billing address
• Subscription plan
• Payment status
• Invoice information
• Tax information
• Transaction metadata

Payment card details are typically processed by a third-party payment processor. BugPort does not intentionally store full credit card numbers on its own servers.

If payment processing is not currently enabled, this section applies only when paid plans or billing features are introduced.

4. Information We Do Not Intentionally Collect

BugPort does not intentionally collect the following unless you choose to include it in a bug report, screenshot, recording, upload, or support message:

• Passwords
• Full payment card numbers
• Government identification numbers
• Health information
• Financial account credentials
• Private keys
• API secrets
• Authentication cookies for third-party websites
• Sensitive personal communications
• Content unrelated to a user-initiated bug report

Because BugPort captures screenshots, recordings, logs, and website content selected by users, sensitive information may be included accidentally if it appears on the screen, in logs, in network data, or in user-provided attachments. Users should review reports before sharing them and avoid capturing sensitive information where possible.

5. How We Use Information

BugPort uses collected information to:

• Provide bug reporting functionality
• Capture screen recordings and screenshots
• Collect logs and network metadata for debugging
• Create, store, display, and manage bug reports
• Associate reports with the correct workspace, project, user, and team
• Authenticate users
• Support collaboration between users and teams
• Upload and process report assets
• Export files or recordings when requested
• Provide support and troubleshooting
• Improve BugPort reliability and performance
• Monitor and prevent abuse, fraud, and security incidents
• Maintain service availability
• Comply with legal obligations
• Enforce our terms and policies

We do not use user data to determine creditworthiness or for lending purposes.

We do not sell user data.

We do not use bug report content, screen recordings, screenshots, logs, network metadata, or website content for advertising or unrelated tracking.

6. Chrome Extension Permissions and Why They Are Used

The BugPort Chrome extension may request permissions needed for its bug reporting features. These permissions may include:

Host Permissions

BugPort may request access to websites so it can show the capture UI, capture selected pages, collect logs, collect network metadata, and create bug reports on pages where users choose to use BugPort.

BugPort uses these permissions only to provide its bug reporting functionality.

7. When BugPort Collects Data

BugPort may collect data when:

• You install or enable the Chrome extension
• You sign in to BugPort
• You open the BugPort web app
• You select a workspace or project
• You start a bug report
• You start a screen, tab, window, or desktop recording
• You capture a screenshot
• You add notes, annotations, attachments, or comments
• You submit or upload a report
• You export or download a recording
• You use Google Drive export
• You contact support
• You experience an error that requires diagnostic troubleshooting

BugPort is designed to collect detailed bug report data when users initiate capture or reporting workflows.

8. How We Share Information

BugPort may share information with the following categories of recipients:

Workspace Members and Team Users

Bug reports may be visible to users in the same workspace, organization, or project depending on permissions and settings.

Service Providers

We may share information with service providers that help us operate BugPort, including providers for:

• Cloud hosting
• Database storage
• Authentication
• File storage
• Video upload and processing
• Email delivery
• Customer support
• Analytics and diagnostics
• Security and abuse prevention
• Payment processing

These providers may process information only as needed to provide services to BugPort.

Third-Party Integrations Requested by Users

If you choose to connect or use an integration, BugPort may share data with that integration. For example:

• Google Drive, when you choose to save or export recordings to Google Drive
• Authentication providers, when you sign in using an external identity provider
• Storage or upload providers, when recordings or files are uploaded for report creation
• IP geolocation providers, when approximate location or timezone context is collected for diagnostics

Legal, Security, and Compliance

We may disclose information if necessary to:

• Comply with law, regulation, legal process, or government request
• Enforce our terms or policies
• Protect the rights, safety, and security of BugPort, users, or the public
• Detect, prevent, or address fraud, abuse, security incidents, or technical issues
• Respond to claims that content violates the rights of others

Business Transfers

If BugPort is involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, information may be transferred as part of that transaction, subject to appropriate protections.

9. Third-Party Services

BugPort may use third-party services to operate its product. Depending on your configuration and use, these may include:

• Cloud infrastructure providers
• Authentication providers
• Database and storage providers
• File upload and media processing providers
• Google services, including Google OAuth and Google Drive
• IP geolocation providers, such as ipapi.co
• Video or file upload infrastructure providers
• Email and support providers
• Payment processors
• Security, monitoring, and diagnostics providers

Third-party services process information according to their own privacy policies and contractual obligations with BugPort.

10. Data Retention

We retain information for as long as reasonably necessary to provide BugPort, comply with legal obligations, resolve disputes, enforce agreements, maintain security, and support legitimate business purposes.

Retention periods may vary depending on the type of data:

• Account information is generally retained while your account remains active.
• Workspace and project data is retained while the workspace or project remains active.
• Bug reports, screenshots, recordings, logs, attachments, and metadata are retained until deleted by an authorized user or according to workspace retention settings.
• Temporary local recording chunks may be deleted after upload, export, cancellation, browser cleanup, or extension uninstall.
• Support communications may be retained for customer service, legal, and operational purposes.
• Security logs may be retained for security, fraud prevention, and compliance purposes.

If you delete a report, workspace, or account, some information may remain in backups or logs for a limited period before deletion according to our backup and retention practices.

11. User Controls and Choices

Depending on your account, workspace settings, and permissions, you may be able to:

• Start or stop captures
• Choose what tab, window, or screen to record
• Review a bug report before submitting it
• Delete reports
• Delete recordings or attachments
• Change workspace or project selection
• Disconnect Google Drive access
• Clear local browser data
• Uninstall the Chrome extension
• Request account deletion
• Request access to personal information
• Request correction or deletion of personal information
• Contact BugPort support for privacy requests

To make a privacy request, contact us at [email protected].

12. Security

BugPort uses reasonable technical and organizational measures to protect information, including:

• Secure transmission of sensitive data
• Authentication controls
• Access controls
• Workspace-based permissions
• Storage protections
• Operational monitoring
• Security review of sensitive workflows
• Limiting access to user data to authorized personnel and service providers

No system is completely secure. We cannot guarantee that information will never be accessed, disclosed, altered, or destroyed by unauthorized parties.

Users should avoid capturing passwords, secrets, private keys, payment details, or highly sensitive information in bug reports.

13. Data Transfers

BugPort and its service providers may process information in countries other than your country of residence. These countries may have data protection laws different from those in your jurisdiction.

Where required, BugPort uses appropriate safeguards for cross-border data transfers.

14. Children’s Privacy

BugPort is not intended for children under the age of 13, or the minimum age required by applicable law. We do not knowingly collect personal information from children.

If you believe a child has provided personal information to BugPort, contact us at [email protected].

15. Enterprise, Workspace, and Team Use

If you use BugPort through an organization, workspace, employer, or team account, your organization may control access to your reports and workspace data.

Workspace administrators may be able to:

• View reports submitted to the workspace
• Manage users and permissions
• Delete or export workspace data
• Configure integrations
• Access report metadata
• Review activity related to workspace usage

If you use BugPort through an organization, contact your workspace administrator for questions about internal data access and retention.

16. Public Reports and Shared Links

BugPort may allow users to share bug reports, recordings, screenshots, or links with other users. If you share a report or link, anyone with access may be able to view the content depending on the sharing settings.

You are responsible for ensuring that shared reports do not contain sensitive information that should not be disclosed.

17. Sensitive Information in Captures

Because BugPort captures user-selected screens, pages, logs, and network metadata, bug reports may accidentally include sensitive information.

Before submitting or sharing a report, users should review captured content and avoid including:

• Passwords
• API keys
• Secret tokens
• Private customer data
• Payment details
• Health information
• Government ID numbers
• Confidential business information
• Private messages
• Sensitive personal data

Where possible, BugPort may redact or avoid collecting sensitive values such as authorization headers, cookies, passwords, and token-like data. However, we cannot guarantee that all sensitive information will be detected or removed automatically.

18. Cookies and Similar Technologies

BugPort’s website and web application may use cookies, local storage, and similar technologies to:

• Keep users signed in
• Remember preferences
• Maintain session state
• Improve security
• Support workspace selection
• Understand product usage
• Diagnose errors and performance issues

You can control cookies through your browser settings, but disabling cookies or local storage may affect BugPort functionality.

19. Chrome Extension Local Data

The BugPort Chrome extension may store data locally using browser storage, IndexedDB, localForage, or similar browser storage mechanisms.

This local data may include:

• Extension settings
• Temporary recordings
• Upload queues
• Recovery files
• Authentication state
• Workspace/project selections
• Draft bug reports
• Capture metadata

Local data may remain on your device until it is uploaded, deleted, cleared by the browser, or removed when you uninstall the extension.

20. Google API and Google Drive Data

If BugPort uses Google APIs, BugPort’s use and transfer of information received from Google APIs will comply with applicable Google API Services User Data Policy requirements, including limited use requirements where applicable.

BugPort uses Google Drive permissions only for user-requested functionality, such as saving or exporting BugPort recordings or report assets to Google Drive.

BugPort does not sell Google user data.

BugPort does not use Google Drive data for advertising.

BugPort does not access unrelated Google Drive files except as necessary for user-requested BugPort functionality and permissions granted by the user.

21. Legal Bases for Processing

Where applicable, BugPort processes personal information based on one or more legal bases, including:

• Performance of a contract
• User consent
• Legitimate interests, such as providing and improving BugPort, security, support, and fraud prevention
• Compliance with legal obligations

If you are located in a jurisdiction that provides specific privacy rights, you may have additional rights described below.

22. Your Privacy Rights

Depending on your location, you may have rights to:

• Access personal information we hold about you
• Request correction of inaccurate information
• Request deletion of personal information
• Object to or restrict certain processing
• Request a copy of your information
• Withdraw consent where processing is based on consent
• Appeal certain privacy decisions
• Lodge a complaint with a data protection authority

To exercise your rights, contact us at [email protected].

We may need to verify your identity before fulfilling a request.

23. California Privacy Notice

If you are a California resident, you may have rights under the California Consumer Privacy Act, as amended by the California Privacy Rights Act.

BugPort does not sell personal information.

BugPort does not share personal information for cross-context behavioral advertising.

Categories of personal information BugPort may collect include:

• Identifiers, such as name, email address, account ID, and IP address
• Internet or electronic network activity, such as page URL, page title, network metadata, logs, and browser activity captured during user-initiated reports
• Geolocation information, such as approximate IP-derived location or timezone
• Audio, electronic, visual, or similar information, such as screen recordings and screenshots
• Professional or employment-related information, such as workspace or company name if provided
• Inferences or technical metadata generated from bug report context
• User-generated content, such as report descriptions, comments, and attachments

We use this information for the purposes described in this Privacy Policy.

California residents may contact us at [email protected]to exercise privacy rights.

24. European Economic Area, United Kingdom, and Switzerland

If you are located in the EEA, UK, or Switzerland, you may have additional rights under applicable data protection laws, including the right to access, correct, delete, restrict, or object to certain processing of personal data.

The controller of your personal data is:

Gurushi Global Solutions LLP
Email: [email protected]

If your organization uses BugPort under a separate agreement, your organization may be the controller of workspace content and BugPort may act as a processor.

25. Do Not Track

Some browsers send “Do Not Track” signals. Because there is no consistent industry standard for responding to these signals, BugPort does not currently respond to Do Not Track signals.

26. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. If we make material changes, we may notify users by updating the date at the top of this policy, posting a notice on our website, sending an email, or using another appropriate method.

Your continued use of BugPort after an update means you accept the updated Privacy Policy.

27. Contact Us

If you have questions, concerns, or privacy requests, contact us at:

BugPort Privacy Team
Gurushi Global Solutions LLP
Email: [email protected]
Website: https://bugport.ai

28. Chrome Web Store Disclosure Summary

For Chrome Web Store disclosure purposes, BugPort may collect the following categories of user data:

• Personally identifiable information, such as name and email address
• Authentication information, such as login/session tokens
• Location information, such as IP-derived country, region, city, or timezone
• Web history or web activity related to user-initiated bug reports, such as page URL, page title, and network metadata
• User activity, such as screen recordings, clicks, scrolling, and report creation activity captured during user-initiated reports
• Website content, such as screenshots, recordings, visible page content, console logs, network metadata, text, images, and attachments included in bug reports

BugPort uses this data only to provide and improve its bug reporting functionality, support users, secure the service, and comply with legal obligations.

BugPort does not sell user data.

BugPort does not use user data for unrelated purposes.

BugPort does not use user data to determine creditworthiness or for lending purposes.