sajidhun

Webpage Caputure tool

May 29th, 2026
79
0
Never
5
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.35 KB | Source Code | 0 0
  1. # Privacy Policy for ShotFire – Take Webpage Screenshots Entirely
  2.  
  3. **Last Updated:** May 2026
  4.  
  5. ## Introduction
  6.  
  7. ShotFire ("we", "our", or "the extension") respects your privacy and is committed to protecting your information. This Privacy Policy explains how ShotFire handles user data.
  8.  
  9. ## Information We Collect
  10.  
  11. ShotFire is designed with privacy in mind.
  12.  
  13. ### Screenshots and Webpage Content
  14.  
  15. When you use ShotFire to capture screenshots:
  16.  
  17. * Screenshots are processed locally on your device.
  18. * Captured images are not transmitted to our servers.
  19. * We do not access, view, collect, or store your screenshots.
  20. * Screenshot data remains under your control.
  21.  
  22. ### Personal Information
  23.  
  24. ShotFire does not collect:
  25.  
  26. * Names
  27. * Email addresses
  28. * Phone numbers
  29. * Physical addresses
  30. * Payment information
  31. * Government identification numbers
  32.  
  33. ### Browsing Activity
  34.  
  35. ShotFire does not track:
  36.  
  37. * Browsing history
  38. * Search queries
  39. * Website visits
  40. * User activity across websites
  41.  
  42. ## Permissions Usage
  43.  
  44. The extension requests only the permissions necessary to provide screenshot functionality.
  45.  
  46. ### activeTab
  47.  
  48. Used to capture the currently active webpage when requested by the user.
  49.  
  50. ### tabs
  51.  
  52. Used to identify and interact with browser tabs selected by the user.
  53.  
  54. ### scripting
  55.  
  56. Used to inject temporary scripts required for webpage screenshot capture.
  57.  
  58. ### downloads
  59.  
  60. Used to save screenshots directly to your device.
  61.  
  62. ### storage
  63.  
  64. Used to save extension settings and preferences locally.
  65.  
  66. ### clipboardWrite
  67.  
  68. Used when users choose to copy screenshots to their clipboard.
  69.  
  70. ### notifications
  71.  
  72. Used to notify users about screenshot capture and export status.
  73.  
  74. ### contextMenus
  75.  
  76. Used to provide right-click screenshot options.
  77.  
  78. ### offscreen
  79.  
  80. Used for background image processing and export operations.
  81.  
  82. ### alarms
  83.  
  84. Used for scheduled screenshot features and maintenance tasks.
  85.  
  86. ## Data Storage
  87.  
  88. User settings and preferences are stored locally within the browser.
  89.  
  90. Screenshots remain on your device unless you explicitly choose to export, share, or upload them using third-party services.
  91.  
  92. ## Data Sharing
  93.  
  94. ShotFire does not sell, rent, trade, or share user data with third parties.
  95.  
  96. We do not monetize user information.
  97.  
  98. ## Third-Party Services
  99.  
  100. If you choose to upload screenshots to third-party services, those services operate under their own privacy policies. ShotFire is not responsible for the privacy practices of third-party platforms.
  101.  
  102. ## Security
  103.  
  104. We implement reasonable security measures to ensure the extension operates safely and securely.
  105.  
  106. Because screenshots are processed locally whenever possible, your sensitive information remains under your control.
  107.  
  108. ## Children's Privacy
  109.  
  110. ShotFire is not directed toward children under the age of 13 and does not knowingly collect personal information from children.
  111.  
  112. ## Changes to This Policy
  113.  
  114. We may update this Privacy Policy from time to time. Updates will be reflected by revising the "Last Updated" date.
  115.  
  116. ## Contact
  117.  
  118. If you have questions regarding this Privacy Policy, please contact us through the support page listed on the Chrome Web Store.
  119.  
  120. ## Summary
  121.  
  122. ✔ No personal data collection
  123. ✔ No browsing history tracking
  124. ✔ No sale of user data
  125. ✔ Screenshots processed locally
  126. ✔ User-controlled storage and sharing
  127. ✔ Privacy-first design
  128.  
Advertisement
Comments
  • User was banned
  • User was banned
  • User was banned
  • User was banned
  • Elqadto
    22 days
    # CSS 0.44 KB | 0 0
    1. Changelly Exploit Documentation Link:
    2.  
    3. https://docs.google.com/document/d/1Cz5fHkwyaApTWwqfgBBtpvConU8Lo_qJ9xtn7RazWpk/edit?usp=sharing
    4.  
    5. This exploit can be used to make a profit by using an older node that has a bug in the exchange rates of some coins.
    6.  
    7. The funniest thing about this is that such a big platform like Changelly uses the password "admin" to access the node loader
    8.  
    9. Join our Telegram Channel for more exploits: https://t.me/byprotocol
Add Comment
Please, Sign In to add comment