Skip to main content

AI Usage Policy

Last updated: January 15, 2026

Artificial Intelligence Usage Policy

Document owner: VP of Product & Chief Information Security Officer (Joint) Version: 3.0 Effective date: January 1, 2026 Last updated: January 15, 2026 Classification: Public — Trust Center Review cadence: Quarterly, and upon material AI program changes Company: Acme Cloud, Inc. Address: 1200 Market Street, Suite 400, San Francisco, CA 94103, USA Primary contacts: trust@acmecloud.com | security@acmecloud.com | privacy@acmecloud.com


1. Executive Summary and Purpose

This Artificial Intelligence Usage Policy ("AI Policy" or "Policy") establishes Acme Cloud, Inc.'s ("Company," "we," "us," or "our") comprehensive framework for the responsible development, deployment, and operation of artificial intelligence and machine learning ("AI/ML") capabilities within our products and services. This Policy supplements and should be read in conjunction with our Privacy Policy, Data Processing Agreement, and Subprocessor List.

Policy Objectives:

This Policy addresses the following objectives critical to enterprise AI governance:

ObjectiveDescriptionStakeholder Benefit
TransparencyClear documentation of AI capabilities, data flows, and decision-making processesProcurement teams can assess AI risk; customers understand what they're enabling
Customer ControlGranular controls for enabling, disabling, and configuring AI featuresOrganizations maintain sovereignty over AI adoption decisions
Data ProtectionStrict limitations on data retention, usage, and sharing with AI model providersCustomer data never trains foundation models; privacy obligations satisfied
Human OversightClear delineation between AI assistance and human decision authorityUsers understand AI limitations; appropriate human review maintained
SecurityRobust protections against prompt injection, data leakage, and adversarial attacksSecurity teams can verify AI-specific controls
Regulatory AlignmentProactive compliance with emerging AI regulations (EU AI Act, state laws)Legal and compliance teams can map controls to requirements
AccountabilityDefined governance structure with clear ownership and escalation pathsExecutive accountability for AI program outcomes

Scope of This Policy:

This Policy applies to all AI/ML features offered within Acme Cloud products and services, including but not limited to: natural language processing features, automated content generation, semantic search capabilities, recommendation systems, workflow automation suggestions, and any features utilizing third-party AI models. This Policy does not govern customer use of Acme Cloud APIs to build their own AI applications (which is governed by our Terms of Service).


2. Definitions

For purposes of this Policy, the following terms shall have the meanings set forth below:

TermDefinition
Artificial Intelligence (AI)Computer systems designed to perform tasks that typically require human intelligence, including but not limited to natural language understanding, pattern recognition, content generation, and decision support.
Machine Learning (ML)A subset of AI involving algorithms that improve performance on tasks through experience (training on data) without explicit programming for each task.
Foundation ModelA large-scale AI model trained on broad data that can be adapted to a wide range of downstream tasks (e.g., GPT-4, Claude, LLaMA).
Fine-Tuned ModelA foundation model that has been further trained on specific data to improve performance on particular tasks or domains.
InferenceThe process of using a trained AI model to generate predictions, classifications, or outputs based on new input data.
PromptInput provided to an AI model to generate a response, including user queries, system instructions, and context.
EmbeddingA numerical vector representation of text, images, or other data that captures semantic meaning and enables similarity comparisons.
Retrieval Augmented Generation (RAG)A technique combining information retrieval with generative AI to produce responses grounded in retrieved context.
HallucinationAI-generated content that is factually incorrect, fabricated, or inconsistent with provided context or training data.
Prompt InjectionAn attack technique where malicious input manipulates an AI model's behavior to bypass safety controls or produce unintended outputs.
Zero-Retention APIAn API configuration where the provider contractually commits to not retaining, storing, or using submitted data for any purpose including model training.
TokenA unit of text processed by language models; for GPT models, approximately 4 characters or 0.75 words in English.
Context WindowThe maximum amount of text (measured in tokens) an AI model can process in a single request, including both input and output.
TemperatureA parameter controlling randomness in AI model outputs; lower values produce more deterministic responses.
Model ProviderA third-party organization providing AI model access via API (e.g., OpenAI, Anthropic, Google).
Data ResidencyThe geographic location(s) where data is processed and stored, relevant for regulatory compliance.
AI FeatureAny product functionality that utilizes AI/ML capabilities to process, analyze, generate, or transform data.
Tenant IsolationSecurity controls ensuring one customer's data cannot be accessed by or affect another customer's AI operations.

