Partner console · Privacy & data
Privacy control center
A structured view of how your workspace data is handled, what you can adjust on this device, and how to exercise your rights. Preferences below are stored locally until account-level APIs are connected.
Overview
Security & compliance signals
Protection in transit
Console traffic uses TLS. Sessions are scoped to your tenant.
Data safeguards
Role-based access and audit-oriented events for sensitive actions (as deployed for your workspace).
Agreements
Your order form, DPA, or master agreement govern where they differ from this summary.
Review contracts with your legal ownerData collection
Choose what non-essential diagnostics and analytics this browser may send. Core security and billing processing may still apply.
Console usage analytics
Aggregated clicks, load times, and feature usage to improve reliability and layout.
Impact: When off, we receive fewer signals to prioritize fixes; essential error reporting may continue.
Technical diagnostics
Detailed error payloads and client context to reproduce issues faster.
Impact: When off, support may need more manual detail if you report a bug.
Data sharing
Control how operational data leaves your immediate session for administrators and product teams.
Share with workspace administrators
Allow tenant admins to see activity and configuration tied to your account role.
Impact: When off, some collaboration and oversight features may be limited for your workspace.
Product feedback loop
Opt in to sharing anonymized usage patterns with Lociq product teams.
Impact: When on, insights may inform roadmap; you can withdraw consent anytime on this device.
Access control
Session and visibility preferences for this device. Enterprise policy may override these when connected.
Session reminders
In-app notices before idle timeout and renewal prompts.
Impact: When off, you may miss warnings before automatic sign-out.
Expose API audit hints in UI
Surface when programmatic access last touched resources you can see.
Impact: When off, audit context stays hidden in the interface (logs may still exist server-side).
Data visibility
What the partner console typically processes and why. Exact categories depend on your deployment and integrations.
| Category | Collected | How it is used |
|---|---|---|
| Account & auth | Email, name, role, tenant id | Sign-in, authorization, support, and billing correlation. |
| Console activity | Views, edits, timestamps | Operations, audit trails, and workspace administration. |
| Campaign & anchor data | Configuration you submit | Delivering programs, analytics, and Dropverse-linked experiences. |
| Technical logs | IP, device hints, errors | Security monitoring, abuse prevention, and reliability. |
Your data actions
Export, deletion, and reset flows. Backend wiring will connect these to your tenant services.
Deletion for production tenants is coordinated with your admin and legal owner. This button opens a confirmation — no data is removed from the button alone.