Privacy
This page explains where screenshots, links, notes, and settings stay when you use AltG, and how the Chrome extension handles the web pages and account session you choose to use.
Single purpose
AltG has one purpose: save web content the user actively selects into a local workflow by capturing web screenshots, saving tab links, extracting page content, and writing the result to a user-authorized local folder or Obsidian vault.
Chrome Web Store Limited Use
AltG uses Chrome extension user data only to provide its single local-save purpose. Activity statistics are uploaded to altg.reka.cc for account connection and active status management. AltG does not sell user data, does not use the data for unrelated advertising, and does not upload screenshots, page body text, or local file contents.
Screenshots stay in your folders
When you choose an image root directory, Chrome grants the extension access to that folder so screenshots can be written there.
You choose the folder in the browser prompt.
You can change the active save target.
The product site does not receive the image files.
Content capture stays in your work directory
When you save pages to Obsidian or another local content directory, Markdown and optional screenshots are written to the path you authorize.
You choose the work directory or vault.
The save path is a folder inside that directory.
Files remain available in your local workflow.
Account checks and feedback stay narrow
Account connection is optional and used only to connect the extension with your AltG web account. Feedback is optional and uses only the email address and message you submit.
Connection, session verification, and activity statistics requests go to altg.reka.cc.
Screenshot files, notes, extracted page files, page body text, and local folder contents are not sent with account checks, activity statistics, or feedback.
Diagnostic logs and account IDs are not sent with feedback.
You keep control
AltG does not sell user data and does not create a hosted workspace for your screenshots or notes.
Clear extension data from Chrome settings when needed.
Re-authorize or change directories if a handle expires.
Disconnect the account to remove the local account session.
Data AltG Handles
Tab URL and title
AltG reads the current tab and current window tab URLs and titles for screenshot metadata, saved tab-link lists, batch screenshots, and content capture.
Page HTML and readable text
When you run content capture, AltG extracts the active page HTML and readable body content so it can create a Markdown note in the destination you choose.
Screenshots and PNG metadata
Screenshots, source URL, page title, capture mode, viewport, image size, and saved time are written to local files and PNG metadata.
Directory handles
File System Access directory handles are stored so Chrome can keep access to the image root directory and content capture work directory or Obsidian vault you authorize.
Extension preferences
Display language, delete confirmation, save paths, filename behavior, watermark settings, and update-check status are stored in browser-managed extension storage.
Account and feedback contact data
If you connect an AltG web account, the extension stores the account connection token and user profile needed to show account status and verify the session with altg.reka.cc. If you send feedback from the product site, AltG receives the email address and message you submit so the team can reply.
Activity statistics
Activity statistics are uploaded to altg.reka.cc for account connection and active status management. AltG does not upload screenshots, page body text, or local file contents with those statistics.
Screenshot diagnostic logs
Diagnostic capture logs may be stored locally in the extension database to troubleshoot screenshot failures. They are not uploaded by the extension.
Chrome extension update checks
Manual update checks use the Chrome extension update API and keep only the status needed to show whether a new version is available.
Chrome Extension Permissions
AltG requests only the permissions needed for the local screenshot, link, page-content, and Obsidian save workflow.
Read selected tab context
Used to read current or window tab URLs and titles, write screenshot metadata, save window links, switch tabs during batch capture, open extension pages, and batch open links.
Capture the user-triggered current tab
Used when you trigger current-page screenshots from the extension action, context menu, or Chrome command so Chrome allows capture for that current tab.
Run capture and clipping scripts
Used to inject clipping code, read viewport details, run long-screenshot scroll and restore logic, and show the screenshot completion toast.
Keep temporary batch-open state
Used with chrome.storage.session to remember the user-entered source URL and redirect state while batch-opened tabs navigate.
Process local files off page
Used to process Blob data, PNG metadata, watermarking, Markdown creation, and writes to authorized local directories in an offscreen document.
Capture full-page screenshots
Used only for Chrome DevTools Protocol Page.captureScreenshot when a page is larger than the visible viewport.
Show local status
Used for saved, error, setup-required, batch-complete, and retry notifications.
Track batch-open redirects
Used to keep PNG metadata tied to the user-entered source URL after a batch-opened tab redirects.
Export tab-link TXT files
Used when you save the current window tab links as a local TXT file.
Show extension action menu commands
Used to add grouped right-click menu commands on the extension icon for visible/full screenshots, Markdown saves, all-page link saves, batch opening, and the shortcuts list.
Work on user-selected web pages
Limited to http://*/* and https://*/* so shortcuts, screenshots, clipping, and batch window processing can run on web pages the user visits.
Enable screenshot-related window workflows when approved
Granted from the Settings page when you click the window batch screenshot permission button. Chrome then allows screenshot capture across every tab in the current window for Alt+P and Alt+Shift+P, and content capture screenshots for Alt+M or Alt+Shift+M when screenshot attachment is enabled. If it is not granted, AltG stops that workflow and opens Settings guidance; current-page screenshots and Markdown-only capture still work.
FAQ
Does AltG upload my screenshots?
No. Screenshot files are written to the local folder you authorize in Chrome.
Can this product site see my files?
No. The marketing site does not receive your screenshots, Obsidian notes, or local folder contents.
Where do saved links live?
Link lists and extension preferences use browser-managed storage unless you export or clip them into your own files.
What is sent for account verification?
Account session checks and activity statistics are sent to altg.reka.cc. Screenshots, notes, extracted page files, page body text, and local file contents are not sent with those requests.
How do I remove local data?
Disconnect the account in extension settings, clear extension data in Chrome, and re-authorize or remove directory access through Chrome when needed.
What is sent when I use feedback?
The product site sends the email address and message you enter. It does not attach screenshots, local files, diagnostic logs, or account identifiers.
If a future release adds network-backed file features beyond account checks, billing, and the feedback form, this page should be updated before that release ships.
Feedback