Privacy Policy

Last updated: July 16, 2026

Overview

Model Optimizer helps engineering teams understand and reduce their AWS Bedrock spend. To do that, we read your Bedrock Model Invocation Logging (MIL) data from S3 in your AWS account, calculate cost and usage metrics, and surface optimization recommendations in our web application. This page explains what we collect, how we use it, where it lives, and what choices you have.

We've tried to keep this in plain language. If anything here is unclear or you'd like more detail, email us at hello@modeloptimizer.ai.

Who we are

"Model Optimizer," "we," "us," and "our" refer to the team operating the Model Optimizer service at www.modeloptimizer.ai and the application at app.modeloptimizer.ai. You can reach us with any privacy questions at hello@modeloptimizer.ai.

What we collect

• Account information. When you sign up, we collect your name, email address, and organization. This is used to authenticate you and to associate you with your team's account.
• Billing information. If you upgrade to a paid plan, billing details (card information, billing address) are collected and processed by Stripe. We do not store your full card details on our servers — Stripe handles that. We retain a customer ID, subscription ID, and the resulting invoice/charge metadata so that we can reconcile billing.
• Your AWS Bedrock usage data. Once you connect a data source, we read MIL records from the S3 bucket you point us at. For each Bedrock invocation we ingest, we store fields such as: timestamp, AWS account ID, AWS region, model ID, input/output token counts, calculated cost, request latency, request status, and any error code or message returned by Bedrock.
• Prompt and response content (only if you choose to share it). Bedrock MIL records can include the full prompt and response text. Whether that content reaches us depends on the data mode you select during onboarding (see "Two data modes" below).
• Connection configuration. The IAM role ARN, S3 bucket name, External ID, and data mode you configure for each data source.
• Site usage analytics. When you browse our marketing site, we collect usage events — pages viewed, clicks on signup prompts, and which gated pricing features you use — through PostHog. See "Cookies and tracking" below for details.
• Email correspondence. If you email us, we receive your message and email address and may retain it for support history.

Two data modes

During onboarding you choose how much MIL content reaches us:

• Full Analytics Mode. We read MIL records directly from your S3 bucket. Those records may include the full prompt and response text, depending on how you've configured Bedrock MIL. If they do, we ingest and store them — we use prompt content to group similar prompts and rate task complexity, which is what powers the model right-sizing recommendations.
• Privacy Mode. You deploy a small Lambda function (the "Bedrock Log Sanitizer") inside your own AWS account using a CloudFormation template we provide. The sanitizer strips the prompt body (input.inputBodyJson) and response body (output.outputBodyJson) from each MIL record before writing the sanitized records to a separate S3 bucket. We only read from that sanitized bucket. The original prompts and responses never leave your account.

