Policy identifier: GT-AI-RETENTION-2026-10-07-v1.1-azure-copy Matching notice identifier: GT-WEB-CONSENT-2026-10-07-v1.1-azure-copy-compact
Godd Technologies, LLC (the Company) may preserve the final conversation record, transcript and covered, consented voice recordings from its three designated website AI assistants in private Microsoft Azure storage. These copies support the inquiry, follow-up and disclosed recordkeeping purposes. This amendment applies prospectively to newly and affirmatively authorized corporate, government-portal and personal-site assistant conversations. Telephone conversations, historical conversations without the required prospective consent and unbound summaries are outside its scope. A later export, amendment or matching summary cannot supply earlier consent.
Before connecting, the visitor must affirmatively agree to the notice for the selected site, language and text or voice mode. The notice describes the interaction, provider processing and Company copy and links to the full policies. Text agreement does not authorize microphone access, voice recording or unexpected audio. Voice requires separate affirmative agreement to speech processing and recording before any microphone request or connection. A material notice or mode change requires new agreement.
The assistant is software, not Angel Godd-Santana or another person. Voice mode uses an AI-generated version of Angel Godd-Santana's voice. AI replies require appropriate human review. The assistant is for ordinary inquiries and cannot purchase a service, accept an Order, book work or a meeting, expand purchasing authority or create an engagement. Published Terms of Use and Service, controlling Government Orders and applicable written Accepted Orders remain controlling. The personal-site assistant uses the Company's CallDesk workflow; this does not convert every activity on Angel's professional site into a Company service. Existing professional contact links remain separate.
The workflow uses ElevenLabs for conversation orchestration, speech processing and conversation history; OpenAI Luna with Google Gemini fallback for language-model processing; Microsoft Azure for Company infrastructure and storage; Notion for the Company inbox; Azure Communication Services for email notifications; and ntfy for push notifications, as applicable. Conversation content and inquiry details support the interaction and follow-up. Inbox entries, notifications and downloads may create additional copies with separate handling. Additional analysis, speech, fallback or downstream processing must be verified and disclosed before use. No training-use or geographic-restriction promise is made without verified applicable terms.
Each Company copy must preserve the authenticated conversation, agent and site identity, the actual original provider start, the applicable consent and notice, signed source evidence and the covered artifacts. The Company must verify the final native provider conversation ID and terminal state, exact copied byte lengths and hashes, storage versions and independent readback. Missing, incomplete or contradictory transcript or audio evidence prevents a claim of complete preservation. Unknown attachments, incomplete recording channels and failed or truncated reads cannot be represented as a complete copy. Partial copies remain protected and count against capacity; they cannot justify removing provider originals.
Azure disposition eligibility is the verified actual original conversation start plus 90 elapsed days, each consisting of 24 hours, measured in UTC. Copying, downloading, retrying, importing, restoring, publishing a policy or changing an Owner decision never restarts that clock. Eligibility does not itself authorize deletion.
Only the exact authenticated Company Owner may establish or continue Keep for identified records, with a documented business or controlling recordkeeping reason and review date. A business relationship does not establish Keep automatically. An overdue review leaves Keep in force. Releasing Keep returns the record to its original clock; age-eligible Company disposition still requires separate approval.
Keep protects the verified Company Azure copy. It does not promise an ElevenLabs hold or customer restoration. Provider natural expiry, explicit provider-original removal and Company Azure removal are separate events. The current provider retention setting and deletion flags do not prove the provider's precise removal timing. No provider-native hold, restoration or erasure of every backup is promised.
Before Company-initiated removal of a provider original, the Company must independently verify the exact complete durable Azure copy and obtain a fresh confirmation identifying the record, current versions, archive digest and action. Separately confirmed provider-original removal may occur before Azure's 90-day eligibility or while Azure Keep remains in force, because the Company copy and its unchanged clock remain. Each explicit permanent deletion requires its own exact-record approval. Successful export, policy adoption, copy-job completion and day-90 eligibility are not deletion authority. An acknowledgement and later operational unavailability do not prove permanent erasure of provider backups, separate logs or downstream copies. Ambiguous outcomes require reconciliation and do not justify a blind retry.
Company copies are private and encrypted in transit and at rest. The scoped service identity accesses storage, and Company retrieval is limited to the exact authenticated Owner. Public blobs, permanent access URLs, browser storage credentials and storage SAS are prohibited. The copy role may add and read content, including listing authority at its exact container scope, but cannot overwrite or delete it. Retrieval must verify the durable seal and copied bytes before an authenticated private download; incomplete or unsealed copies are not presented as complete downloads.
Future Azure removal requires separately reviewed authority and exact-record confirmation. An age-of-blob lifecycle rule may not bypass original-start eligibility or Keep. Storage redundancy and readback do not promise immutable WORM storage or restoration after privileged deletion.
New copy intake and execution must follow a reviewed preservation schedule, current signed authority, bounded capacity and durable job state. Reservations include successful, pending, partial, ambiguous and Keep copies. Exhausted capacity, missing authority, uncertain source evidence or unresolved copy state blocks new dispatch. An automatic replacement attempt may not hide an earlier partial result. Serving-policy expiry or revocation stops new intake and copying. Existing verified Owner custody remains governed by its captured signed approval and unchanged retention and Keep decision. A separately confirmed and durably claimed provider-removal action has its own bounded authority; serving-policy revocation does not promise atomic cancellation across Azure and ElevenLabs.
Notion inbox records, email and push notifications, Owner downloads, operational logs, versions, soft-deleted objects and backups retain separate controls and limitations. Notion Trash is recoverable. This amendment does not promise permanent erasure of every copy on day 90.
Do not submit credentials, full payment-card details, classified information, CUI, nonpublic FCI, export-controlled data or other restricted or sensitive information through the assistant. An alternative contact method is support@goddtechnologies.com. Privacy requests use that address with the subject “Privacy Request.” Identity, authority, applicable exceptions and privacy-request handling follow the Company Privacy Policy; this amendment creates no additional waiver or request deadline.