Amazon Q Developer vs. Ollama: data protection per plan

yes (AWS Service Terms, section 1.14.1: 'These Service Terms incorporate the AWS Data Processing Addendum ("DPA"), when you use AWS Services to process Customer Data'; no exception for the Free Tier is stated there; section 50.13 additionally governs the use of Free Tier content for service improvement)

yes (according to the GDPR Center, the AWS GDPR DPA, including standard contractual clauses, is part of the AWS Service Terms and applies automatically)

not publicly documented (no DPA on the retrieved pages; the Privacy Policy names Ollama Inc. as controller)

not publicly documented (no DPA on the retrieved pages; the Privacy Policy names Ollama Inc. as controller)

not publicly documented (no DPA on the retrieved pages; the Privacy Policy names Ollama Inc. as controller)

not publicly documented (no DPA on the retrieved pages; the Privacy Policy names Ollama Inc. as controller)

not publicly documented (no DPA on the retrieved pages; the Privacy Policy names Ollama Inc. as controller)

FAQ and documentation 'Amazon Q Developer service improvement': in the Free Tier, content (questions, responses, generated code) may be used for service improvement, according to the documentation including 'for model training'. Service Terms 50.13: Amazon Q Content may be used to improve Amazon Q and, for that purpose, stored outside the AWS Region in use; content that does not contain personal data may also be used to train other AWS ML models. Opt-out depending on the environment: IDE/command line via the setting 'Share Amazon Q content with AWS' or 'Amazon Q: Share Content'; console/mobile app/AWS websites/chat applications via an AI services opt-out policy in AWS Organizations. Telemetry (without code) can be switched off separately. Pricing page: 'Opt-out available'.

FAQ: Amazon Q Developer Pro and Amazon Q Business do not use content for service improvement; content from the Pro Tier is not used to train underlying foundation models. Telemetry/usage metrics may be collected (opt-out in the IDE settings). Pricing page: 'Automatically opted out'.

Pricing page (FAQ Privacy): "Prompt or response data is never logged or trained on." Terms (May 2026, section 5): Ollama does not use inputs or outputs to train AI models. Privacy Policy (March 2026): no use of inputs or outputs for training; prompt or response content is not requested in support requests. According to the pricing page, Ollama requires no-logging, no-training and zero-data-retention policies from hosting partners. Local use: according to the Privacy Policy, Ollama has no access to prompts and responses.

Pricing page (FAQ Privacy): "Prompt or response data is never logged or trained on." Terms (May 2026, section 5): Ollama does not use inputs or outputs to train AI models. Privacy Policy (March 2026): no use of inputs or outputs for training; prompt or response content is not requested in support requests. According to the pricing page, Ollama requires no-logging, no-training and zero-data-retention policies from hosting partners. Local use: according to the Privacy Policy, Ollama has no access to prompts and responses.

Pricing page (FAQ Privacy): "Prompt or response data is never logged or trained on." Terms (May 2026, section 5): Ollama does not use inputs or outputs to train AI models. Privacy Policy (March 2026): no use of inputs or outputs for training; prompt or response content is not requested in support requests. According to the pricing page, Ollama requires no-logging, no-training and zero-data-retention policies from hosting partners. Local use: according to the Privacy Policy, Ollama has no access to prompts and responses.

Pricing page (FAQ Privacy): "Prompt or response data is never logged or trained on." Terms (May 2026, section 5): Ollama does not use inputs or outputs to train AI models. Privacy Policy (March 2026): no use of inputs or outputs for training; prompt or response content is not requested in support requests. According to the pricing page, Ollama requires no-logging, no-training and zero-data-retention policies from hosting partners. Local use: according to the Privacy Policy, Ollama has no access to prompts and responses.

Pricing page (FAQ Privacy): "Prompt or response data is never logged or trained on." Terms (May 2026, section 5): Ollama does not use inputs or outputs to train AI models. Privacy Policy (March 2026): no use of inputs or outputs for training; prompt or response content is not requested in support requests. According to the pricing page, Ollama requires no-logging, no-training and zero-data-retention policies from hosting partners. Local use: according to the Privacy Policy, Ollama has no access to prompts and responses.

Documentation 'Data storage in Amazon Q Developer': in the Free Tier, content is stored in a US Region (console error diagnosis: US West/Oregon, everything else: US East/N. Virginia). Cross-region inference may route requests to other Regions within the geography. Service Terms 50.13.1: content used for service improvement may be stored outside the Region in use. The sub-processor list names Canada, Germany, the Netherlands and the USA as locations of the AWS entities that process Free Tier content for service improvement (only without opt-out).

Documentation 'Amazon Q Developer Pro Region support': the Q Developer console and profile are available in US East (N. Virginia) and Europe (Frankfurt); Pro via a personal Builder ID only in US East (N. Virginia). Documentation 'Data storage': in the Pro Tier, content is stored in the profile Region only for the following features: Q chat in the AWS console, error diagnosis in the console, Q in Eclipse, JetBrains, VS Code and Visual Studio, and Q on the command line; for all other features 'your content may be stored and processed in a US Region' (can be blocked via a service control policy). Exceptions include: Amazon Q artifacts (visualisations) in a US Region; Console to Code stored in the console Region and processed in a US Region; CloudWatch investigations possibly in other Regions. Not available for profiles in Frankfurt: support chat, troubleshooting resources, .NET transformation in the IDE, Slack integration, Console Mobile App, GitLab Duo with Amazon Q, Amazon Q for GitHub. Cross-region inference stays within the geography (Europe: Frankfurt, Ireland, Paris, Stockholm).

Pricing page (FAQ Privacy): Ollama hosts models and compute resources primarily in the United States; to serve global demand, traffic may be routed to Europe ("may route to Europe for additional capacity"). A selectable EU region is not documented. Privacy Policy: data may be transferred to and processed in the United States. Local models run on the user's own device.

