A clear path
to your workspace.

Review unused starter additions for removal in Starter setup before removing the frontend. Server checks preserve edited or published workflows and pipelines with jobs or references. The process targets recorded kit additions rather than sweeping account records.

Preserve your local configuration and source edits. Preview frontend removal with node setup.mjs remove "/path/to/seedly" --dry-run. The automatic uninstaller uses a private restoration receipt and refuses to overwrite later edits. Keep that receipt private and out of public hosting or source exports. Removing frontend files does not remove account data or undeploy backend functions.

For an update, follow the documented removal/install process and reapply your preserved changes. A manually merged installation needs its own private change ledger and reviewed source rollback.

One contact-linked record is one patient relationship. It holds the patient label, an age band label, the preferred contact window, the referring office, the annual recall month with its state, contact attempts and last contact date, the review request state with the date it was asked for, cosmetic consults as a date and a decision with their follow-ups, packages as the office’s own commercial label with sessions total, used and booked plus the purchase and expiry dates and a recorded amount, and an editable front desk checklist. Referring offices are workspace records with their own revision guard, because a referring office is not a patient.

This is a front-desk and relationship workspace, not a medical record. It is not a HIPAA compliance product and does not make a practice HIPAA compliant. It is not an EHR, EMR or practice management system. It never stores diagnoses, conditions, lesion or mole descriptions, body areas, biopsy or pathology results, photographs or images, medications, product strengths, units injected, treatment settings, medical history, skin type classifications, insurance member or policy numbers, government identifiers or dates of birth; age is a band label at most and visit types are category labels only. Package and service labels are the office’s own commercial names, such as Series of 6 or Annual plan. The shared model refuses text that looks like a condition or finding word, a body area in anatomical phrasing, a drug, brand or device name, a dose or product strength, clinical vocabulary, an ICD-10 style code or an insurance member identifier, in every field, on the server as well as in the browser. Treat that as a guard against accidental entry rather than a guarantee. Clinical records stay in the practice’s own clinical system, and the kit gives no medical or skincare advice. Your practice decides what it records in its CRM and is responsible for its own privacy, security and regulatory obligations. There is no clinical system integration, no insurance or billing, no package payment processing or gift cards, no scheduling engine, no automated reminders or patient messaging, no patient portal and no payments. Recording a recall does not contact anybody and does not book anything, recording a session as used takes no payment, and the recorded package amount is a reference the office keeps for itself.

The kit’s original operational screens share the frame with full CRM modules from your own Seedly source. Existing account permissions, feature gates, and configured providers still determine access to those modules.