Privacy Mode trades some recommendation depth (we can't analyze prompt complexity if we never see the prompts) for stronger data isolation. If your Bedrock usage involves content you cannot share with a third-party processor — PHI, regulated financial data, or anything similar — use Privacy Mode, or do not connect Model Optimizer to that workload at all.

How we connect to your AWS account

We do not ask for or accept AWS access keys. The CloudFormation template you deploy creates an IAM role in your account that trusts our AWS account and is gated by a unique External ID we generate for you. The role's permissions are limited to the S3 actions needed to list and read objects from the bucket you specify (s3:ListBucket, s3:GetBucketLocation, and s3:GetObject on that bucket only). We have no write access, no access to other resources in your account, and you can revoke our access at any time by deleting the CloudFormation stack.

How we use the information

• Operate the service. Authenticate you, render the dashboard, calculate cost and usage metrics, generate optimization recommendations, and aggregate daily summaries.
• Bill you, if you're on a paid plan. Calculate your usage-based charge and report it to Stripe so you can be invoiced.
• Communicate with you. Send transactional email related to your account (sign-in links, billing notifications, connection-failure alerts, security notices) and reply to support emails.
• Improve the product. Debug issues, troubleshoot ingestion failures, and improve the quality of our recommendations.
• Protect the service. Investigate abuse, fraud, and security issues, and comply with applicable law.

We do not sell your data, and we do not use your prompts, responses, or usage data to train machine-learning models.

Where your data lives and how it's protected

• Region. Our infrastructure runs in AWS us-east-1 (N. Virginia). Account data, configuration, and ingested usage records are stored there.
• Encryption in transit. All traffic to our web application, API, and AWS services is over HTTPS/TLS.
• Encryption at rest. Customer data stored in DynamoDB and S3 is encrypted at rest using AWS KMS-managed keys.
• Access control. Internal access to production data is limited to the small operations team that runs the service, and is granted on a need-to-know basis through AWS IAM.
• Point-in-time recovery. Our primary DynamoDB tables have point-in-time recovery enabled to protect against accidental loss.

We do not currently hold SOC 2, ISO 27001, HIPAA, or PCI certifications. If your organization requires any of those, please factor that in before connecting workloads that fall under those regimes.

How long we keep your data

• Bedrock usage records. Ingested usage records are stored for approximately 3 years from the record's timestamp, after which they expire automatically.
• Account and configuration data. Retained for as long as your account is active. If you close your account or delete a data source, we will delete the associated configuration and stop ingesting from it.
• Billing records. Retained as long as needed to meet tax, accounting, and audit obligations.
• Email correspondence. Retained for support history; you can ask us to delete specific messages.

Service providers we share data with

We use a small number of third-party services to operate Model Optimizer. Each of them only receives the minimum data necessary to do its job:

• Amazon Web Services (AWS). Our hosting and storage provider. All ingested data, application servers, and email delivery (via Amazon SES) run on AWS.
• Stytch. Handles user authentication and team-membership for our application. Stytch receives your email address and name when you sign up or are invited to a team.
• PostHog. Provides product analytics for our marketing site. PostHog receives the usage events described under "Cookies and tracking" below (page views, clicks on signup prompts, and which gated pricing features you use), and, if you are signed in, your email address so we can connect your activity before and after account creation.
• Stripe. Handles payment processing for paid plans. Stripe receives the billing information you provide at checkout and the usage-based charge amounts we report.
• Calendly. If you book a setup or sales call through a Calendly link we share with you, Calendly receives the contact and scheduling details you submit.

We may also disclose information if required to do so by law, or to protect the rights, property, or safety of Model Optimizer, our customers, or others.

Cookies and tracking

Analytics on the marketing site. Our marketing site at www.modeloptimizer.ai uses PostHog, a product-analytics service, to understand how visitors use the site — page views, clicks on signup prompts, and which pricing features are used. PostHog stores a small amount of data in your browser (cookies and similar storage) to recognize return visits. We use this to measure what's useful and improve the site; we do not use it for advertising, we do not sell this data, and we have session recording turned off — PostHog receives analytics events, not recordings of your screen or keystrokes. If you sign in, we associate your analytics activity with your account email so we can understand the journey from visitor to user. Apart from the PostHog analytics script itself, page resources — including fonts — are served from our own domain.

Signed-in sessions across our sites. Our application at app.modeloptimizer.ai uses cookies and similar storage as needed to keep you signed in — these are essential to running the application and are not used for advertising or cross-site tracking. If you have an account and are signed in, your session cookie is shared across our own modeloptimizer.ai subdomains so that pages on the marketing site (for example, the Bedrock pricing reference) can show you the signed-in features you're entitled to without a separate login. This never extends beyond our own domain.

Server-side request logs. Separately from the client-side behavior described above, our content delivery network (Amazon CloudFront) writes standard access logs to a private S3 bucket. Each entry records the request timestamp, the requested URL, response status, client IP address, referrer, and user agent. We use these logs for security monitoring and to understand site usage in aggregate. Logs are retained for 90 days and are not shared with any party outside of AWS, our infrastructure provider.

Your choices and rights

• Disconnect at any time. You can delete a data source in the application, which stops further ingestion, and you can delete the CloudFormation stack in your AWS account, which revokes our access entirely.
• Delete your account. Email us at hello@modeloptimizer.ai and we'll delete your account and the associated configuration and usage data. Some billing records may be retained as noted above.
• Access and export. If you'd like a copy of the data we hold about you or your organization, email us and we'll work with you to provide it.
• Correct or update. Most account details can be updated directly in the application. For anything else, email us.

Children

Model Optimizer is a business product not directed at children, and we do not knowingly collect personal information from anyone under 16.

Changes to this policy

When we make material changes to this policy we'll update the "Last updated" date above and, for significant changes, notify account owners by email. Continued use of the service after a change means you accept the updated policy.

Contact

Questions about this policy, your data, or how to exercise any of the choices above? Email us at hello@modeloptimizer.ai.