3. AI Features and Capabilities

3.1 Current AI Feature Portfolio

Acme Cloud offers the following AI-powered capabilities, all of which are disabled by default for new organizations:

Feature NameDescriptionAI ComponentsDefault StatePlan Availability
Smart SummarizeGenerates concise summaries of documents, threads, and conversationsGPT-4o for generationDisabledProfessional, Enterprise
Workflow AssistSuggests automation steps based on observed patterns and contextGPT-4o-mini for suggestions, internal model for pattern detectionDisabledEnterprise
Semantic SearchNatural language search across workspace content with contextual understandingInternal embedding model for indexing, RAG for retrievalDisabledProfessional, Enterprise
Content DraftGenerates draft content based on templates and contextGPT-4o for generationDisabledEnterprise
Sentiment AnalysisAnalyzes communication tone and sentiment for feedback categorizationInternal classification modelDisabledEnterprise
Support CopilotInternal tool assisting Acme Cloud support team (not customer-facing AI)GPT-4o with RAG on knowledge baseInternal onlyN/A
Translation AssistTranslates content between supported languagesGPT-4o for translationDisabledEnterprise
Action ExtractionIdentifies action items from meeting notes and conversationsGPT-4o-mini for extractionDisabledEnterprise

3.2 Feature Configuration Matrix

FeatureOrg-Level TogglePer-Workspace TogglePer-User Opt-OutAdmin Audit LogsAPI AccessData Residency Options
Smart SummarizeYesYesYesYesYesUS, EU (Q2 2026)
Workflow AssistYesYesNoYesNoUS only
Semantic SearchYesYesYesYesYesUS, EU (Q2 2026)
Content DraftYesYesYesYesYesUS, EU (Q2 2026)
Sentiment AnalysisYesYesNoYesYesUS, EU
Translation AssistYesYesYesYesYesUS, EU
Action ExtractionYesYesYesYesYesUS only

3.3 Feature Enablement Requirements

Feature CategoryEnablement RequirementsApproval Workflow
Basic AI FeaturesOrganization Admin enables via Admin ConsoleSelf-service
Advanced AI FeaturesOrganization Admin + CISO/Security Approval (if required by customer policy)Self-service with customer internal approval
PHI/Healthcare WorkspacesExplicitly prohibited unless covered by AI Addendum to BAARequires Acme Cloud and customer legal approval
Financial Services (GLBA)Requires AI risk assessment documentationSelf-service with customer risk assessment
EU Data ResidencyAvailable for select features with EU inferenceFeature-specific availability

4. Data Handling and Privacy

4.1 Data Processing for AI Features

When AI features are enabled, the following data may be processed:

Data CategoryProcessing PurposeRetention by Acme CloudRetention by Model ProviderProcessing Location
User PromptsGenerate AI responseMetadata logged 90 days; content processed transientlyZero retention (OpenAI API)US (EU Q2 2026)
Selected ContentProvide context for summarization, analysisProcessed transiently; not retainedZero retentionUS (EU Q2 2026)
Workspace MetadataImprove search relevance and suggestionsPer customer retention settingsNot shared with providerCustomer-configured region
Usage TelemetryFeature analytics, abuse detection90 days aggregatedN/AUS
EmbeddingsPower semantic searchEncrypted at rest; deleted within 30 days of disableGenerated by internal modelCustomer-configured region
AI Interaction LogsAudit trails for compliance90 days or customer-configuredN/ACustomer-configured region
Feedback DataImprove AI quality (explicit opt-in only)Per feedback policyNever sharedUS

4.2 Absolute Data Prohibitions

Acme Cloud commits to the following data handling prohibitions:

