Privacy
Privacy built around minimal monitoring data.
This policy describes how DatabaseMeter handles account, monitoring, report, and analysis data. Deployment-specific analytics or legal notices may supplement these practices.
Account information
The application stores the immutable Auth0 subject needed for ownership, plus available profile fields such as email, email-verification state, and display name.
Monitoring and report information
Connected integrations store project metadata, aggregate usage snapshots, synchronization history, alert configuration, optional PostgreSQL statistics, weekly-report preferences, and limited email delivery history. When provider-resource monitoring is enabled, DatabaseMeter stores bounded normalized resource snapshots and capability states, not raw provider metric responses or provider label values. Hourly resource snapshots are retained for up to 90 days and daily resource rollups for up to 13 months. DatabaseMeter does not retrieve application table rows or SQL text.
Public PostgreSQL Health Check
Manual Health Check input is parsed locally and is not uploaded or persisted. If a signed-in user chooses an existing connection, the server runs the fixed read-only diagnostic through that encrypted connection and returns only the bounded statistics payload; the report is not saved to monitoring history. Both paths exclude application rows, credentials, connection details, client addresses, and SQL text.
Query-counter analyzer
CSV, TSV, and JSON imports for the pg_stat_statements analyzer are normalized locally. Query-text and unknown columns are discarded before the local report or download. A signed-in connected run returns only bounded counters through the existing encrypted read-only connection and does not save the one-time report.
On-demand AI analysis
When an authenticated user explicitly starts AI analysis, DatabaseMeter sends OpenAI a bounded package of normalized monitoring evidence selected for the predefined prompt and chosen database scope. Credentials, connection details, authentication identifiers, SQL text, application rows, and raw provider responses are excluded. OpenAI response storage is disabled for the request. OpenAI states that API data is not used for model training by default; its standard abuse-monitoring logs may be retained for up to 30 days unless different organization controls apply. DatabaseMeter retains the validated result and safe run metadata for 30 days unless the user deletes it sooner; the full input package is not retained.
Public-site analytics
DatabaseMeter uses Google Analytics on public pages to understand aggregate site use, such as page views, referring pages, approximate location, and browser or device information. Google Analytics may use cookies or similar identifiers. The analytics tag is not loaded in the authenticated dashboard, and DatabaseMeter does not intentionally send database names, project identifiers, monitoring values, credentials, SQL text, application rows, or Health Check and analyzer input to Google Analytics.
Service providers
The architecture uses Auth0 for identity, Vercel for application hosting, a dedicated Neon Postgres database for application records, Google Analytics for public-site measurement, OpenAI for optional user-triggered AI analysis, and Resend for enabled operational email delivery.
Control and contact
Users can disconnect integrations and permanently delete DatabaseMeter-owned account data from Settings. Privacy questions can be sent to info@aisuretech.com.
See the whole portfolio clearly.
Checking your secure session…