Privacy Policy

1. What KundiPost Is

KundiPost is a Chrome extension that helps a signed-in user prepare and save Facebook Group posts and Marketplace listings, publish selected content, and delete selected older active Marketplace listings. The extension uses a supporting KundiPost server for Google sign-in, account access limits, saved content, and image storage. KundiPost does not offer a public API to users or developers.

The KundiPost website provides product information and this Privacy Policy. Product actions, including sign-in, saving content, publishing, and Marketplace cleanup, take place through the Chrome extension.

KundiPost is an independent product. It is not affiliated with, endorsed by, sponsored by, or officially connected to Meta or Facebook.

2. Google Sign-In and Account Information

When you choose to sign in, the extension uses Chrome’s chrome.identity feature to request Google account access limited to OpenID, email, and basic profile information. Chrome returns a Google access token to the extension. The extension sends that token to the supporting KundiPost server, which asks Google to validate it and obtain the corresponding profile.

The following account information is stored by KundiPost:

• Google’s stable account identifier.
• Email address and email-verification status.
• Display name and profile image URL when Google provides them.
• The browser timezone supplied during the first sign-in.
• Your KundiPost access tier, such as Free or Pro, and any temporary Pro grant and expiration details.

Temporary Pro access lasts for the granted number of consecutive 24-hour periods, measured from the exact grant time. Lifetime Pro access has no scheduled expiration.

The Google access token is used to complete authentication and is not stored in the KundiPost database. After successful sign-in, KundiPost issues a separate application session token that expires after seven days. The raw application session token is stored in Chrome extension storage; the server stores only its SHA-256 hash, expiry time, creation time, and last-used time.

3. Content You Choose to Save

Saved content is sent to the supporting KundiPost server only when you choose to save or update it in the extension.

• Prepared Group post text and the images attached to each saved post.
• Saved Marketplace listing type, title, price, category, condition, description, location, and attached images.
• For saved vehicle listings: vehicle type, year, make, model, mileage, body style, title status, condition, fuel type, transmission, and exterior and interior colors when provided.

The server stores database identifiers, creation and update times, and ordered image references needed to return saved content to the correct Google account.

4. Images and Bunny.net

Images attached to saved posts and listings are transferred through the supporting KundiPost server and uploaded to Bunny Storage. KundiPost stores each image’s Bunny object path, delivered image URL, and display order in its database. Bunny.net stores and delivers those image files.

A delivered Bunny CDN image URL may be accessible to anyone who possesses the URL. Do not upload an image that you do not have permission to use or do not want hosted in this way.

5. Facebook Information Processed in the Browser

KundiPost operates through the Facebook account already signed in to the active Chrome profile. Depending on the feature you start, the extension processes:

• Joined Group identifiers, names, URLs, join state, last-visited information when available, and your Group selections.
• The post text and images you select for a Group publishing queue.
• For Group balance history, the selected Group identifiers and the latest known name of each Group that accepts a post.
• Facebook request URLs, headers, request bodies, form fields, and response data needed to load Groups and carry out the posting queue you started.
• Marketplace form fields and audience options shown by Facebook while publishing a listing.
• Active Marketplace listing identifiers, titles, creation times, pagination data, and deletion-request data needed for the cleanup you confirmed.
• Facebook cookie names and request-cookie availability used for local diagnostics. For a publishing workflow, the extension also reads the numeric c_user Facebook account identifier and sends that identifier to the KundiPost server for Free-tier binding and per-Facebook-account Group balance history. It does not send other Facebook cookie values.

This Facebook workflow information and captured request templates are processed inside the browser and sent to Facebook to perform the action you requested. The server converts the numeric Facebook account identifier into a keyed HMAC for Free-tier binding and Group balance history and does not store the raw identifier. KundiPost does not store Facebook passwords, other Facebook cookie values, or captured Facebook request templates in its server database.

When a Group post fails, KundiPost may temporarily display Facebook's response body in the current activity log so you can copy it for troubleshooting. The response remains in the current extension session, is not uploaded to the KundiPost server, and is copied only when you press the copy button.

When you choose Balanced posting, the extension sends the selected Group identifiers and latest names, accepted-post target, active Facebook account identifier, Groups that genuinely failed during the current queue, and starter-incompatible Groups remembered for the current browser session to the supporting KundiPost server. The server converts the Facebook identifier to a keyed HMAC, compares the selected Groups with stored lifetime counts, and returns an ordered posting plan. Merely including a Group in a plan does not create or increment its stored statistic; that happens only after Facebook accepts a post as published or pending approval.

Saved post and listing content is stored by KundiPost as described above. Content published to Facebook is also received and handled by Facebook under Facebook’s own terms and privacy practices.

6. Information Stored in Chrome

The extension stores the following information in Chrome extension storage:

• The seven-day KundiPost application session token, its expiry time, and a local copy of the signed-in profile information returned by KundiPost.
• A signed-out preference so the extension does not silently sign in again.
• Loaded Group information, selected Group identifiers, Group search text, and display preferences.
• During the current browser session, a SHA-256 key representing the active Facebook account and Group identifiers that could not initialize the first visible composer, so the current or a later Balanced or selected-order queue can automatically choose another starter Group.
• Group and Marketplace queue intervals, successful-post targets, shuffle settings, and other current side-panel workflow settings.
• The Gemini API key, rewrite toggles, hashtag preferences, and custom rewrite instructions when you choose to save them.