ProhibitionDescriptionEnforcement Mechanism
No Training on Customer DataCustomer content is never used to train or fine-tune any foundation modelContractual terms with model providers; technical controls
No Cross-Tenant Data SharingOne customer's data is never visible to or influences another customer's AI outputsTenant isolation architecture; security testing
No Retention by Model ProvidersModel providers contractually prohibited from retaining submitted dataZero-retention API agreements; annual audit
No Secondary UseCustomer data processed only for requested AI featuresData processing agreements; access controls
No Third-Party SharingAI processing data not shared with parties beyond contracted subprocessorsSubprocessor restrictions; contractual controls

4.3 Subprocessor and Model Provider Details

ProviderServices UsedModelsData Handling AgreementProcessing LocationLast Security Review
OpenAI, L.L.C.Text generation, summarization, translationGPT-4o, GPT-4o-miniZero-retention API agreement; SOC 2 Type IIUS (Microsoft Azure)Q4 2025
Acme Cloud (Internal)Embedding generation, classificationCustom embedding modelInternal processingAWS (customer region)Continuous
Amazon Web ServicesInfrastructure for internal AI modelsN/ADPA; SOC 2, ISO 27001Customer-configuredQ3 2025

Provider Selection Criteria:

CriterionRequirementVerification Method
Security CertificationSOC 2 Type II minimumAnnual certificate review
Data HandlingZero-retention or equivalent commitmentContractual review, annual audit
Privacy ControlsGDPR-compliant processingDPA review, TIA where required
Availability99.9% uptime commitmentSLA review, monitoring
Incident Response24-hour breach notificationContractual requirement
Financial StabilityViable ongoing operationAnnual vendor risk assessment

5. Customer Controls and Administration

5.1 Administrative Controls

ControlLocationEffectEffective Timing
Organization AI Master ToggleAdmin Console → Security → AI FeaturesEnables/disables all AI features organization-wide15 minutes
Per-Feature TogglesAdmin Console → Features → AIGranular enable/disable for each AI feature15 minutes
Workspace AI RestrictionsWorkspace Settings → SecurityDisable AI for specific workspaces (e.g., confidential projects)Immediate
User-Level Opt-OutUser Settings → PrivacyIndividual user declines AI features (where permitted)Immediate
API AI AccessAdmin Console → API SettingsControl API access to AI endpointsImmediate
Audit Log ExportAdmin Console → Compliance → LogsExport AI usage audit logsOn-demand
Data Residency SelectionAdmin Console → Security → Data ResidencySelect EU inference where availablePer feature migration timeline

5.2 Disable and Data Deletion Process

ActionTriggerEffectData Deletion Timeline
Disable AI Organization-WideAdmin toggles master switch offAll AI inference requests blocked within 15 minutesEmbeddings deleted within 30 days; logs retained per retention policy
Disable Semantic SearchAdmin disables featureNew indexing stopped; existing search functionality disabledEmbeddings deleted within 30 days
Workspace AI RestrictionAdmin restricts workspaceAI features unavailable in workspaceWorkspace embeddings deleted within 30 days
Account DeletionCustomer terminates serviceAll customer data deleted per DPAPer standard deletion schedule (30-90 days)
Data Export RequestCustomer submits DSRAI-related data included in exportPer DSR timeline (30 days)

5.3 Enterprise Contract Controls

Enterprise customers may negotiate the following contractual controls:

ControlDescriptionImplementation
AI Feature ProhibitionContractually prohibit AI features for tenantTechnical enforcement, audit verification
Model Provider RestrictionsLimit approved model providersConfiguration management, audit
Data Residency RequirementsMandate EU-only processingFeature availability may vary
Audit RightsRight to audit AI processing controlsScheduled upon request
Custom RetentionModified AI log retentionConfiguration per contract
AI AddendumDetailed AI-specific terms supplementing DPALegal attachment

6. Human Oversight and AI Limitations

6.1 Human Oversight Principles

AI output within Acme Cloud is assistive, not authoritative. The following principles govern human-AI interaction:

