Security
Access to your Fusion environment
SQL Space sends your SQL to Oracle Fusion BI Publisher using an organization-owned connection. Passwords are encrypted at rest and decrypted on the server. One-time BI Administrator credentials used for report installation are not stored.
The installed report can run the SQL it receives. Restrict its BI Publisher permissions carefully. Automatic installation verifies read access on the report and data model for only the chosen role and BI Administrator; the containing folder can retain inherited permissions. If verification fails, the uploaded objects are removed and the app offers manual installation and permission instructions.
Tenant and account protection
Postgres row-level security separates organizations. Connection access also follows roles and member grants within an organization. Owners and admins use two-step login. SQL Space uses HTTPS in deployment, CSRF checks, security headers, rate limits and server-side checks on every signed-in request.
What is stored
Ordinary query results stay in server request and browser memory. Multi-sheet XLSX exports temporarily store result rows in Postgres: they are scoped to your organization and user, removed after successful workbook assembly, and expire after one hour. Maintenance removes expired exports on its five-minute schedule. Backups can retain those rows for up to seven days after live removal.
Saved SQL, history and audit records are stored separately and can contain sensitive SQL literals. History keeps up to 500 runs per user. SQL audit records are pruned after 365 days. Account security events stay until organization deletion. Operational logs are configured for 30-day retention; avoid placing personal data in connection names or error reports.
Actions taken by SQL Space operators on customer accounts (for example creating an organization, changing a role or seats, extending a trial, resetting a password or two-step login, granting operator access, or requesting an organization deletion) are recorded with the operator, the time, the organization and user concerned, and a written reason. These platform records hold no SQL, passwords, tokens or query results, are kept for 365 days, and remain after a customer organization is deleted. Operators have no access to saved SQL, results or stored connection passwords through the operator console. This draft statement is subject to the same legal review as the rest of this page.
Hosting, monitoring and deletion
Production runs on a dedicated virtual server from Contabo in Germany (EU), with a fixed outbound IP and daily database backups kept for at most seven days. The application encrypts stored connection passwords and authenticator secrets; the database files and backups on the server are not separately encrypted at rest. Sentry, when enabled, receives only error types and stack locations. Request data, credentials, SQL, SOAP bodies, exception messages, local variables and breadcrumbs are excluded from error monitoring.
An owner can request deletion with a password and authenticator code. Product access stops immediately. Live tenant data is purged after 30 days, on the maintenance schedule. The deletion record is written outside the database; when an off-server backup remote is configured, that record is copied there before the deletion is acknowledged, and a restore replays it before traffic resumes. Backups can still retain deleted data for up to seven days. SQL Space does not claim SOC 2 certification.