When you reach out
We use what you share to understand your needs and get back to you.
Privacy / 01
Privacy, without the maze.
Share only what you’re comfortable with. We’ll keep it to the conversation you started.
Ask HunpeoLabs
Ask with only the context you need.
The assistant uses published HunpeoLabs information. Your conversation is held in this page’s memory, with up to twelve displayed exchanges and six previous questions used for context. It is cleared when you leave or reload; it is not saved to browser storage or a chat database. Questions and conversation text are not sent to traffic analytics or written to application logs.
When the optional Gemini integration is enabled, questions that need additional matching, recent questions and relevant public source information may be processed by Google Cloud Vertex AI. Firebase App Check with reCAPTCHA Enterprise helps protect that path. The input notice tells you when Google processing is available. Avoid sharing secrets or sensitive personal information. Google processing and retention follow the configured provider service terms; this page does not promise zero provider retention.
Rate limits use a random in-memory session identifier. Published-content counters are held temporarily in server memory. When AI is enabled, the server stores keyed hashes of rate-limit buckets and counts in Firestore, without question text, account identity or raw network addresses. Expiry fields support the configured cleanup policy. Opening Contact does not send your conversation or submit a project brief; you review and submit the contact form separately.
How we handle what you share
Nothing more
We don’t sell your information or use it to target ads.
Still curious?
Talk to us at support@hunpeolabs.com.
Optional measurement
Traffic analytics stays your choice.
If traffic analytics is enabled and you choose Allow, Google Analytics for Firebase helps us understand aggregate visits, pages viewed, traffic sources, approximate location, and browser or device information. It may use Analytics cookies and a Firebase installation identifier.
We do not send project brief fields, use User-ID, or enable advertising personalization. You can change your choice at any time through Analytics preferences in the footer. We review the linked property’s retention setting before production measurement is activated.
Chrome extension
Satsunic SEO extension
Website checks run when you request them. Optional account and Pro tools use connected services for the tasks you choose.
Website checks and saved work
Satsunic reads the supported page you select and requests public pages, robots.txt and sitemaps when you start a crawl. The website receives these requests and normal network information, including your IP address. Crawl requests do not include the website’s cookies or authorization headers.
Reports and saved work can contain URLs, page text, links and inspection findings. Saved work stays in the extension’s browser storage. Exports create files you control; Satsunic does not automatically send them to an AI service. Removing a saved item does not remove files you downloaded.
Optional sign-in and connected checks
Google and Firebase handle account sign-in. The extension keeps your Firebase session in its browser storage so it can restore sign-in and share the session across Satsunic views. Signing out removes the stored sign-in session; it does not delete cloud records.
When you request a connected check, the backend receives the account and workspace identifiers and the inputs needed for that task. Depending on the feature, this can include a search query, domain, business or public location, keywords and region. Supported provider checks use DataForSEO. Connecting a Google Business Profile uses Google’s permission flow; availability depends on the connected service.
Server records include workspace membership, entitlements, quotes, jobs, results, credit reservations and settlements. Opening a panel or exporting a loaded result does not start a paid provider check; you review a quote before starting one.
Payments and subscriptions
Lemon Squeezy hosts checkout and subscription management. You enter card details on its payment service, not in the extension. Satsunic receives the billing events needed to manage subscription access and credits. Billing events and credit settlements are separate from website inspection results.
Deletion and retention
Use the extension’s saved-work controls to remove local items. Signing out hides account-scoped saved work but does not erase it. On a shared device, remove saved work before signing out.
Connected results have source-specific expiry rules. Expiry limits access to those results; financial and audit records have separate retention requirements. Clearing browser data does not erase records held by Firebase, DataForSEO, Google or Lemon Squeezy.
With analytics permission, HunpeoLabs records aggregated public-page visits and engaged article reads. Anonymous session identifiers expire after 30 minutes of inactivity; hashed deduplication receipts expire after 24 hours. Counts exclude identified staff and bots and are approximate. We do not store raw IP addresses, email, or full query strings in traffic records.
For privacy questions or deletion requests, email support@hunpeolabs.com.
Blog accounts and discussion
Your public words, your private account.
Firebase Authentication processes your email and sign-in details. A necessary session cookie keeps you signed in for up to one day. Your display name and approved comments are public; your email, account identifiers and reports are not included in public comment responses.
Comments and edits pass automatic spam checks. Ordinary comments can appear immediately; suspicious content is held for moderator review. Deleting a comment removes its public text and name; a placeholder may remain to preserve replies. Server-only anti-spam records contain account-linked moderation counters and up to 20 recent comment fingerprints and submission times. Fingerprints older than 24 hours are ignored and pruned on the next submission or edit; inactive records remain until the account erasure process removes them. Moderation records and backups follow our operational retention process. Contact us for account or data deletion requests.
Rate limits use per-account and shared site budgets to reduce spam; verified network identifiers may be hashed when trusted ingress is configured. Sharing buttons open the service you choose only when clicked; that service handles what you choose to publish. Article view counts use a random, tab-scoped session identifier to avoid counting reloads twice. The server stores only a keyed hash with a 24-hour expiry and an aggregate count; raw network addresses and account identities are not stored in view statistics. Separately opened tabs may count as separate views. Share totals count sharing actions from this website, including copied links; they do not verify publication on social networks. Random action identifiers are stored only as keyed hashes with a 24-hour expiry to avoid duplicate requests. We do not send comment text or account identity to traffic analytics.
For Studio editors, unsaved drafts may be kept in local storage on this device, separately for each account and article. A successful save clears the local copy. Recovery copies older than seven days are ignored and cleared when that article is opened again. They are not shared across devices.