Privacy Policy
Last updated November 15, 2026
This policy explains how Simple Injection LLC (“we”, “us”) handles information through simpleinjection.com (the “Website”), our cloud dashboard at dashboard.simpleinjection.com (the “Dashboard”), and our AI-assistant plugins for OpenAI and Anthropic (the “Plugins”).
Summary
- We do not sell personal information or any data collected through the Website, Dashboard, or Plugins, and we do not use it for advertising.
- We do not use Plugin or Dashboard data to train AI models.
- The Plugins are read-only. They can look up device information for the one company you authorize. They cannot operate pumps, change setpoints, or make purchases.
- We never see your conversation with your AI assistant. We receive only the tool request (such as a device identifier or a date) and your connection credential.
- What a Plugin returns is passed to your AI-assistant platform, which handles it under its own policies.
- Plugin read events are recorded, with their time, in your company’s activity history, which we retain permanently as an audit trail.
Information you give us
When you submit the quote request form, the contact form, or the email prompt before downloading a resource, we receive the details you enter, such as your name, company, email address, phone number, and application notes. We use this information to respond to your request, prepare quotes, provide support, and follow up on products you asked about. Downloading a resource requires agreeing to receive our newsletter; we add your email address to our newsletter list and record each resource you download with it, and you can unsubscribe at any time with the link in any newsletter email. When you request a quote or send us a message through the contact form, we also add your email address to our newsletter list unless you untick the newsletter box on the form. When you enter a giveaway, we receive your name, email address, and, if you choose to give it, your phone number, along with the bonus actions you report completing and the friends who entered with your referral link. We use this to run the giveaway, contact the winner, and send our newsletter, which entering requires.
Dashboard accounts and device information
The Dashboard uses Firebase Authentication to sign users in with an email address and password or a Google account, and requires a verified email address. It stores account details such as your name, email address, company, and role, and the company’s records. Dashboard account holders are also subscribed to our newsletter: we share your name, email address, and company with Brevo for this, and you can unsubscribe at any time with the link in any newsletter email without affecting your Dashboard account.
It also stores and displays information from connected pumps and tank level monitors, including device identifiers (IMEI) and names, pump status and setpoints, tank levels and chemical labels, injection measurements, battery voltage, assigned labels or hashtags, alarms, and timestamps. The information available depends on the device and the records held by the service. Device names, chemical labels, and hashtags are text your company enters; please do not put personal information in them.
AI-assistant plugins
When you connect a Plugin, your AI assistant can ask Simple Injection for read-only information about the company you authorize. The Plugin connects to our hosted service at dashboard.simpleinjection.com/api/v1/mcp. It does not operate pumps, change setpoints, or process purchases, and there is no tool that does.
What each tool receives and returns
These are all of the tools the Plugin provides. Every result is limited to the company that authenticated.
| Tool | What the assistant sends us | What we return |
|---|---|---|
list_devices | None. | The company’s internal key and name, then for every pump and tank level monitor: device identifier (IMEI), device name, device type, tank levels and chemical labels, battery voltage, assigned hashtags, active alarms, and last-update time. Pumps also return head on/off status, head setpoints, and latest injection amounts. Tank level monitors also return tank level heights, days until empty, yesterday’s and this month’s drop, and the configured injection rate and unit. |
get_device | Device identifier (IMEI). | For a pump: device identifier, name and type, head on/off status and setpoints, latest tank levels, battery voltage, and hashtags. For a tank level monitor: device identifier, name and type, tank levels, chemical labels and level heights, days until empty, yesterday’s and this month’s drop, injection rate and unit, battery voltage, hashtags, active alarms, and last-update time. No history. |
get_device_history | Device identifier (IMEI); start date (up to 365 days back); optional maximum number of readings (2 to 1,000, default 200). | The device’s current state (the same fields as get_device), the start and end time of the period, and timestamped tank-level (gallons) and battery-voltage readings from the start date until now. Each reading carries its time as both a text timestamp and a Unix timestamp. Long histories are evenly sampled to the requested size, and the result says how many readings existed, how many were returned, and whether sampling happened. |
get_device_alarms | Device identifier (IMEI); optional start date (default last 30 days, up to 365 days back); optional maximum number of entries (1 to 500, default 100). | The device identifier and name, its currently active alarms, the start and end time of the period, and its alarm history (activations and clearances, each with alarm message text and a timestamp). |
get_profile | None. Available on OAuth connections only. | The name and email address of the Dashboard user who authorized the connection, a label combining that name (or email) with the company name, and a stable identifier derived from a one-way hash of the user and company identifiers. It contains no credentials. |
Along with each request we receive the connection credential (an OAuth access token or a company API key), which we use only to identify the connection and company. Some values may be missing for a particular device, and the Plugin returns what the service holds.
Connecting and authenticating
Connecting through OAuth sends you to a Simple Injection sign-in and consent page. Only a company administrator can authorize a connection, and you choose which company to grant. The connection has a single permission (“devices:read”). Each time a connection refreshes, we re-check that the authorizing user is still an administrator of that company; if not, or if a refresh token is ever reused, the connection is revoked.
Company API keys are an alternative connection method. An administrator creates and deletes them in the Dashboard’s API Keys Management page. Anyone holding a key can read that company’s device data through the Plugin, so keep keys private.
We keep these authentication records:
| Record | What it contains | How long |
|---|---|---|
| Registered assistant application | Application name and redirect addresses supplied by the AI-assistant platform when it registers, a generated client identifier, and the registration time. | Kept as registered. It contains no user information. |
| Pending authorization request | Client identifier, redirect address, a PKCE code challenge, an opaque state value, the requested scope, and an expiry. | Valid for 10 minutes; deleted once you approve or deny. |
| Authorization code | Stored only as a one-way hash, together with the client identifier, the authorizing user’s identifier, the selected company, and an expiry. | Valid for 5 minutes; deleted when exchanged for tokens. |
| Access and refresh tokens | Stored only as one-way hashes, together with the client identifier, the authorizing user’s identifier, the selected company, scope, a grant identifier, and timestamps. | Access tokens expire after 1 hour; refresh tokens after 30 days and can be used only once (each refresh issues a new pair). |
| Grant record | Client identifier, user identifier, company, whether the grant is revoked, and hashes of the current token pair. | Kept while the connection is active and after it is revoked, so that revoked tokens stay rejected. |
| Company API key (alternative connection method) | The key value, the company it belongs to, the name and identifier of the Dashboard user who created it, and the creation time. | Kept until a company administrator deletes it in the Dashboard. |
What we do not collect through the Plugins
We do not receive your prompts, your conversation history, or files from your AI assistant, and we do not store the data returned by a tool call as a separate copy. We do not record your IP address, browser, or device details in the Plugin’s own records, although our infrastructure provider may process such technical request data to operate and protect the service (see “Logs” below).
Sharing with your AI-assistant platform
Tool results are returned to the AI-assistant platform you connected, such as OpenAI or Anthropic, so it can respond to you. That platform processes the information under its own privacy policy and your account or organization settings, which also determine whether and how long it keeps the results. Disconnecting the Plugin does not delete information the platform already received; use that platform’s controls for its retention and deletion. On OAuth connections, the platform can also receive your account name, email address, and a company label so it can show which connection is active.
Activity history and logs
Activity history
Each successful device-data read (every tool except get_profile) creates a company activity record naming the tool used and, depending on the tool, a device identifier or device counts (for example, “Tool: get_device. Device: 123456789012345.”). Authorizing an AI assistant also creates a record that includes the authorizing user’s identifier. Every record is stored with the exact time of the event (to the millisecond), so it shows when a company’s devices were queried. Records are readable by the company’s administrators in the Dashboard and by Simple Injection super administrators. They do not include the data that was returned, the request’s IP address, or your conversation.
We retain activity records permanently, as the company’s audit trail of who accessed or changed what, and when. That history lets a company investigate unauthorized access or a disputed change long after the fact, and it lets us show what happened if there is a dispute about equipment. Records contain no returned device data, and only the authorization record names an individual user. Disconnecting a Plugin does not delete that history, and it is not subject to routine deletion.
Logs
Our hosted service writes operational logs to Google Cloud logging. These record security and operational events such as an OAuth authorization being granted (including the user and company identifiers), API key creation or deletion (showing only the last four characters of the key), and unexpected errors, which can include a device identifier. Google’s infrastructure may also log technical request data, such as IP addresses and request details, for security and operations. These logs are kept for 30 days (see “Retention”). We use logs only to run, secure, and troubleshoot the service.
How we use information
- To respond to inquiries, provide quotes, and support customers.
- To send our newsletter to people who subscribe when requesting a quote, contacting us, downloading a resource, or entering a giveaway, and to Dashboard account holders.
- To run giveaways and contact their winners.
- To authenticate users and connections and to limit access to the authorized company.
- To provide the Dashboard and to answer the requests made through the Plugins.
- To keep compliance records, secure the service, prevent misuse, and troubleshoot errors.
- To measure and improve how the Website and the Dashboard are used, and to find and fix errors.
- To send the alarm alerts and account emails you ask for.
We do not use Plugin or Dashboard data for advertising, to build profiles, to sell or share with data brokers, or to train AI models.
Who receives information
| Recipient | What | Why |
|---|---|---|
| Your AI-assistant platform (OpenAI for ChatGPT, Anthropic for Claude) | Tool results described above, and for OAuth connections your account name, email address, and company label. | To answer the request you made to your assistant. The platform processes this under its own privacy policy and your account or organization settings. |
| Google (Firebase Authentication, Cloud Functions, Realtime Database, Firebase Hosting, Cloud Logging, Cloud Messaging) | Sign-in credentials, account and company records, device data, authentication records, activity history, operational logs, and the content of push notifications. | Google is our infrastructure provider for the Dashboard and the hosted Plugin service. It acts on our behalf. |
| Sentry (Functional Software, Inc.) | Error and crash reports from the Dashboard web app: the error and its stack trace, the page address, browser and device type, our app version, and your IP address. If you use the in-app feedback form, whatever you write in it. | To detect and fix faults in the Dashboard. Used in the Dashboard web app only, not by the hosted Plugin service. |
| Contentsquare | Usage analytics from the Dashboard web app: pages and screens visited, clicks, scrolling, and navigation, plus browser, device, and technical network information. Contentsquare sets first-party cookies in your browser to recognize repeat visits. | To understand how the Dashboard is used and to improve its usability. Used in the Dashboard web app only, not by the hosted Plugin service. |
| Twilio | The mobile number of a user who turned on SMS alarm notifications, and the text of the message: the device name and identifier, the alarm message, and the device’s GPS coordinates. | To deliver SMS alarm alerts. Sent only to users who have a phone number on their account and have enabled SMS notifications for that alarm. |
| SendGrid (Twilio) | The email address of the recipient and the content of the message: welcome and invitation emails and, for users who enabled email notifications, alarm alert emails. | To deliver account and alarm emails from the Dashboard. |
| Brevo | The details you enter into website forms, the email address you give when requesting a quote, contacting us, downloading a resource, or entering a giveaway, which of those you signed up through, the name, email address, and company of Dashboard account holders, and which resources you download. | To deliver form submissions to our team by email, to send our newsletter to its subscribers, and to keep a record of the resources each subscriber has downloaded. |
| Google (Tag Manager, YouTube) | Website interaction events and technical browser and network information. | Website measurement, and playback of embedded video. This applies to the Website only, not the Plugins. |
Our Website is hosted on Google Firebase Hosting, and its forms are processed by Google Cloud Functions, which may log technical data such as IP addresses and request details for security and operations. Google is our only infrastructure provider for hosting the Dashboard and the hosted Plugin service; the other recipients above handle specific functions. We may also disclose information if required by law or to protect our rights, users, or the security of the service, and to a successor if our business is sold or reorganized.
Dashboard analytics, error reporting, and notifications
The Dashboard web app, including its sign-in page and the consent page you see when you connect a Plugin, uses two third-party tools in production. Contentsquare records how the app is used (pages and screens visited, clicks, scrolling, and navigation, with browser and device details) so we can improve it. Sentry receives error and crash reports, including your IP address. Neither tool is used by the hosted Plugin service, so tool requests made through a Plugin are not sent to them. Their retention is listed under “Retention”.
You can block these tools with your browser’s privacy settings or a content blocker without losing access to the Dashboard. If you use the optional in-app feedback form, what you write is sent to Sentry.
Alarm alerts are sent by SMS (through Twilio), by email (through SendGrid), or as push notifications (through Google), only to users who have enabled that channel. An SMS alert includes the device name, its identifier, the alarm message, and the device’s GPS coordinates. You control which alerts you receive in your notification settings.
Website measurement
The Website loads Google Tag Manager and records website interactions, such as clicks on email, phone, and quote links, form submissions, resource downloads, and pump-sizing results, for measurement. Loading Google services sends technical browser and network information to Google. Browser privacy controls can limit third-party requests and storage. The Plugins do not use this measurement.
Local storage
We store a few items in your browser’s local storage so the site works as expected: your product comparison selections, and a flag or email address remembering that you have already unlocked resource downloads. This data stays on your device, and you can clear it at any time in your browser settings.
Embedded content
The Platform page can load a video from YouTube (using the privacy-enhanced youtube-nocookie.com domain) once you choose to play it. Google may collect data under its own policies at that point. Links to LinkedIn, YouTube, and AI-assistant platforms take you to third-party sites with their own policies.
Retention
| Information | How long we keep it |
|---|---|
| Website form submissions | As long as needed to handle your request and maintain our business records. |
| Giveaway entries | Until the winner has been drawn and the prize delivered, plus a reasonable period to resolve any questions about the result. |
| Newsletter subscription | Until you unsubscribe using the link in any newsletter email, or ask us to remove you. |
| Dashboard account, company, and device telemetry | While the company’s Dashboard account is active. The Plugin can reach back at most 365 days of history. |
| Plugin authentication records | As listed in the table above. Expired tokens and codes stop working immediately. Records of expired or replaced entries may remain in our database after they stop working until we remove them; they cannot be used to access data. |
| Company activity history (including Plugin read and authorization events) | Retained permanently as the company’s audit trail of who accessed or changed what, and when. Each entry carries a timestamp and is readable by the company’s administrators and by Simple Injection super administrators. It is not subject to routine deletion. |
| Operational and diagnostic logs (Google Cloud Logging) | 30 days, which is Google Cloud Logging’s standard retention for application logs. Audit logs that Google keeps about administrative actions on our cloud project are retained by Google for 400 days. |
| Dashboard error reports (Sentry) | Up to 90 days, under Sentry’s standard retention. |
| Dashboard usage analytics (Contentsquare) | Up to 13 months, under Contentsquare’s standard retention. Its cookies last up to 13 months. |
| SMS alarm messages (Twilio) | Twilio keeps message records, including the message text, for up to 13 months by default. After that, records may remain only as metadata. |
Your choices and controls
- Disconnect a Plugin. Remove the connection in your AI-assistant platform’s settings. Your assistant then stops using it. Access tokens that were already issued expire within one hour, and refresh tokens within 30 days. To end access immediately, email us and we will revoke the connection.
- Delete an API key. A company administrator can delete a key on the Dashboard’s API Keys Management page, which stops every application using that key.
- Stop sharing by changing who is an administrator. If a user is no longer an administrator of a company, their OAuth connections for that company stop working at the next refresh.
- Access, correction, and deletion. You can ask what we hold about you, ask us to correct it, or ask us to delete it, including inquiry, account, authentication, telemetry, and diagnostic records. Email privacy@simpleinjection.com or use our contact page. We may need to verify your identity or company authority first. Deleting information does not change the permanent compliance-history retention described above, and disconnecting a Plugin or deleting a key does not by itself delete stored service records or information already shared with your AI-assistant platform.
- Company data. Pump and tank telemetry belongs to the company that owns the equipment. Where information concerns a company’s devices rather than you personally, requests are handled with that company’s authorized administrator.
- Browser controls. You can clear local storage and manage cookies and third-party requests in your browser.
Privacy rights
Depending on where you live, you may have the right to know what personal information we hold, to correct or delete it, to receive a copy, and not to be discriminated against for exercising these rights. We honor these requests for everyone, using the contact methods above. We do not sell or share personal information for cross-context behavioral advertising, and we do not make automated decisions about you with legal or similarly significant effect.
Security
Connections to the Website, Dashboard, and Plugin service use HTTPS. OAuth uses PKCE; authorization codes and tokens are stored only as one-way hashes; refresh tokens are single-use and rotate; and a reused refresh token revokes the whole connection. Authentication records are in database areas that browsers cannot read, and every Plugin request is limited to the single company that authenticated. No system is perfectly secure, so tell us promptly if you suspect a key, token, or account has been compromised.
Children
The Website, Dashboard, and Plugins are intended for businesses and are not directed to children. We do not knowingly collect personal information from children under 13. If you believe a child has given us information, contact us and we will delete it.
Changes
We may update this policy from time to time, for example when a Plugin tool changes what it receives or returns. The date above shows when it was last revised.
Contact
Simple Injection LLC
344 N Walsh Drive
Casper, WY 82609
(877) 866-4171
privacy@simpleinjection.com