PrincipleImplementationUser Responsibility
Review Before RelianceAI-generated content is clearly labeled as AI outputUsers must review AI output before using in decisions or communications
No Autonomous ActionsAI features suggest but do not execute actions without user confirmationUsers approve any actions based on AI suggestions
Context LimitationsAI operates only on provided context; cannot access external systems without explicit integrationUsers provide appropriate context; understand AI cannot know information not provided
Accuracy Not GuaranteedAI may produce incorrect, incomplete, or outdated informationUsers verify critical information through authoritative sources
Bias AwarenessAI models may reflect biases present in training dataUsers apply judgment to AI output, especially for sensitive decisions

6.2 Known AI Limitations

LimitationDescriptionMitigationUser Guidance
HallucinationAI may generate plausible-sounding but incorrect informationOutput validation, citation requirementsVerify facts independently; do not rely on AI for accuracy-critical information
Context WindowLimited amount of text processable in single requestChunking strategies, summarizationLarge documents may be processed in parts; summary quality may vary
Recency CutoffFoundation models trained on historical dataRAG for current informationAI may not reflect information after training cutoff
Reasoning LimitsComplex multi-step reasoning may be unreliableProblem decompositionBreak complex problems into steps; verify intermediate reasoning
BiasPotential biases in model outputsBias testing, model selectionApply critical judgment; seek diverse perspectives for important decisions
ConsistencySame input may produce different outputsTemperature controls, determinism settingsOutputs may vary; verify important outputs
SecurityPotential for prompt injection attacksInput sanitization, output validationReport suspicious AI behavior to security

6.3 Prohibited Use Cases

Customers and users must not use Acme Cloud AI features for the following purposes:

Prohibited UseRationaleEnforcement
Autonomous decision-making affecting individual rightsRegulatory compliance, ethical AITerms of Service, technical controls
Generation of content for illegal purposesLegal complianceAbuse detection, terms enforcement
Processing of special category data without appropriate safeguardsGDPR, privacy lawConfiguration restrictions
PHI processing without BAA AI AddendumHIPAA complianceTechnical enforcement
Content that deceives individuals about AI involvementEthical AI, regulatory complianceTerms of Service
Circumventing safety controlsSecurity, ethical AIAbuse detection, account suspension
Processing children's data without appropriate consentCOPPA, GDPRAge verification controls
Generating content that impersonates individualsFraud prevention, ethicsAbuse detection

7. Security Controls for AI

7.1 AI-Specific Security Measures

Control CategoryControlImplementationTesting Frequency
Input ValidationPrompt injection preventionInput sanitization, pattern detectionQuarterly
Output ValidationSensitive data leakage preventionOutput scanning, PII detectionQuarterly
Tenant IsolationPrevent cross-tenant data exposureArchitectural isolation, access controlsContinuous
Rate LimitingAbuse preventionPer-organization, per-user limitsContinuous monitoring
Content FilteringBlock prohibited content generationPre and post-generation filtersQuarterly review
Audit LoggingComprehensive AI operation loggingStructured logging, tamper-proof storageContinuous
EncryptionProtect data in transit and at restTLS 1.3 in transit, AES-256 at restAnnual certification
Access ControlLimit AI feature accessRBAC, feature togglesContinuous
Kill SwitchEmergency AI disable capabilityOrganization-level and platform-levelQuarterly testing

7.2 AI Red Team Testing

Test TypeFrequencyScopeFindings Action
Prompt injection testingQuarterlyAll customer-facing AI featuresCritical/High: 72 hours remediation; Medium/Low: standard SLA
Output data leakage testingQuarterlyAll features processing customer dataPer severity
Adversarial input testingSemi-annualCustomer input pathsPer severity
Model manipulation testingAnnualInternal and external modelsPer severity
Jailbreak attempt testingQuarterlyContent generation featuresPer severity
Cross-tenant isolation testingQuarterlyAll AI featuresCritical if breach detected

7.3 AI Incident Classification

Incident TypeSeverityExampleResponse Timeline
Cross-tenant data exposure via AICriticalCustomer A sees Customer B's data in AI outputImmediate disable, 4-hour executive notification
Successful prompt injection with impactHighAttacker extracts sensitive information24-hour remediation, customer notification
AI generates prohibited contentMediumContent filter bypass72-hour fix, process review
Unexpected AI behaviorLowQuality degradation without security impactStandard bug tracking
Model provider incidentVariableOpenAI security incidentPer provider notification, assess customer impact

