Local Data Storage in ProfileSpider
Learn what ProfileSpider stores locally in your browser, what uses the backend, how exports work, and what happens if browser data is cleared.
Quick answer
ProfileSpider saves profiles, lists, tags, and notes locally in your browser using IndexedDB. That saved list data is not stored on ProfileSpider servers. Export is the main backup method. Account, credit, billing, team data, and AI extraction calls still use the backend.
Local
What ProfileSpider Stores Locally
Saved lead data lives in your browser, not in a cloud CRM.
Saved profiles
Profiles, people, companies, or leads you save in the extension are stored locally in your browser.
Lists
Your saved ProfileSpider lists are stored in local browser storage using IndexedDB.
Tags
Tags used to organize leads by campaign, client, source, region, role, or status are stored locally.
Notes
Manual notes added to saved rows are stored locally with your saved profiles.
Column settings
Column visibility and custom export header labels are stored locally as one global browser setting.
Export preferences
Export-related settings are handled locally where applicable, and exported files are generated client-side.
Backend
What Is Not Local-Only
Some parts of ProfileSpider require backend services to work.
Account data
Your account and login state use ProfileSpider backend services.
Credits and billing
Credit balances, subscription data, top-ups, invoices, and billing actions use backend and Stripe systems.
Team data
Team membership, team credit pool data, and current-cycle team usage use backend services.
AI extraction calls
AI-powered extraction and enrichment calls use backend services to process page or URL content.
Email finding
Email finding uses external/provider-backed services and is not a purely local operation.
Credit API and sync
Credit information is retrieved from the ProfileSpider API and can be updated through live sync.
Privacy
What Is Not Stored on ProfileSpider Servers
Saved profiles and lead rows are not stored on ProfileSpider servers.
Saved lists are not stored on ProfileSpider servers.
Tags and notes attached to saved profiles are not stored on ProfileSpider servers.
Exported files are generated client-side from your local saved data.
ProfileSpider does not act as a cloud CRM for your saved lead lists.
Storage
How Local Browser Storage Works
ProfileSpider stores saved profiles, lists, tags, and notes in your browser using IndexedDB.
IndexedDB is browser storage. That means your saved ProfileSpider data is tied to the browser profile and device where you use the extension.
If you use a different browser, a different Chrome profile, or another computer, your saved local lists may not appear there unless you exported and moved the data yourself.
Backup
Export Is the Backup Method
Because saved list data is local, export important lists before clearing browser data or changing devices.
Export to Excel
Use Excel when you want a normal spreadsheet for review, backup, or client handoff.
Export to CSV
Use CSV when you want a portable file for CRM imports, outreach tools, or spreadsheet workflows.
Export to JSON
Use JSON when you want structured data for technical workflows, scripts, or backups.
Risk
When Local Data Can Be Removed
Exports
How Exports Relate to Local Storage
Exports are generated from the saved data in your browser.
Exporting does not use credits. You can export saved lists to CSV, Excel, or JSON.
Exported files are plain, unbranded files. Once exported, you can store them wherever you normally keep spreadsheets or backups.
Teams
How Local Storage Works with Teams
Team credits and team membership use backend services, but saved profiles, lists, tags, and notes remain local to the browser where they were saved.
A team credit pool lets selected members spend shared credits, but it does not turn saved lead lists into shared cloud records.
If a team needs to share a list, export it to CSV, Excel, or JSON and share the exported file through your normal workflow.
Best practices
Best Practices for Local Data
Export important lists regularly.
Export before clearing browser data or uninstalling the extension.
Use clear list names and tags so exported files stay understandable later.
Keep source URLs in exports so you can verify where each row came from.
Use Excel or CSV exports for client handoff, CRM imports, and team sharing.
Use JSON exports when you need a technical backup or structured data file.
Clarifications
Common Misunderstandings
ProfileSpider is not a cloud CRM
Saved profiles and lists are local to your browser. They are not stored as shared cloud CRM records.
Not everything is local-only
Account, billing, credits, team data, AI extraction, enrichment, and email finding use backend or provider services.
Export is your backup
Because saved lead data is local, exporting is the main way to back up or move lists.
Team credits are not shared lists
A shared team credit pool does not mean all team members automatically share the same saved local lists.
Questions