WhoPrompt
FeaturesPricingFAQContactSign InStart Free
Documentation

Database Connection
Documentation

Everything you need to know about securely connecting your databases to WhoPrompt

Quick Start

Get connected in 3 simple steps

1

Create Read-Only User

Set up a database user with SELECT-only permissions

2

Enable SSL/TLS

Ensure encrypted connections are enabled

3

Add Connection

Paste your connection string in WhoPrompt

Security Overview

WhoPrompt securely connects to your database to run read-only queries. Your credentials are encrypted using AES-256-GCM encryption and stored securely. We never access your data directly - all queries run through secure, isolated connections.

AES-256 Encryption

All credentials encrypted at rest

Read-Only Queries

Only SELECT statements allowed

No Data Storage

Query results never stored permanently

Supported Databases

PostgreSQL

Popular
  • Full support
  • SSL/TLS
  • Read-only mode

MySQL

Popular
  • Full support
  • SSL/TLS
  • Read-only mode

Spreadsheet

Popular
  • XLSX, XLS, CSV
  • Up to 50MB
  • Automatic parsing

SQL Server

  • Full support
  • TLS encryption
  • Read-only mode

SQLite

  • File-based
  • Local only
  • Read-only mode

Spreadsheet Uploads

For non-technical users or for quick analysis, WhoPrompt allows you to upload spreadsheet files directly. We handle the parsing and make your data available for analysis.

Supported Formats

XLSX, XLS, and CSV files are supported.

Instant Analysis

Your spreadsheet is made available for analysis right after upload.

Connection String Formats

PostgreSQL Connection

Format:

postgresql://username:password@hostname:5432/database_name?sslmode=require

Popular Providers:

Neon
postgresql://user:pass@ep-xxx.aws.neon.tech/dbname?sslmode=require
Supabase
postgresql://postgres:pass@db.xxx.supabase.co:5432/postgres
Railway
postgresql://postgres:pass@containers-us-west-xxx.railway.app:5432/railway

Security Best Practices

Exclude Sensitive Tables

High

For enhanced privacy, you can exclude specific tables from being accessed by the AI. This is useful for tables containing PII or other sensitive information.

Create a Read-Only User

Critical

Grant only SELECT permissions. Never give INSERT, UPDATE, or DELETE access.

Enable SSL/TLS Encryption

Critical

Always use encrypted connections for production databases to protect data in transit.

Use Strong Passwords

High

Generate complex passwords with mixed characters, numbers, and symbols.

Rotate Credentials Regularly

Change database passwords every 90 days and update them in WhoPrompt.

Configure Firewall Rules

High

Whitelist only necessary IP addresses to access your database.

Use Private Networks

Keep databases in private networks (VPC) when possible, use VPN or SSH tunnels.

Do's and Don'ts

Do's
  • Use read-only database users
  • Enable SSL/TLS encryption for production
  • Use strong, unique passwords
  • Whitelist specific IP addresses in firewall
  • Rotate credentials every 90 days
  • Keep database in private network (VPC)
Don'ts
  • Grant INSERT, UPDATE, or DELETE permissions
  • Hardcode credentials in application code
  • Share database credentials across multiple services
  • Disable SSL for production databases
  • Use default or weak passwords
  • Expose databases directly to the internet without firewall rules

Troubleshooting Common Issues

Need Help?

Can't find what you're looking for? Our support team is here to help you get connected.

Contact SupportGet Started Free

Typical response time: Within 24 hours