Privacy Policy for Magicline Plus

1. Controller

2. Scope

This privacy policy applies to the Magicline Plus browser extension for Chrome and Chromium-based browsers. Magicline Plus enhances the Magicline web interface with internal studio workflows such as follow-up appointments, member data maintenance, Wellpass/aggregator assistance, SEPA mandate workflows, task text snippets, and feedback.

Magicline Plus is not the operator of Magicline. Data processed directly in Magicline is also subject to the privacy information of the relevant Magicline customer or studio and of Magicline.

3. Categories of data processed

• Authentication information: a revocable, studio- and device-scoped JARVIS device token in local extension storage, plus server-side token ID, hash, studio assignment, creation/use timestamps, and revocation status. Magicline passwords and Magicline API keys are not stored.
• Personally identifiable information: names, member numbers, profile references, contact details, visible profile data, and profile images within Magicline.
• Financial and payment information: IBAN/bank data, SEPA mandate information, payment run groups, and related follow-up tasks where required for enabled workflows.
• Personal communications: user-submitted feedback such as sender name/location, title, message, and optional screenshots.
• User activity in the extension: settings, feature toggles, reminders, workflow states, completed steps, and diagnostics.
• Website content: visible content of the Magicline web interface, tables, dialogs, form fields, SEPA PDFs, and page states needed for the selected feature.

Magicline Plus does not store Magicline passwords, PINs, or Magicline API keys. It uses the existing Magicline browser session. The optional central JARVIS connection does require and locally store the device token described above.

4. Purposes of processing

• Displaying and prioritizing follow-up appointment and member data maintenance hints.
• Supporting Wellpass/aggregator and customer change workflows.
• Preparing visible Magicline form filling so users can review data before saving.
• Executing clearly confirmed, bounded Magicline write actions for member data, notes, profile/card cleanup, bank account, payment-run group, partner-data exchange, and document upload.
• Studio-scoped central configuration and coordination through JARVIS, including feature/studio settings, reminders, member snapshots, activity/audit data, and statistics snapshots.
• Supporting SEPA mandate, local signing, document-upload hints, and temporary PDF handling.
• Saving extension settings, table/column configuration, text snippets, and local reminders.
• Providing local backup and restore functionality for Magicline Plus settings.
• Receiving and processing feedback or error reports.
• Security, diagnostics, and stability checks.

5. Browser storage

• chrome.storage.sync: small settings, feature toggles, filters, and columns; large task text snippets are not synced because of browser quotas.
• chrome.storage.local: the JARVIS device token, task text snippets, local reminders, “never ask” decisions, backup/recovery data, short-lived SEPA PDF buffers, and time-bounded write reservations containing action/customer references to prevent duplicate Magicline writes.
• chrome.storage.session: other short-lived workflow markers, follow-up contexts, open aggregator tasks, and diagnostics for the current browser session.
• Magicline page sessionStorage/localStorage: legacy migration or fallback only.

6. Recipients and external services

Magicline

Magicline Plus runs inside the existing Magicline web interface and uses the active browser session. Data displayed or saved in Magicline remains processed in the Magicline environment of the respective studio.

JARVIS backend

When central connectivity is enabled, the extension sends the JARVIS device token and studio-scoped settings, feature states, reminders/member snapshots, activity/audit data, and statistics snapshots to the internal JARVIS backend. JARVIS stores token metadata and required studio/workflow data in local SQLite databases. Administrative access is separately authenticated; backups are created consistently, restore-verified, and removed after the configured retention period.

Feedback via JARVIS and Telegram, with an optional Cloudflare Worker

Feedback content, a redacted page URL, and optional images are sent only to JARVIS with the studio-scoped device token. JARVIS validates the token, applies a rate limit, and relays the report either directly or with a server-side secret through the optional Cloudflare Worker to an internal Telegram support channel. The Worker is not an anonymous browser API. Users should review and mask member, bank, or other sensitive data in screenshots before sending them.

Cloudflare Pages for hosting this policy

This information page can be hosted on Cloudflare Pages. When the page is accessed, Cloudflare processes technically necessary access data such as IP address, request time, user agent, and requested URL to deliver the page and protect the service. Magicline Plus does not use its own analytics or advertising trackers on this page.

Chrome Web Store and browser vendors

Installation, updates, and extension management are handled by the relevant browser or store. Google, Microsoft, or other browser vendors may process their own technical data.

7. No sale, no ads, no remote code

• Magicline Plus does not sell user data.
• Magicline Plus does not use user data for creditworthiness or lending purposes.
• Magicline Plus does not include advertising or tracking SDKs.
• Magicline Plus does not load remote JavaScript or WebAssembly code for execution. Executable extension files are included in the extension package.

8. Legal bases

Where the GDPR applies, the legal bases may include Art. 6(1)(b) GDPR for providing the requested extension functions, Art. 6(1)(f) GDPR for legitimate interests in efficient studio workflows, security, error analysis, and abuse prevention, and Art. 6(1)(a) GDPR where users voluntarily provide feedback, attachments, or optional settings.

9. Retention and deletion

• Session data is generally needed only for the current browser session.
• Local reminders and settings remain stored until users change, reset, or remove the extension.
• JARVIS studio/workflow data remains until changed or deleted by the responsible operator; device tokens remain valid until revoked/deleted, while only token hashes are stored server-side.
• JARVIS SQLite backups are removed after 30 days by default unless the operator documents a different retention setting.
• SEPA PDF buffers are technically limited and only needed temporarily for signing/document workflows.
• Backup files are generated locally in the downloads folder and must be stored or deleted by users.
• Feedback reports are retained only as long as needed for support, error analysis, and traceability.

10. Data subject rights

Where the GDPR applies, data subjects may have rights to access, rectification, erasure, restriction of processing, data portability, and objection, as well as the right to lodge a complaint with a competent supervisory authority.

11. Changes

This privacy policy may be updated when functions, data flows, providers, or legal requirements change. The current version will be published on this page.