Last updated: October 19, 2026
Scope
This policy describes BlindSense Automation’s private IGCE Agent Lab and this informational website. The application processes owner-authorized training materials to prepare instructor-guide drafts. The public website does not provide access to private documents or processing systems.
Google account data and permissions
The application uses the authorized account’s email address to check identity. It accesses document content and file metadata, such as names, identifiers, folder locations, and modification details, for source matching, conversion, validation, and output creation. Google Docs, Sheets, Drive, and Apps Script permissions support document processing, workflow records, execution, and owner-authorized maintenance.
The configured Google permissions include broad access to Drive files, Docs, and Sheets, and permissions to view or manage Apps Script projects, deployments, processes, and metrics, connect to external services, and run when the owner is absent. These permissions can cover more than the intended IGCE folders; Google does not enforce a folder-only boundary for the broad Drive permission. The lab’s authorized operating scope is the owner’s personal IGCE replica. Employer accounts and work Drive resources are excluded.
Use and AI processing
Document text and relevant source context are sent to Google’s Gemini API with processing instructions to generate and validate draft instructor material. This means document content leaves its original document for AI processing by Google.
The autonomous controller also uses the OpenAI API for workflow decisions, maintenance, troubleshooting, and continuation summaries. Operational instructions, checkpoints, tool results, and error evidence are sent to OpenAI. These may include Google file metadata and document excerpts when present in tool results or diagnostic evidence. The application does not represent that Google-derived information stays exclusively within Google services.
Google and OpenAI process API inputs and outputs under their applicable service terms and data-handling policies. These can include abuse monitoring, retention, and authorized human review. This application does not promise zero retention by either provider. AI-generated material and operational decisions require appropriate review and validation.
Storage and retention
Source documents, generated guides, intermediate AI artifacts, workflow records, validation evidence, and operational metadata may be retained in the owner’s private Google environment. Cloud Storage also retains controller checkpoints, events, transcripts, and workspace recovery snapshots. Runtime configuration contains credentials needed for authorized access. Operational services may retain execution and error records, and AI providers may retain API data under their applicable settings and policies.
There is no application-wide automatic deletion period promised by this policy. Records remain until removed by the owner or expired under the relevant service’s settings and policies; recovery copies and provider logs may remain for their applicable retention periods.
Disclosure and protection
Google services provide document storage, execution infrastructure, authentication, and Gemini processing. OpenAI provides the controller’s AI processing described above. Data is used for the authorized workflow, validation, maintenance, and troubleshooting. BlindSense Automation does not sell Google user data or use it for advertising. Access is restricted to authorized identities, and external service requests use HTTPS. Credentials and private documents are not published on this website. No system can guarantee absolute security.
Google API Limited Use
BlindSense Automation’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. BlindSense Automation does not use Google user data to train generalized AI models.
Your choices and deletion
The account owner can revoke the application’s access in Google Account settings and stop scheduled processing. Revocation does not delete previously created files, intermediate artifacts, transcripts, backups, or logs. Authorized users can request access, correction, or deletion through the application owner using the user support email shown on the Google authorization screen. Deletion must cover the relevant stored artifacts and remains subject to applicable provider retention and legal requirements.
Website visitors
This Google Sites website does not ask visitors to connect a Google account to IGCE or upload documents. Google may process normal hosting and security information under its own privacy policy.
Changes
Material changes to this policy will be reflected in the date above. Review this policy before authorizing new processing.