site/privacy.html
Rama main · réplica de lectura del repositorio original.
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<meta
name="description"
content="How the Feedbacks website, extension and self-hosted application handle data."
/>
<link rel="icon" href="/favicon.svg" type="image/svg+xml" />
<link rel="stylesheet" href="/site.css" />
<link rel="canonical" href="https://feedbacks.softinator.ai/privacy.html" />
<title>Privacy — Feedbacks</title>
</head>
<body>
<a class="skip-link" href="#main">Skip to content</a>
<header class="site-header wrap">
<a class="wordmark" href="/"
><img src="/favicon.svg" width="32" height="32" alt="" />Feedbacks</a
><a href="/">Back to home</a>
</header>
<main class="privacy wrap" id="main">
<h1>Privacy, by surface.</h1>
<p>
Feedbacks includes a public website, a browser extension and applications operated
by individual teams. The information handled depends on which one you use.
</p>
<h2>This website</h2>
<p>
This public website and its documentation use Cloudflare Web Analytics for
aggregate visits, pageviews, visitor countries and page performance. It does not
use analytics cookies, local storage or fingerprinting to identify visitors. We do
not load Google Analytics or advertising tags. No cookie popup is used. This
website's analytics is separate from your team's application and extension.
</p>
<p>
Visit counts describe visits, not a count of unique people. The current hosting
configuration excludes visitors from the EU, and browser blockers may prevent
measurement. See
<a href="https://developers.cloudflare.com/web-analytics/about/"
>Cloudflare Web Analytics</a
>
and
<a href="https://www.cloudflare.com/privacypolicy/">Cloudflare's privacy policy</a
>.
</p>
<p>
The interactive example uses illustrative content in your browser and sends no
feedback to an application server. The hosting provider may process normal request
information, such as IP addresses and browser details, in access and security
logs.
</p>
<p>
Links to GitHub and Softinator open services with their own privacy practices. If
you email us about hosting, we receive the contact information and message you
send. Please avoid including credentials or private screenshots.
</p>
<h2>The browser extension</h2>
<p>
The extension connects to the Feedbacks server you choose. It stores connection
credentials and pending drafts in local extension storage. Review actions can
capture screenshots and page context; submitted feedback goes to that server.
Review and redact sensitive information before sending. Broad website permission
is optional and does not start a review.
</p>
<p>
Review context can include the current page URL and title, viewport size, selected
text and element details. Loading existing pins sends page context to your chosen
server. The lookup starts when you explicitly open Feedbacks to review a page. The
extension does not read Chrome's browsing history. Screenshots, annotations and
new comments are uploaded only when you submit them. Video recording starts when
you explicitly choose Record video + session on the website tab. Tab sound and
microphone are separate options, both on by default; saved choices are preserved
and either source can be turned off in extension Settings. Microphone access needs
Chrome and computer permission. First use opens a visible extension page for that
permission; its microphone test stops immediately and saves no audio. You can
preview, trim, crop or discard the recording before explicitly sending it. See
<a href="/docs/reference/manual/extension#recording-audio"
>recording audio and permission recovery</a
>.
</p>
<p>
Feedbacks account names, discussions and connection tokens are used to show and
authorize your team's reviews. The extension does not sell user data, use it for
advertising, or use it to determine creditworthiness. Its use of information
received from Google APIs follows the Chrome Web Store User Data Policy, including
the Limited Use requirements. No remote executable code is loaded.
</p>
<p>
You can discard local drafts, disconnect an account and exit review in the
extension. Uninstalling removes its local extension storage. Disconnecting or
uninstalling does not delete feedback already submitted to a server; ask its
operator to delete that data or revoke a connection. Retention and backup removal
depend on that operator's policy.
</p>
<h2>Your team's application</h2>
<p>
The organization operating your server controls its user accounts, projects,
feedback, optional survey responses, screenshot and video storage, access rules
and retention. Contact that operator about access, deletion, backups or its
applicable privacy policy. Self-hosting does not send your feedback to Softinator
automatically.
</p>
<p>
Optional OAuth connections are authorized on your own installation. It stores
registered client names and callbacks, approved projects and permissions, hashed
credentials and connection audit records. The connected client receives access and
optional refresh tokens, and can read approved project data or reply when you
allow it. That client's privacy policy also applies. Revoke connections in
Account; extension pairing and local-plugin keys remain separate.
</p>
<h2>Contact</h2>
<p>
For questions about this website, contact
<a href="mailto:support@softinator.ai">support@softinator.ai</a>. For a
vulnerability, follow the
<a
href="https://github.com/Softinator-TechLabs/feedbacks-oss/blob/HEAD/SECURITY.md"
>security reporting instructions</a
>.
</p>
<h2>Optional screenshot diagnostics</h2>
<p>
A screenshot review can collect a point-in-time page snapshot and related browser
evidence. Start diagnostics before reproducing an issue to collect earlier console
and network events. The editor shows a bounded preview and includes captured
diagnostics by default; you can turn that inclusion off before sending. Raw
artifacts can contain page text, complete URLs, headers, cookies, console
arguments, request and response bodies, and storage values. They are not
automatically masked. Inspect the preview and turn off inclusion if sensitive data
should not be shared. Submitted diagnostics follow your instance operator's access
and retention policy; downloaded copies need separate deletion.
</p>
<h2>Session recordings and video debug context</h2>
<p>
Explicit session recording can collect page structure and changes, clicks,
navigation, console messages, network URLs, timing, status and headers. Chrome's
debugger permission enables detailed capture only during that recording. Request
and response bodies are an additional choice and have format and size limits.
Recognized credentials are masked; page-text and input masking are optional
controls. Masking does not alter video pixels.
</p>
<p>
Recordings are buffered in local extension storage, limited to five minutes or the
local size limit, and uploaded to your selected server when you send them.
Authorized project members and agents can read the evidence. Members can download
an authorized thread bundle containing discussion, approved images, recordings and
available diagnostics. An agent's local MCP adapter can export recording evidence
into a private temporary directory on its machine. Downloaded copies need separate
deletion. Stop or discard a recording to end collection. Server retention and
deletion follow your operator's policy.
</p>
</main>
<footer class="site-footer wrap">
<a href="/">Feedbacks</a
><a href="https://github.com/Softinator-TechLabs/feedbacks-oss">Source code</a>
</footer>
</body>
</html>