Introduction
Cred Issue Reporter ("the Extension", "we", "our") is a Chrome extension designed to help developers and QA teams capture, annotate, and report bugs directly to their Redmine project management system. We are committed to protecting your privacy and being transparent about our data practices.
✅ No Third-Party Data Collection
We don't collect, store, or transmit any data to our servers
✅ User Control
You decide what data is included in bug reports
✅ Transparency
Pre-submission review shows exactly what will be sent
✅ Direct Communication
Data goes only to YOUR Redmine server
1. Data Collection and Usage
1.1 What Data We Collect
The Extension collects the following types of data ONLY when you actively create a bug report:
A. Screenshot Data
- What: Visual capture of the current browser tab
- When: Only when you click "Capture Screenshot"
- Storage: Temporarily in browser memory, then sent to your Redmine server
- Retention: Cleared after report submission or 1 hour of inactivity
B. Page Information
- Current webpage URL
- Page title
- Browser name and version
- Operating system information
- Screen resolution and viewport size
- Timestamp of capture
C. Network Activity (Optional - Can be disabled)
- HTTP/HTTPS request URLs
- Request methods (GET, POST, etc.)
- Response status codes
- Request/response headers
- Failed request information
Note: Network monitoring captures traffic from the webpage you're reporting on.
D. Console Logs (Optional - Can be disabled)
- JavaScript console output (log, warn, error, info)
- Error messages and stack traces
- Timestamps of log entries
Note: Console logs may inadvertently contain sensitive information from the webpage.
E. Browser Storage (Optional - Disabled by default)
- LocalStorage contents
- SessionStorage contents
- Cookies
F. Redmine Credentials
- Redmine server URL
- Redmine API key
- Default project preferences
- Storage: Encrypted in Chrome's secure storage (chrome.storage.sync)
1.2 How We Use This Data
Direct Use Only: All collected data is used exclusively for creating bug reports in YOUR Redmine server.
Specifically:
- Screenshot + Annotations → Attached to Redmine issue as image file
- Page Information → Included in issue description for context
- Network Requests → Exported as HAR file, attached to issue
- Console Logs → Exported as text file, attached to issue
- Browser Storage → Included in technical data JSON file (if enabled)
- Redmine Credentials → Used to authenticate API requests to your server
We DO NOT:
- ❌ Send any data to our servers or third parties
- ❌ Use data for analytics, tracking, or advertising
- ❌ Share data with anyone except your designated Redmine server
- ❌ Store data permanently (temporary memory only, cleared within 1 hour)
2. Data Storage and Retention
2.1 Local Storage
| Type | Location | Retention |
|---|---|---|
| Settings Data | Chrome's encrypted sync storage | Until you uninstall or clear manually |
| Temporary Data | Browser memory (RAM) | Maximum 1 hour |
| Session Storage | Chrome's session storage | Until browser closes or submission |
2.2 No Server-Side Storage
Important: We do NOT operate any servers or databases. All data handling occurs:
- Locally in your browser
- In transit to your Redmine server (encrypted via HTTPS)
- On your Redmine server (per your organization's policies)
3. Data Sharing and Transmission
3.1 Data Recipients
Only One Recipient: Your Redmine Server
- Data is transmitted ONLY to the Redmine server URL you configure
- Transmission uses secure HTTPS protocol
- Authentication via your personal API key
- No intermediate servers or proxies
3.2 Third-Party Services
We Do NOT use:
- ❌ Analytics services (Google Analytics, etc.)
- ❌ Crash reporting services
- ❌ Advertising networks
- ❌ Social media integration
- ❌ Any external APIs except your Redmine server
4. User Control and Transparency
4.1 Privacy Settings
You have complete control over data collection:
| Setting | Default | Description |
|---|---|---|
| Include Network Requests | ON | Capture HTTP/HTTPS traffic |
| Include Console Logs | ON | Capture JavaScript console output |
| Include LocalStorage Data | OFF | Capture browser storage |
| Include Cookies | OFF | Capture cookie data |
| Sanitize Sensitive Data | ON | Remove problematic characters |
4.2 Pre-Submission Review
Transparency Guarantee: Before ANY data is sent to Redmine, you will see a review modal with tabs showing all data. You must explicitly click "Confirm & Submit" to proceed.
5. Permissions Explained
| Permission | Purpose |
|---|---|
| activeTab | Access current tab to capture screenshots and page info |
| storage | Store Redmine credentials and preferences securely |
| tabs | Capture screenshots and create annotation tabs |
| webRequest | Monitor network requests for debugging context |
| scripting | Collect page information and console logs |
| tabCapture | Enable video recording of tab content |
| offscreen | Required for video recording functionality |
| <all_urls> | Monitor network requests on any page where you report bugs |
6. Your Rights (GDPR/CCPA Compliance)
| Right | How to Exercise |
|---|---|
| Right to Access | View all data via pre-submission review modal |
| Right to Deletion | Uninstall extension to delete all locally stored data |
| Right to Data Portability | Export technical data as JSON files before submission |
| Right to Object | Disable specific data collection features in settings |
| Right to Rectification | Edit all data in review modal before submission |
Note: Since we don't store data on our servers, these rights are inherently built into the Extension's design. You have complete control over your data at all times.
7. Compliance Summary
| Regulation | Status | Notes |
|---|---|---|
| GDPR | ✅ Compliant | User control, transparency, data minimization |
| CCPA | ✅ Compliant | No data sales, opt-out controls available |
| Chrome Web Store Policies | ✅ Compliant | Transparent disclosure, justified permissions |
8. Contact Information
Extension Developer:
- GitHub Repository: https://github.com/prabhuvikas/Cap-screen
- Issue Tracker: https://github.com/prabhuvikas/Cap-screen/issues
For Privacy Concerns:
- Open an issue on GitHub with label
privacy - We aim to respond within 7 business days
9. Changes to Privacy Policy
We may update this Privacy Policy to reflect changes in extension functionality, legal requirements, or user feedback.
How we notify you:
- Update "Last Updated" date at the top
- Post notice in extension update notes
- Maintain version history on GitHub
Continued use of the Extension after changes constitutes acceptance of the updated policy.
10. Acknowledgment
By installing and using Cred Issue Reporter, you acknowledge that you have read and understood this Privacy Policy and agree to its terms.
If you do not agree with this policy, please do not install or use the Extension.