Clearing extension data or uninstalling KundiPost removes this locally stored information. It does not delete the KundiPost account, server-stored drafts and listings, Bunny-hosted images, or content already published on Facebook.

7. Optional Gemini Rewriting

Gemini rewriting is off by default. If you enable it and provide your own Gemini API key, the extension sends the original Group post body or Marketplace description, your custom instructions, destination type, and hashtag preference directly to Google’s Gemini service. The Gemini API key is stored in Chrome extension storage and is not sent to or stored by the KundiPost server.

Google handles Gemini requests under Google’s applicable terms and privacy policies. If rewriting is disabled, unavailable, or unsuccessful, KundiPost uses the original content.

8. Access-Tier, Daily-Usage, and Group-Balance Records

KundiPost stores your access tier and counts saved Group posts and Marketplace listings to enforce Free-account storage limits. Immediately before a Facebook publishing action, the extension requests a usage reservation from the supporting server. For Free accounts, the first publishing claim creates a one-to-one binding between the signed-in Google account and the Facebook account active in Chrome. The same Free Google account cannot switch to another Facebook account, and the same Facebook account cannot obtain another Free allowance through a different Google account. The server stores:

• A keyed HMAC of the numeric Facebook account identifier, not the raw identifier.
• Whether the operation is a Group post or Marketplace listing.
• A randomly generated operation identifier.
• Whether the operation was claimed, succeeded, or released after a known failure.
• Claim, success, release, and daily-expiry times as applicable.
• For accepted Group posts, the Group identifier, latest known Group name, lifetime accepted-post count, last accepted time, and an operation identifier used to prevent a retried request from incrementing the count twice.

These records enforce the current calendar-day allowance against both the Google account and the bound Facebook account inside a database transaction. Saved drafts do not count as publications. Facebook-accepted Group submissions, including posts awaiting administrator approval, successful Marketplace publications, and active reservations count toward the displayed daily usage; a confirmed failed attempt is released.

Published Group posts and posts awaiting administrator approval increment the lifetime Group-balance count. Confirmed failures do not. This count does not impose a posting limit and does not reset; it is used only when you choose Balanced posting to prioritize selected Groups with fewer accepted posts. You can instead choose the normal selected-order workflow.

9. Server Logs

The supporting KundiPost server creates operational request and error logs. These logs may include the request time, method, path, response status, processing duration, network address, and sanitized error details. They are used to operate the service and investigate failures. Google access tokens and application bearer tokens are not intentionally written to application logs.

10. When Information Is Shared

KundiPost transfers information only as needed for the current product flow:

• Google: to authenticate the selected Google account and, separately, to process Gemini rewriting only when you enable that optional feature.
• Facebook: to load available Groups and Marketplace information and to perform publishing or cleanup actions that you start.
• Bunny.net: to store and deliver images attached to saved content.
• Hosting, database, and network providers: to run and secure the supporting KundiPost server and website.

KundiPost does not sell personal information and does not use extension data for personalized, retargeted, or interest-based advertising.

11. Retention, Sign-Out, and Deletion

• Saved Group posts, Marketplace listings, and associated image references remain until you delete the saved item or request deletion of your account data.
• Deleting a saved post or listing removes its database records and requests deletion of its Bunny Storage directory. It does not delete copies already published on Facebook.
• Marketplace cleanup permanently deletes the active Facebook listings included in the confirmed cleanup. KundiPost cannot restore those Facebook listings.
• Signing out invalidates the current KundiPost application session and removes the local session and cached Google access token. Signing out does not delete your account or saved content.
• Application sessions are created with a seven-day expiry. Expired session records may remain until routine server cleanup removes them.
• Account, hashed Facebook-account binding, Group-balance history, access-tier, usage, and operational records remain while needed to provide the account, enforce limits, address security or abuse, resolve disputes, or meet legal requirements.

KundiPost currently provides deletion controls for individual saved posts and listings. For deletion of the complete KundiPost account and its server-stored data, email haronkibetrutoh@gmail.com from the Google account used with KundiPost. We may verify account ownership before completing the request.

12. Your Controls

• Review and edit content before saving or publishing it.
• Choose the posts, listings, Groups, audiences, and actions in each workflow.
• Pause, resume, or stop an active publishing queue.
• Keep Gemini rewriting disabled or remove the locally stored Gemini API key.
• Delete individual saved posts and Marketplace listings from the extension.
• Clear extension storage or uninstall KundiPost to remove local extension data.
• Contact us to request deletion of the complete KundiPost account and stored data.

13. Chrome Web Store and Google Limited Use

Information obtained through Chrome extension permissions is used only to provide and improve KundiPost’s disclosed user-facing features. It is not used for personalized advertising, creditworthiness, lending, or unrelated profiling.

KundiPost’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. KundiPost also follows the Chrome Web Store User Data Policy for data handled by the extension.

14. Security

KundiPost uses reasonable safeguards for stored information. Production communication with the supporting server uses HTTPS, application session tokens are stored as SHA-256 hashes in the database, and Bunny Storage credentials are kept on the server rather than embedded in the extension. No transmission or storage method can guarantee absolute security.

15. Children’s Privacy

KundiPost is intended for business and selling workflows and is not directed to children. We do not knowingly collect personal information from children.

16. Changes to This Policy

This policy may be updated when KundiPost’s implemented features, data handling, service providers, or legal obligations change. The revised policy will display a new “Last updated” date.

17. Contact

For privacy questions or account-data requests, email haronkibetrutoh@gmail.com.