Pricing page (FAQ Privacy): Ollama hosts models and compute resources primarily in the United States; to serve global demand, traffic may be routed to Europe ("may route to Europe for additional capacity"). A selectable EU region is not documented. Privacy Policy: data may be transferred to and processed in the United States. Local models run on the user's own device.

Pricing page (FAQ Privacy): Ollama hosts models and compute resources primarily in the United States; to serve global demand, traffic may be routed to Europe ("may route to Europe for additional capacity"). A selectable EU region is not documented. Privacy Policy: data may be transferred to and processed in the United States. Local models run on the user's own device.

Pricing page (FAQ Privacy): Ollama hosts models and compute resources primarily in the United States; to serve global demand, traffic may be routed to Europe ("may route to Europe for additional capacity"). A selectable EU region is not documented. Privacy Policy: data may be transferred to and processed in the United States. Local models run on the user's own device.

Pricing page (FAQ Privacy): Ollama hosts models and compute resources primarily in the United States; to serve global demand, traffic may be routed to Europe ("may route to Europe for additional capacity"). A selectable EU region is not documented. Privacy Policy: data may be transferred to and processed in the United States. Local models run on the user's own device.

• Amazon Web Services EMEA SARL / Amazon Web Services, Inc. (contracting party, depending on the account country)
• AWS infrastructure entities per region (e.g. A100 ROW GmbH, region Europe/Frankfurt)
• Amazon Bedrock (LLM inference; cross-region inference within the geography)
• The sub-processor list (section 'AWS entities providing service improvement') names the locations Canada, Germany, the Netherlands, US for 'Amazon Q Developer Free Tier / Kiro Free Tier / Individual Subscriber'; applies provided the customer has not objected to use for service improvement

• Amazon Web Services EMEA SARL / Amazon Web Services, Inc. (contracting party, depending on the account country)
• AWS infrastructure entities per region (e.g. A100 ROW GmbH, region Europe/Frankfurt)
• Amazon Bedrock (LLM inference; cross-region inference within the geography)
• The sub-processor list (section 'AWS entities providing service improvement') names the locations Canada, Germany, the Netherlands, US for 'Amazon Q Developer Free Tier / Kiro Free Tier / Individual Subscriber'; applies provided the customer has not objected to use for service improvement

• NVIDIA Cloud Providers (NCPs) for hosting open models, without names or locations (pricing page)
• Stripe (payment processing, according to the Terms and Privacy Policy)
• Cloud infrastructure and model inference providers according to the Privacy Policy, without names
• Sub-processor list: not publicly documented

• NVIDIA Cloud Providers (NCPs) for hosting open models, without names or locations (pricing page)
• Stripe (payment processing, according to the Terms and Privacy Policy)
• Cloud infrastructure and model inference providers according to the Privacy Policy, without names
• Sub-processor list: not publicly documented

• NVIDIA Cloud Providers (NCPs) for hosting open models, without names or locations (pricing page)
• Stripe (payment processing, according to the Terms and Privacy Policy)
• Cloud infrastructure and model inference providers according to the Privacy Policy, without names
• Sub-processor list: not publicly documented

• NVIDIA Cloud Providers (NCPs) for hosting open models, without names or locations (pricing page)
• Stripe (payment processing, according to the Terms and Privacy Policy)
• Cloud infrastructure and model inference providers according to the Privacy Policy, without names
• Sub-processor list: not publicly documented

• NVIDIA Cloud Providers (NCPs) for hosting open models, without names or locations (pricing page)
• Stripe (payment processing, according to the Terms and Privacy Policy)
• Cloud infrastructure and model inference providers according to the Privacy Policy, without names
• Sub-processor list: not publicly documented

0 USD (pricing page)

19 USD per user per month (pricing page, no indication whether incl. VAT; according to AWS Tax Help, AWS Europe charges VAT on service charges for accounts in the EU)

0 USD (pricing page). Additional usage credits at token prices per million tokens, e.g. gpt-oss:120b 0.15 USD input and 0.60 USD output; off-peak prices outside 12:00–18:00 UTC on weekdays and all day at weekends. Purchased credits expire after one year; the customer is responsible for taxes (Terms).

20 USD per month or 200 USD per year (16.67 USD per month billed annually) (pricing page); one account per person. The customer is responsible for taxes (Terms).

100 USD per month (pricing page); one account per person. The customer is responsible for taxes (Terms).

from 500 USD per month (pricing page); usage beyond the included credits is billed from a shared team balance as you go. According to the FAQ, Ollama creates a separate team account on joining. The customer is responsible for taxes (Terms).

Custom (pricing page: "Custom", volume usage pricing; contact via sales)

yes (50 agentic requests per month in IDE/CLI; Java upgrade transformation up to 1,000 lines of code per month; console Q&A)

yes (extended limits for agentic requests, according to the FAQ 10,000 inference calls per month or around 1,000 user requests; Java/.NET transformation up to 4,000 lines of code per user in the pool; admin dashboard, IP indemnity)

yes (cloud models with starter usage credits and access to starter models; all cloud models after buying usage credits; local models unlimited; 1 concurrent request)

yes (Free plus 60 USD of usage credits per month, larger pro models, several models concurrently, 3 concurrent requests; Fast mode "coming soon" according to the pricing page)

yes (Pro plus 300 USD of usage credits per month, early access to the newest models, 10 concurrent requests)

yes (Pro plus unlimited users, 1,000 USD of usage credits per month shared across the team, centralised billing and administration, priority support, 10 concurrent requests; shared projects "coming soon" according to the pricing page)

yes (Team plus model access controls, cost budgets for users and API keys, private Slack channel with dedicated support, custom security questionnaires)