Privacy Policy
Last updated: August 10, 2026
mosAIc ("mosAIc", "we", "us") provides AI functions inside Google Sheets. This policy explains what data the mosAIc add-on and backend receive, how we use it, and who else processes it. mosAIc is currently a private beta operated by an individual developer; you can reach us any time at dheerajneelam.10@gmail.com.
What we receive
- Your mosAIc API key. A
mosaic_live_…key identifies your account and is sent with every request. It is stored (as a hash) so we can authenticate you and enforce usage limits. - The content you pass to a function. When you call
=mAI(…)or anmAI_*helper, the values from the cells you reference — and any instruction you type — are sent to the mosAIc backend so it can generate a result. This may include whatever text you put in those cells. - Usage metadata. For each non-cached request we record technical metadata: the task type (e.g. summarize), the model used, token counts, estimated cost, latency, and a timestamp.
What we do not store
We do not save the text of your cells, your instructions, or the AI's responses in our database. Usage records contain only the technical metadata listed above — never the content itself.
To keep the service fast and cheap, the backend keeps a short-lived result cache (up to 6 hours). The cache key is a one-way cryptographic hash of the request, so your input text is not recoverable from it; the cached value is the generated result, which is automatically discarded after the cache expires.
Who else processes your data
To generate results and run the service, your request passes through these providers:
| Provider | Role | What it sees |
|---|---|---|
| OpenRouter | Model gateway that routes to the underlying AI model | Your instruction and input text, to generate the result |
| Underlying model providers (e.g. OpenAI, Anthropic, Google) via OpenRouter | Run the AI model that produces the result | Your instruction and input text |
| Supabase | Backend hosting, database, and authentication | Your API key hash and usage metadata |
| Upstash (Redis) | Short-lived result cache and rate limiting | Hashed request keys and cached results (≤6h) |
| Google (Apps Script) | Runs the add-on inside your spreadsheet | Governed by Google's own privacy policy |
These providers process data on our behalf under their own terms and privacy policies. We do not control, and are not responsible for, how the underlying model providers handle prompts sent through OpenRouter — review OpenRouter's policy for details. Because of this, do not send sensitive, confidential, or regulated data (personal health information, government IDs, payment card data, etc.) through mosAIc.
How we use data
- To generate the AI results you request.
- To authenticate you, enforce rate limits and monthly quotas, and prevent abuse.
- To understand aggregate usage and cost so we can improve routing and reliability.
We do not sell your data, and we do not use your content to train our own models (we don't train models).
Data retention
Cached results expire automatically within 6 hours. Usage metadata is retained while your account is active so we can operate limits and diagnose issues. You can ask us to revoke your key and delete your associated metadata at any time by emailing us.
Google user data
The add-on requests only the permissions it needs to read the cells you reference and to make requests to the mosAIc backend. It does not read spreadsheets you don't invoke it on, and it does not transmit your Google account credentials anywhere. mosAIc's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Children
mosAIc is not directed to children under 13 and should not be used by them.
Changes
We may update this policy as the product grows. Material changes will be reflected by the "last updated" date above.
Contact
Questions or data requests: dheerajneelam.10@gmail.com.