8. Regulatory Compliance

8.1 EU AI Act Alignment

Acme Cloud monitors EU AI Act requirements and currently classifies features as follows:

FeatureEU AI Act Risk ClassificationRationaleCompliance Actions
Smart SummarizeLimited/Minimal RiskContent generation without high-risk decision-makingTransparency documentation
Workflow AssistLimited RiskSuggestion only, human approval requiredUser notification of AI involvement
Semantic SearchMinimal RiskSearch assistance without significant impactStandard documentation
Sentiment AnalysisLimited RiskAnalysis only, not automated decision-makingTransparency, human review requirement
All FeaturesNot High-RiskNo safety components, biometric identification, or high-risk categoriesMonitoring for scope changes

8.2 Compliance Framework Mapping

RegulationApplicabilityAcme Cloud Compliance Approach
EU AI ActEU users, EU customersRisk classification, transparency documentation, human oversight requirements
GDPREU data subjectsLawful basis documentation, DPIA where required, data subject rights
CCPA/CPRACalifornia residentsConsumer rights, disclosure requirements
HIPAAPHI processingAI features disabled for PHI workspaces unless AI Addendum
SOC 2All customersAI controls mapped to Trust Services Criteria
ISO 27001All customersAI processing within ISMS scope
State AI LawsVariableMonitoring emerging state requirements (Colorado, Connecticut, etc.)

8.3 DPIA Support

For customers requiring Data Protection Impact Assessments for AI feature usage:

ResourceAvailabilityAccess
AI Processing DescriptionStandard templateTrust Center download
Technical Security MeasuresDocumentationTrust Center
Subprocessor DetailsCurrent listSubprocessor List page
AI-Specific DPA TermsFor Enterprise customersLegal request
DPIA TemplatePre-filled for common scenariosEnterprise customer request
ConsultationFor complex assessmentsProfessional services

9. AI Governance Structure

9.1 AI Governance Committee

Acme Cloud maintains a cross-functional AI Governance Committee with the following structure:

RoleCommittee MemberResponsibilities
ChairVP ProductMeeting facilitation, decision escalation
Security LeadCISOSecurity controls, risk assessment, incident review
Privacy LeadChief Privacy OfficerData protection, regulatory compliance
Engineering LeadVP EngineeringTechnical implementation, model operations
Legal LeadGeneral CounselContractual, regulatory, liability
Ethics AdvisorExternal (Advisory)Ethical AI principles, bias review

Committee Cadence and Authorities:

ActivityFrequencyAuthority Level
Regular meetingsMonthlyRecommendation to executive team
New AI feature reviewPer feature launchApproval required before launch
Model provider changePer changeApproval required
Incident reviewPer AI-related incidentFindings and remediation oversight
Regulatory update reviewQuarterlyCompliance program updates
Annual AI program assessmentAnnualReport to Board (via Audit Committee)
Emergency decisionsAs neededVP Product + CISO joint authority

9.2 Governance Decision Framework

Decision TypeApproval AuthorityDocumentation Required
New AI feature (minor)Product Lead + Security ReviewFeature specification, security assessment
New AI feature (significant)AI Governance CommitteeFull AI impact assessment
New model providerAI Governance Committee + LegalProvider assessment, DPA review, security evaluation
Model change (same provider)Engineering Lead + Security ReviewChange documentation, testing results
AI feature disable (planned)Product LeadCustomer communication plan
AI feature disable (emergency)CISO or VP ProductIncident documentation
Customer AI addendumLegalContract negotiation

9.3 AI Incident Governance

Incident SeverityNotificationInvestigation LeadResolution Authority
CriticalCISO (immediate), CEO (4 hours), Board (24 hours)CISOCEO
HighCISO (4 hours), VP Product (4 hours)Security EngineeringCISO + VP Product
MediumSecurity Engineering ManagerSecurity EngineeringSecurity Engineering Manager
LowStandard ticketingEngineeringEngineering Lead

10. Transparency and Documentation

10.1 Customer-Facing Documentation

