Security, ownership and boundaries

Control should be clear before any website, account or family information enters the system.

FarewellOS is designed to own the reusable technology while the funeral home retains control of its identity, core accounts and business data.

The funeral home retains

Your identity, accounts and business data

Domain name and business identity
Google Business Profile and reviews
Individual Google Ads account and history
Original photographs and business-specific content
Customer and family information

FarewellOS owns and licenses

The reusable platform and operating method

Software, dashboards and reusable code
Website framework and sector templates
Automation, reports and quality-control systems
Call-handling playbooks and workflows
FarewellOS brand and platform intellectual property

Data principles

Collect less. Separate properly. Give access only for a defined reason.

Purpose limitation

Every integration and data field needs a clear operational purpose. Credentials are not collected merely because a connector exists.

Role-based access

People should see only the information required for their work. Multi-client systems must maintain strict separation between organisations.

Sensitive-data caution

The public FarewellOS website asks only for business-enquiry information and explicitly tells users not to submit family or deceased-person data.

Documented changes

Important configuration, campaign, routing and content changes should be recorded so responsibility does not disappear inside automation.

Third-party boundaries

Google, hosting, telephony, analytics and other partners retain their own service terms and responsibilities. FarewellOS does not disguise that dependency.

Data minimisation

The future operations platform should store only information that has a defined workflow, retention need and access owner.

Current security status

Honest about the stage of the platform.

The public website framework includes secure form handling, nonces, spam controls, rate limiting, basic security headers and an internal lead table. It is not yet presented as a certified enterprise funeral-management system.

Live Public website and business enquiry handlingPilot Partner-based call routing and summary workflowsRoadmap Multi-client operational and family-data modulesRequired before scale Formal policies, processor agreements, access model, retention controls, incident process and independent review

Recommended account structure

Managed access rather than unnecessary ownership transfer.

Asset	Recommended owner	FarewellOS role
Domain name	Funeral home	Technical management by authorised access
Google Business Profile	Funeral home	Manager access
Google Ads account	Funeral home	Administrative/manager access
Reviews	Remain with the business profile	Monitoring, response and request workflow
Website framework	FarewellOS	Licensed and managed for the client
Client-specific content and photographs	As agreed; normally funeral home for originals	Use within the service licence
Family/customer information	Funeral home as controller, subject to applicable law	Processor only where specifically contracted

Before any sensitive integration

Define the purpose, owner, access, retention and fallback.

The written proposal and data-processing documents must match the actual module being delivered.

Discuss the platform