PROdb Cookies
What cookies does PROdb set and what do they do
On this page 3
PROdb's platform dbFLEX uses cookies for authentication, storing certain user preferences, and tracking user movements within the application. No cookies contain personally identifiable information (PII).
Standard Cookies
The following cookies are used in the V3 and V2 user interfaces:
| Cookie | Purpose | Scope | Access |
|---|---|---|---|
| .SOD | Authorization information — encrypted, contains no personal data | /secure | Server only |
| lastappid | Last visited database identifier (number) | /secure | Server only |
| opendoc | Short-lived cookie for "Navigate to Document" custom action | /secure/db/{app-id} | Server only |
| td-wks | Currently selected workspace ID (number) | /secure/db/{app-id} | Set by script, read by server |
| v3 | Indicates the user switched to the V3 design | /secure/db/{app-id} | Set by script, read by server |
Browser-only Settings (V2 UI only)
The V3 UI stores these in localStorage instead:
| Cookie | Purpose |
|---|---|
| td-sidebar | Show or hide the sidebar |
| td-dense | Use small or large fonts |
Admin Setup Cookies
Used by system administrators in the setup section:
| Cookie | Purpose | Scope | Access |
|---|---|---|---|
| CSRFToken | Short-lived encrypted token for cross-site request forgery protection | /secure | Server only |
| pins | List of pinned table IDs | /secure/db/{app-id} or /setup | Set by script, read by server |
For session timeout and cookie lifecycle details, see the PROdb Security Details page.