Skip to main content
Since Poge stores all data client-side in the browser’s LocalStorage, backups are essential for data protection. Poge includes built-in export/import functionality for both full data backup and settings-only backup.

​
Understanding Poge’s Data Storage

Poge stores several types of data in your browser:

Database Connections

Saved PostgreSQL server connections including host, port, username, and encrypted passwords.

Query History

Your SQL query history with timestamps and execution results.

Saved Notes

SQL notes and snippets you’ve saved for later use.

User Preferences

Theme settings, UI preferences, and editor configurations.
Browser data is not permanent. Clearing browser data, switching browsers, or using private/incognito mode will result in data loss. Regular backups are essential.

​
Backup Strategies

​
Automatic Browser Backup

Some browsers sync LocalStorage across devices, but this is not reliable for critical data:
  • Chrome/Edge: Syncs some data when signed in
  • Firefox: Syncs data across devices
  • Safari: Uses iCloud sync on Apple devices
Do not rely solely on browser sync. Always maintain manual backups of important connections and queries.

​
Manual Backup Frequency

Recommended backup schedule:
1

After adding new connections

Export your data immediately after adding important database connections.
2

Weekly for active users

If you use Poge daily, create weekly backups of your full data.
3

Before browser updates

Major browser updates can sometimes clear LocalStorage. Export beforehand.
4

Before switching devices

Export data before moving to a new computer or browser.

​
Encrypted Full Data Export

Poge uses encrypted .enc files for full data backups, protecting sensitive connection information.

​
Creating an Encrypted Backup

1

Open Settings

Click the Settings icon in the Poge interface.
2

Navigate to Export

Find the “Export Data” section.
3

Choose encryption password

Enter a strong password to encrypt your backup. This password will be required for restoration.
Store this password securely! Without it, your backup cannot be decrypted. Consider using a password manager.
4

Export

Click “Export Full Data”. A file named poge-backup-YYYY-MM-DD.enc will be downloaded.

​
What’s Included in Full Export

The encrypted export contains:
  • All database connections (including passwords)
  • Complete query history
  • Saved notes and snippets
  • User preferences and settings
  • Theme and UI customizations

​
Encryption Details

Poge uses strong encryption for backup files:
  • Algorithm: AES-256-GCM (industry standard)
  • Key derivation: PBKDF2 with high iteration count
  • Format: Encrypted JSON with authentication tag

​
Settings-Only Export

For sharing configurations without sensitive data, use settings-only export.

​
Creating a Settings Export

1

Open Settings

Navigate to the Settings panel.
2

Choose Settings Export

Select “Export Settings Only” instead of full export.
3

Download

A plain JSON file poge-settings-YYYY-MM-DD.json will be downloaded.

​
What’s Included in Settings Export

The settings export contains only:
  • UI preferences
  • Theme settings
  • Editor configurations
  • Display options
What’s NOT included:
  • Database connections
  • Passwords
  • Query history
  • Personal notes
Settings exports are plain JSON files (not encrypted) since they don’t contain sensitive data. They’re safe to share or version control.

​
Restoring from Backup

​
Restoring Encrypted Backup

1

Open Import

Navigate to Settings → Import Data.
2

Select backup file

Choose your .enc backup file.
3

Enter password

Provide the encryption password you used when creating the backup.
4

Choose import mode

Select how to handle existing data:
Combines backup data with existing data. Newer entries take precedence.
5

Import

Click “Import” and wait for confirmation.
Using “Replace” mode will permanently delete all current data. Use “Merge” mode if you’re unsure.

​
Restoring Settings

1

Open Import

Navigate to Settings → Import Settings.
2

Select settings file

Choose your .json settings file.
3

Import

Settings will be applied immediately. No password needed.

​
Migration Between Instances

Moving between different Poge instances (self-hosted, Vercel, different browsers) is straightforward.

​
Migrating to a New Instance

1

Export from source

On your current Poge instance:
  1. Export full data (encrypted)
  2. Save the .enc file securely
2

Access new instance

Open your new Poge deployment:
  • https://your-new-deployment.vercel.app
  • https://poge.yourdomain.com
  • http://localhost:3000 (self-hosted)
3

Import to destination

On the new instance:
  1. Go to Settings → Import
  2. Upload your .enc file
  3. Enter decryption password
  4. Choose “Replace” for clean migration