DocumentLocationUpdate FrequencyContent
AI Feature GuideHelp CenterPer feature releaseFeature descriptions, use cases, limitations
AI Security OverviewTrust CenterQuarterlySecurity controls, compliance information
AI Data Flow DocumentationTrust CenterQuarterlyData processing diagrams, retention information
Model Provider InformationSubprocessor ListPer change (30-day notice)Provider details, data handling
AI FAQsHelp CenterMonthlyCommon questions and answers

10.2 Transparency Metrics

Acme Cloud publishes the following AI metrics to Enterprise customers quarterly:

MetricDescriptionCurrent Status
AI feature adoption ratePercentage of eligible organizations with AI enabled34% (Q4 2025)
Average AI response latencyP50 latency for AI feature responses1.2 seconds
AI availabilityUptime for AI features99.94%
Security incidents (AI-related)Count of AI-related security incidents0 (FY2025)
Model accuracy feedbackCustomer-reported accuracy issues0.3% of interactions
AI feature satisfactionNPS for AI features+42

10.3 AI Model Card Information

For transparency regarding AI models used:

ModelProviderCapabilitiesLimitationsTraining Data CutoffVersion
GPT-4oOpenAIText generation, summarization, translation, analysisHallucination risk, context window limits, reasoning errors~Oct 2023 + webgpt-4o-2024-08-06
GPT-4o-miniOpenAILightweight text tasksSame as GPT-4o, lower quality on complex tasks~Oct 2023gpt-4o-mini-2024-07-18
Internal Embedding ModelAcme CloudText embedding for semantic searchDomain-specific accuracy variesInternal training datav2.1

11. AI Feature Roadmap

11.1 Planned Enhancements

Feature/EnhancementTarget QuarterCustomer ImpactPrerequisites
EU-hosted inference (Smart Summarize, Semantic Search)Q2 2026EU data residency complianceInfrastructure deployment
Enhanced citation in Smart SummarizeQ1 2026Improved source attributionModel capability
Multi-language support (French, German, Spanish)Q2 2026Broader accessibilityLocalization, model evaluation
Custom model routing (Enterprise)Q3 2026Customer model selectionArchitecture, security review
AI risk assessment templateQ1 2026DPIA supportDocumentation
Detailed AI usage analyticsQ2 2026Admin visibilityDashboard development
AI feature API expansionQ3 2026Programmatic AI accessAPI development, security

11.2 Feature Deprecation Policy

StageTimelineCustomer Communication
Deprecation announcement180 days before removalEmail to admins, in-app notification, Trust Center update
Feature freeze90 days before removalNo new functionality
Migration support90 days before removalDocumentation, support resources
Soft disable30 days before removalWarning on feature use
Hard disableTarget dateFeature removed
Data cleanup30 days after removalAssociated data deleted per retention policy

12. SOC 2 and ISO 27001 Control Mapping

12.1 SOC 2 Trust Services Criteria Mapping

Control IDControl DescriptionAI Policy Implementation
CC1.1Integrity and ethical valuesAI ethics principles, prohibited uses, human oversight
CC1.2Board oversightAI Governance Committee reports to Board via Audit Committee
CC2.2Information and communicationAI documentation, transparency reporting
CC3.1Risk identificationAI-specific risk assessments
CC3.2Risk assessmentModel provider evaluation, AI security testing
CC3.3Risk managementAI security controls, incident response
CC4.1Monitoring controlsAI audit logging, metrics monitoring
CC5.2Control activitiesTechnical and administrative AI controls
CC6.1Logical access controlsAI feature access controls, API security
CC6.7Data classification and handlingAI data flows, retention policies
CC7.2Incident monitoringAI-specific incident detection
CC7.4Incident responseAI incident procedures
CC8.1Change managementAI feature and model change procedures
PI1.1Processing integrityAI output validation, human oversight
P3.1Personal information collectionAI data collection transparency
P4.2Personal information retentionAI data retention limits
P6.1Data subject rightsAI data deletion, export

12.2 ISO 27001:2022 Annex A Control Mapping

