GodSay GitHub Publication and Privacy Design

Goal

Publish the GodSay Chrome extension source to https://github.com/zomvs/godsay without exposing local credentials, and provide a public privacy policy suitable for use in the Chrome Web Store review form.

Repository Contents

The repository will use main as its default branch and include the extension source, manifest, icons, tests, development scripts, store assets, README, and project documentation. Generated archives, macOS metadata, and the credential-bearing src/local-config.js file will not be committed.

An empty src/local-config.example.js file will document the expected configuration shape. The README will explain how developers can copy or generate the ignored local configuration. Release archives will continue to contain an empty, release-safe src/local-config.js so the published extension can load before a user configures it through the extension UI.

Credential Safety

The ignore rules will cover:

  • src/local-config.js
  • .DS_Store
  • dist/
  • common local environment files such as .env and .env.*

Before the first full commit, staged files will be scanned for credential-bearing configuration and common API-key patterns. The ignored local configuration will remain on the developer machine and will not be modified by repository publication.

Privacy Policy

The repository root will contain a bilingual PRIVACY.md titled for GodSay / 神说. It will state:

  • which visible X post content and metadata the extension processes;
  • which API configuration, language preference, and optional advertising text it stores;
  • that settings are stored with Chrome synchronization storage;
  • that selected post data and prompts are sent only to the OpenAI-compatible service chosen by the user;
  • that the developer does not operate a collection server, sell data, or use data for advertising profiles;
  • that retention by an external AI provider is governed by that provider’s policy;
  • how users can delete stored data and revoke access;
  • the purpose of each Chrome permission;
  • compliance with the Chrome Web Store User Data Policy, including Limited Use requirements;
  • an effective date and a GitHub Issues contact link.

The Chrome Web Store privacy-policy URL will be https://github.com/zomvs/godsay/blob/main/PRIVACY.md after the public push.

Publication Flow

  1. Update ignore rules and add the safe configuration example.
  2. Add the bilingual privacy policy and update setup documentation.
  3. Run the existing tests and syntax checks.
  4. Inspect the exact staged file list and scan staged content for secrets.
  5. Commit the source on main, configure the GitHub remote, and push.
  6. Verify the remote branch and fetch the public privacy-policy URL.

Failure Handling

If GitHub authentication prevents the push, all local commits will remain intact and the exact authentication blocker will be reported without exposing credentials. If the repository is not public after the push, the privacy-policy URL will not be represented as review-ready until public access is verified.

Success Criteria

  • The remote main branch contains the maintainable source repository.
  • No local API key or generated local configuration is tracked.
  • PRIVACY.md is publicly accessible without authentication.
  • The test suite and JavaScript syntax checks pass.
  • The privacy-policy URL can be pasted into the Chrome Web Store review form.