4

Verify migration

Check that all connections, history, and settings transferred correctly.

​
Cross-Browser Migration

Moving data between browsers (Chrome → Firefox, Safari → Edge): 
1. Open Poge in Browser A
2. Export full data → save to Downloads
3. Open Poge in Browser B
4. Import the saved file
5. Verify connections work

​
Team Distribution

Sharing connection templates with team members:
1

Create template connections

Set up database connections with placeholder credentials.
2

Export settings

Export settings-only (not full data) to avoid sharing passwords.
3

Distribute

Share the .json file with team members via:
  • Internal wiki
  • Git repository (safe since no passwords)
  • Team chat
4

Team imports

Each member:
  1. Imports the settings file
  2. Updates connections with their own credentials
Never share encrypted backups containing real passwords, even with team members. Each person should maintain their own credentials.

​
Backup Storage Best Practices

​
Secure Storage Locations

Store backup files and encryption passwords in a password manager:
  • 1Password (supports file attachments)
  • Bitwarden (secure notes with attachments)
  • LastPass (secure notes)

​
Backup File Organization

Keep your backups organized: 
backups/
├── 2026-03/
│   ├── poge-backup-2026-03-01.enc
│   ├── poge-backup-2026-03-08.enc
│   └── poge-backup-2026-03-15.enc
├── 2026-02/
│   └── poge-backup-2026-02-15.enc
└── settings/
    └── poge-settings-team-template.json

​
Backup Rotation Policy

Recommended retention schedule:
  • Daily: Keep last 7 days
  • Weekly: Keep last 4 weeks
  • Monthly: Keep last 12 months
  • Yearly: Keep indefinitely

​
Disaster Recovery

​
Scenario: Browser Cache Cleared

1

Don't panic

Your backup files are safe outside the browser.
2

Open Poge

Navigate to your Poge instance (it will appear empty).
3

Import latest backup

Import your most recent .enc backup file.
4

Resume work

All connections and history are restored.

​
Scenario: Lost Encryption Password

Without the encryption password, backup files cannot be decrypted. This is by design for security.
If you’ve lost your password:
  1. Check your password manager
  2. Check secure notes or documents where you might have saved it
  3. If truly lost, the backup is unrecoverable
  4. You’ll need to manually recreate connections
Prevention: Always store encryption passwords in a password manager.

​
Scenario: Corrupted Backup File

If a backup file is corrupted:
  1. Try an older backup file
  2. Check if you have cloud storage versions/history
  3. Use settings-only export if available (no encryption needed)

​
Automated Backup Scripts

For power users, automate backup reminders: 
// Run this in browser console to export data programmatically
const exportData = () => {
  const data = localStorage.getItem('poge-data')
  const blob = new Blob([data], { type: 'application/json' })
  const url = URL.createObjectURL(blob)
  const a = document.createElement('a')
  a.href = url
  a.download = `poge-backup-${new Date().toISOString().split('T')[0]}.json`
  a.click()
}

exportData()

​
Compliance and Data Governance

For organizations with compliance requirements:

​
Data Retention

  • Backups contain database credentials and query history
  • Follow your organization’s data retention policies
  • Securely delete old backups when no longer needed

​
GDPR Considerations

If you’re in the EU:
  • Backup files may contain personal data
  • Store backups in GDPR-compliant locations
  • Ensure backups are encrypted
  • Have a process for backup deletion on request

​
Backup Verification

Regularly test your backups:
1

Test in private browser

Open Poge in an incognito/private window.
2

Import backup

Import your latest backup to verify it works.
3

Test connections

Verify that database connections can be established.
4

Check query history

Ensure your query history is complete.
Test your backups at least once per quarter to ensure they’re valid and you remember your encryption password.

​
Migration Troubleshooting

​
Import fails with “Invalid password”

  • Double-check your password (case-sensitive)
  • Ensure you’re using the .enc file, not .json
  • Verify the file wasn’t corrupted during transfer

​
Connections don’t work after import

  • Database credentials may have changed
  • Server IP/hostname may be different
  • Check SSL/TLS requirements for the database

​
Missing query history

  • Ensure you used “Full Export”, not “Settings Only”
  • Check if you selected “Merge” instead of “Replace”
  • Verify the export date - you may have an older backup
Your data is now protected with a solid backup strategy!