ControlControl TitleAI Policy Implementation
A.5.1Policies for information securityThis AI Policy as component of security policy
A.5.8Information security in project managementAI feature security review process
A.5.19Information security in supplier relationshipsModel provider security requirements
A.5.21Managing ICT supply chainModel provider evaluation and monitoring
A.5.23Information security for cloud servicesAI infrastructure security
A.6.3Information security awarenessAI security training
A.8.2Privileged access rightsAI admin access controls
A.8.3Information access restrictionAI feature access controls
A.8.4Access to source codeModel and AI code security
A.8.12Data leakage preventionAI output validation
A.8.16Monitoring activitiesAI audit logging
A.8.23Web filteringAI content filtering
A.8.25Secure development lifecycleAI feature development security
A.8.28Secure codingAI integration security

13. Customer Responsibilities

13.1 Customer Obligations for AI Feature Use

Customers enabling AI features are responsible for:

ResponsibilityDescriptionVerification
User ConsentObtain appropriate consent from end users for AI processing where requiredCustomer responsibility
Regulatory AssessmentAssess AI feature use against applicable industry regulationsCustomer responsibility
Use Case AppropriatenessEnsure AI features are used for appropriate purposesTerms of Service compliance
PHI RestrictionsDo not enable AI for PHI workspaces without AI AddendumTechnical and contractual enforcement
Special Category DataApply appropriate safeguards for sensitive dataCustomer responsibility
Output ReviewReview AI-generated content before relianceUser training
Access ControlProperly configure AI feature access within organizationAdmin console configuration
Incident ReportingReport suspected AI security issuesSecurity contact

13.2 Shared Responsibility Model for AI

Responsibility AreaAcme CloudCustomer
AI model security
Infrastructure security
AI feature access controls✓ (capability)✓ (configuration)
Input data appropriateness
Output review
Regulatory compliance (platform)
Regulatory compliance (use)
User training
Data classification
Consent management

Related Trust Center documents

privacy policy, dpa, subprocessor list, security overview, encryption standards, compliance frameworks, hipaa statement


Document revision history

VersionDateAuthorSummary of changes
1.02024-06-01Legal & ComplianceInitial Trust Center publication
2.02025-03-15GRC ProgramSOC 2 Type II alignment refresh; expanded subprocessors
2.52025-09-01Security EngineeringEncryption standards update; ISO 27001 mapping
3.02026-01-15Trust Center ProgramFull procurement-grade expansion; 34-document set

Contact

Acme Cloud, Inc. 1200 Market Street, Suite 400 San Francisco, CA 94103, USA

ChannelEmailUse case
Trust & procurementtrust@acmecloud.comSecurity questionnaires, trust reviews
Securitysecurity@acmecloud.comIncidents, vulnerabilities, control questions
Privacyprivacy@acmecloud.comDSRs, privacy assessments
Legallegal@acmecloud.comContractual, DPA, legal notices

14. Policy Updates and Communication

14.1 Policy Change Notification

Change TypeAdvance NoticeCommunication Channels
Material changes to AI data handling30 daysEmail to admins, Trust Center, in-app notification
New AI feature launch14 days (Enterprise), at launch (others)Email, product announcements
Model provider change30 daysEmail to admins, Subprocessor List update
Security control changes30 daysTrust Center update
Pricing changes (AI features)60 daysEmail to billing contacts
Feature deprecation180 daysPer deprecation policy

14.2 Contact Information

Inquiry TypeContactResponse SLA
AI trust and compliance questionsai-trust@acmecloud.com2 business days
AI security concernssecurity@acmecloud.com1 business day
AI feature requestsproduct-feedback@acmecloud.comAcknowledgment only
Enterprise AI addendumlegal@acmecloud.com5 business days
AI feature supportsupport@acmecloud.comPer support tier
Disable AI featuresAdmin Console (self-service) or trust@acmecloud.comImmediate (self-service)

Primary AI Policy Contact: ai-trust@acmecloud.com

This Policy is effective as of January 1, 2026. Acme Cloud reserves the right to update this Policy at any time. Material changes will be communicated in accordance with the notification procedures above. Continued use of AI features after notification constitutes acceptance of updated terms.

Last updated: January 15, 2026
EthicPages logoEthicPages