Grok 4.7
Data-use posture
Not used to train the provider's models
On the AWS Bedrock FAQ, expand the question "Will AWS and third-party model providers use customer inputs to or outputs from Amazon Bedrock to train Amazon Nova, Amazon Titan or any third-party models?" The answer reads: "No, AWS and the third-party model providers will not use any inputs to or outputs from Amazon Bedrock to train Amazon Nova, Amazon Titan, or any third-party models."
No provider-side logging of your prompts
Because the model providers don't have access to those accounts, they don't have access to Amazon Bedrock logs or to customer prompts and completions.
Not yet verified for this route
Not yet verified for this route
Not yet verified for this route
Not yet verified for this route
Not yet verified for this route
Where requests are processed
Amazon Web Services
These accounts are owned and operated by the Amazon Bedrock service team. Model providers don't have any access to those accounts.
Any region where the provider runs this model. Listed today: North America: Canada, Mexico, United States. South America: Brazil. Europe: France, Germany, Ireland, Italy, Spain, Sweden, Switzerland, United Kingdom. Asia: Bahrain, India, Indonesia, Israel, Japan, Malaysia, Singapore, South Korea, Taiwan, Thailand, United Arab Emirates. Oceania: Australia, New Zealand. Africa: South Africa. The provider can add regions without notice.
The destination Regions for Global cross-Region inference profiles include all commercial Regions.
North America: Canada, Mexico, United States. South America: Brazil. Europe: France, Germany, Ireland, Italy, Spain, Sweden, Switzerland, United Kingdom. Asia: Bahrain, India, Indonesia, Israel, Japan, Malaysia, Singapore, South Korea, Taiwan, Thailand, United Arab Emirates. Oceania: Australia, New Zealand. Africa: South Africa. Content the provider keeps for abuse review is stored where the request was processed.
If cross-region inference is enabled for these models, retained inputs and outputs are stored in destination regions (i.e., the region where your inference request is processed).
Data sent between the provider's regions stays on the provider's network, does not cross the public internet and is encrypted in transit.
All data transmitted during cross-Region operations remains on the AWS network and does not traverse the public internet. Data is encrypted in transit between AWS Regions.
The provider's logs for Northern Inference's account record these requests in the provider region Northern Inference calls. Listed today: North America: Canada.
CloudTrail logs all cross-Region inference requests in your source Region.
When using global cross-Region inference, CloudWatch and CloudTrail continue to record log entries in your source AWS Region, simplifying observability and management.
AWS China Regions, AWS GovCloud (US) Regions
AWS commercial Regions are in the aws partition, Regions in China are in the aws-cn partition, and AWS GovCloud Regions are in the aws-us-gov partition.
With global inference profiles, Amazon Bedrock automatically selects a commercial AWS Region to process the request.
2026-10-21
Archived policy evidence
Northern Inference keeps a timestamped, hash-verified archive of this provider's data-use policy, so the legal basis that applied to any request can be shown after the fact.