DignitasOps Privacy Policy
Effective date: November 6, 2026
Last updated: November 7, 2026
This Privacy Policy explains current contact practices and planned information practices of DignitasOps, a DBA of DSHG Sonic ("DignitasOps," "we," "us" or "our"). Our marketing website is an unpublished preview and visitor analytics is not active. When you submit a form, we email your contact details, request and consent choice to hello@dignitasops.com. We don't keep a separate lead database; submissions stay in that company mailbox. The planned Service is being developed to include the website at dignitasops.com, the DignitasOps web application, driver app (a progressive web app), funeral home portal and online payment pages (together, the "Service"). Product capabilities, security controls and data collection described below are planned, not implemented or validated in this marketing project. Descriptions of future operation do not dilute the legal duties, rights or prohibitions in this Policy.
DignitasOps is based in Sarasota, Florida. You can reach us about privacy by email only, at hello@dignitasops.com.
The short version:
- We plan to collect only what is needed to run the future Service, keeping information about decedents to a minimum. When you submit a form, we email your contact details, request and consent choice to hello@dignitasops.com. We don't keep a separate lead database; submissions stay in that company mailbox.
- Our customers own the case information they put into the Service. When the planned Service is available, we will process it for them only under their instructions.
- We do not sell personal information, and we do not use case or decedent information for advertising.
- The planned Service is being designed not to store photos of a decedent. Planned camera capture is for documents only; decedent photography remains prohibited.
- The planned Service is being designed to encrypt customer data, separate each customer’s data and restrict visibility by role. These controls are not implemented or validated in this preview.
- You can ask us at any time to access, correct, export or delete your information.
1. What the Service does
The planned DignitasOps Service is being developed as software for licensed mortuary removal and transport companies, and for funeral homes that run their own vehicles. It is being developed to support call intake, dispatch, a driver app designed to work offline, chain-of-custody records, document capture, electronic signatures, pricing, invoicing, online payments, and exports to accounting software. The Service is in development and not yet available; future parts may be in pre-release or beta.
The Service is for businesses and their staff, not for the general public. We do not say the Service is HIPAA certified or SOC 2 certified, and we do not say it guarantees compliance with any law or regulation. We do not file death certificates, burial-transit permits or any other government filings for you.
2. Information we plan to collect
A. Website visitors and people who contact us
At an approved launch, we plan to use cookieless aggregate website analytics as described in Section 7. Emails you send directly may contain contact information. When you submit a form, we email your contact details, request and consent choice to hello@dignitasops.com. We don't keep a separate lead database; submissions stay in that company mailbox. Planned information categories include:
- Your name, work email, company name and role, if you give them to us
- The messages you send us
- Aggregate website traffic information, such as pages viewed, visit duration, traffic source, browser and device type. Lovable’s planned built-in analytics uses a same-domain script and endpoint and a visit-scoped random identifier discarded at visit end; it stores nothing in the visitor browser and does not create profiles or track across visits. This preview has no visitor analytics.
- Information from similar technology for planned cookieless website analytics, and planned app-specific cookies and device storage (see Section 7)
B. Account information
When the future Service becomes available, we plan to collect the following when a customer sets up an account or invites a user:
- Name, work email, phone number, company name and role
- Login credentials. The planned identity-provider design is intended to avoid readable password storage and require two-factor authentication; implementation has not been validated.
- Professional details the customer enters, such as license numbers, employee numbers, vehicle details and work schedules
- Records of sign-ins and account activity, kept for security
- Support requests and product feedback
C. Customer content, including case and decedent information
The planned Service is being developed to let customers and users enter operational information. This future "customer content" may include:
- Case details: call date and time, pickup and destination locations, the ordering funeral home or facility, crew and vehicle, status updates and notes
- Limited decedent details: name, and where the customer chooses to record them, date of birth, sex, time of death and facility identification band number
- Chain-of-custody records: who handed over or received custody, when and where, identification tag numbers, and any exceptions and how they were resolved
- People involved in a case: names, titles, organizations and license numbers of releasing staff, receiving staff, family members or other authorized persons, and on- site contact names and phone numbers
- Electronic signatures, together with the statement that was signed and the time it was signed
- Document images, such as release forms, permits and identification paperwork
- Billing records: rate cards, invoices, statements, payments and account balances between our customer and its funeral home customers
D. Location information
The planned Service is being developed to use location to show vehicles and record custody events, through two planned methods:
- Driver phones. The planned driver app is being designed to record phone location about every 30 seconds and at each status update only while it is open and a case is active, not in the background, and to stop at shift end. Drivers would be able to decline location access while retaining non-location functionality. This behavior is not implemented or validated.
- Vehicle GPS. If a customer connects a vehicle tracking provider (for example, Linxup), we plan to receive vehicle positions from that provider once that integration is implemented.
E. Payment information
Future payments are planned to be processed by Stripe; this preview has no payments. When a funeral home pays an invoice by bank transfer (ACH) or card, the planned payment flow would have Stripe collect bank or card details directly. The planned Service is being designed not to store full card numbers or bank account numbers. We plan to receive payment status, amount, date, method type and last four digits. Future subscription billing is also planned through Stripe; implementation is not validated.
F. Device and app information
For the future Service, we plan to collect device type, operating system, app version, error reports and performance data. The planned offline driver app would store some data on the phone (see Section 7); none of this app collection or storage is implemented in this preview.
3. Information we do not collect
- No photos of decedents. The planned driver camera is being designed to open only from a "Capture document" action, show "Documents only. Never photograph the decedent.", and hide flagged improper images promptly with permanent deletion available. These controls are not implemented or validated; the prohibition remains.
- No medical details. The planned Service is not intended to request cause of death, diagnoses, medications or other medical information. Customers must not enter it in free-text fields.
- No Social Security numbers, and no financial information about next of kin.
- No full payment card or bank account numbers (the planned payment flow would have Stripe hold these).
- No sensitive information in texts or alerts. Planned text messages, error reports and system logs are being designed to omit decedent names and details. Planned texts would use a case number and a secure login-required link; implementation is not validated.
4. How we use information
For the future Service, we plan to use information to:
- Provide the Service: dispatch calls, record custody events, price and send invoices, take payments and sync to accounting software
- Create and manage accounts, verify identity, and enforce role-based access
- Send service messages, such as call offers, alerts, invoices, payment receipts and account notices
- Send marketing emails to people who signed up for them (each one has an unsubscribe link)
- Answer support requests and fix problems
- Keep the Service secure: detect fraud and abuse, monitor for attacks, keep audit logs, and investigate incidents
- Improve the Service, using aggregated or de-identified information about how the Service is used
- Meet legal obligations, enforce our terms, and protect the rights and safety of our customers, users and the public
We do not use customer content, including case or decedent information, for advertising or marketing. We do not use it to train general-purpose artificial intelligence models.
5. Our role for customer content
When the Service is available, our customers will decide what customer content goes into it and how it is used. For future customer content, the customer is the controller (or the business, under some state laws), and DignitasOps is its processor or service provider.
| Role | Who |
|---|---|
| Will control future customer content, including case and decedent information | The customer (the removal company or funeral home that holds the account) |
| Will process future customer content on the customer's behalf | DignitasOps, a DBA of DSHG Sonic |
| Will control website, waitlist and account information when those collection features are available | DignitasOps, a DBA of DSHG Sonic |
When the planned Service is available, we will process customer content only to provide the Service, under the customer's instructions and our agreement with them, and as this Policy describes. Customers are responsible for having a lawful basis to enter information into the Service, for giving any notices that are required, and for how they use records once exported from the Service.
If you are a family member, funeral home staff member or other person named in a customer's records, please send privacy requests to that customer. If you write to us, we will pass your request to the customer, or tell you which customer to contact.
6. How we share information
We do not sell personal information. We do not share it for cross-context behavioral advertising. We share information only as follows.
Service providers (subprocessors). The providers below are planned for the future Service, subject to appropriate contracts limiting data use; their integrations and controls are not validated in this preview. Lovable is the marketing preview host and intended future marketing host, not a replacement for the planned AWS customer platform:
| Provider | Current marketing hosting or planned future role |
|---|---|
| Lovable | Marketing preview hosting and delivery of internal lead-notification emails to hello@dignitasops.com; planned future marketing-site hosting and built-in cookieless aggregate visitor analytics, active only after approved publication. No customer-platform migration is implied. |
| Amazon Web Services | Planned customer-platform hosting, databases, file storage, encryption keys, sign-in and two-factor authentication, email delivery, and maps and routing |
| Stripe | Planned payment processing and subscription billing |
| Twilio | Planned text message delivery |
| Sentry | Planned customer-platform error monitoring, intended to remove personal information; configuration not validated |
Services a customer chooses to connect. If a customer uses a future implemented connection, we plan to send it only the information needed for that connection. Examples include QuickBooks Online (invoices and payments), a vehicle GPS provider such as Linxup, Gusto (driver hours) and Slack (alerts). The customer controls these connections. That service's own privacy policy then applies to what it receives.
Within a customer's own business relationships. The planned funeral home portal is being developed to let invited funeral homes see only their own cases’ status, documents and invoices, subject to customer sharing settings. The portal and controls are not yet implemented.
Legal and safety reasons. We may disclose information if we believe in good faith that the law, a court order or legal process requires it, or to protect the rights, property or safety of DignitasOps, our customers or others. Where the law allows, we will tell the affected customer first.
Business transfers. If DignitasOps is involved in a merger, acquisition, financing or sale of assets, information may transfer to the new owner. The protections in this Policy, or ones at least as protective, will continue to apply.
Professional advisors, such as lawyers and accountants, who have a duty of confidentiality.
With your permission, in any other case.
7. Cookies and storage on your device
This unpublished marketing preview does not collect visitor analytics. At an approved launch, we plan to use Lovable’s built-in aggregate analytics to measure page views, visit duration and traffic sources. It uses similar technology—a same-domain script and endpoint—not analytics cookies. Nothing is stored in the visitor browser; a visit-scoped random identifier is discarded at visit end. It does not create visitor profiles or track across visits. Notice dismissal in this preview is memory-only, with no cookie or browser storage. We do not use advertising trackers or session replay.
Future app-specific technologies are planned to:
- Make the app work and keep it secure
- Maintain signed-in sessions
- Support offline work as described below
When app cookies are implemented, you can block or delete them in your browser settings, though some app features may not work without them. The planned website analytics does not track across visits regardless of "Do Not Track" signals. Where state law requires it, we will honor Global Privacy Control signals as opt-out requests.
In the future web app, secure session cookies are planned to keep users signed in and protect against forged requests. These controls are not implemented or validated in the marketing preview. Advertising cookies are not planned for the web app.
The planned driver app is being designed to store some case data on the phone for offline work, encrypt it, and erase it on logout or administrative access removal. These storage and erasure controls are not implemented or validated in this preview.
8. Text messages and email
Text messages. The future Service is planned to send texts to drivers and staff, such as call offers, deadline alerts and on-call alerts, and status updates to customers who choose them. When these messages are available, message and data rates may apply; recipients can reply STOP to opt out or HELP for help. These reply controls are planned, not implemented or validated. Planned texts must not include a decedent’s name; that control is not yet validated.
Email. For the future Service, we plan to send service emails, such as invoices, receipts, security alerts and account notices, which you can't opt out of while you use the Service. Future marketing emails must go only to people who signed up, and each must have an unsubscribe link; email delivery and unsubscribe controls are not connected in this preview. You can also unsubscribe by emailing hello@dignitasops.com.
9. Location information
Planned location functionality is being designed to help dispatchers choose a nearby crew and attach time and place to custody records. Phone collection is planned only while the app is open and a case is active (Section 2D). The planned retention design deletes raw position history after 90 days and retains attached locations as long as their custody or status record. Collection, deletion and retention controls are not implemented or validated.
10. Security
The planned Service is being developed to include administrative, technical and physical safeguards designed to protect information. None of the following product controls is implemented or validated in this marketing preview:
- Encryption in transit (TLS) and at rest, plus extra field-level encryption for decedent names, dates of birth and identification band numbers
- Separation of each customer's data from every other customer's data, enforced in the database
- Role-based access, so each user sees only what their role allows, and required two- factor authentication
- Custody records, signatures and audit logs that can't be edited after the fact; corrections are added as new records
- Audit logs of sign-ins, changes, exports and document downloads
- Encrypted backups, tested restores, security monitoring and a web application firewall
- Limited staff access to production systems, and no real customer data in testing environments
No method of storing or sending data is completely secure, so we can't guarantee absolute security. If we learn of a security breach that affects personal information, we will notify affected customers, individuals and regulators as the law requires.
11. How long we keep information
The product retention settings and controls described in this section are planned, not yet implemented or validated in this marketing preview.
We keep information only as long as we need it for the purposes in this Policy, unless the law requires longer. Florida-licensed independent removal services must retain all signed contracts for at least two years under Fla. Admin. Code R. 69K-24.022(5). Other records may be subject to different or longer requirements. Customers choose retention periods suited to their records, operations, contractual obligations and legal holds, within the product settings below. The 2-year signed-records minimum is a DignitasOps product setting, not a statement that all records share that legal retention period. After a subscription ends, customers have 90 days to export their records. After that, DignitasOps may delete them; keeping records beyond that period is the customer's responsibility, including keeping exported copies for as long as their obligations require.
| Information | How long we keep it |
|---|---|
| Waitlist and marketing contacts | Until you unsubscribe or ask us to delete it. After that, we keep only your email address on a do-not-contact list, so we can honor your opt-out. |
| Signed records (custody records, signatures, signed documents) | As the customer sets, with a DignitasOps product minimum of 2 years. This setting does not mean that all records share the same legal retention period. |
| Invoices, payments and other financial records | 7 years by default; the customer can change this |
| Audit logs | At least as long as the records they relate to |
| Raw location history | 90 days |
| Account information | While the account is open, plus 90 days after it closes |
| Customer content after a subscription ends | Read-only for 90 days so the customer can export it; after that, DignitasOps may delete it, subject to any legal hold or law requiring DignitasOps to retain it. Keeping records beyond the export period is the customer's responsibility. |
| Backups | Overwritten on a rolling 35-day cycle |
| Security and system logs | Up to 12 months, unless needed to investigate an incident |
| Support emails | Up to 3 years after the issue is closed |
If records are under a legal hold, we keep them until the hold is lifted. Customers get notice before scheduled deletions of their records.
12. Your rights and choices
Requests about your information. Depending on where you live, you may have the right to:
- Know what personal information we have about you, and get a copy
- Correct information that is wrong
- Delete your information
- Get your information in a portable format
- Opt out of the sale of personal information, targeted advertising, or certain profiling (we don't do any of these)
- Not be treated differently for using these rights
To make a request, email hello@dignitasops.com with "Privacy Request" in the subject line. We will confirm we received it, and we may ask for information to verify your identity before we act on it. We aim to respond within 45 days, and we will tell you if we need more time where the law allows. You may use an authorized agent; we may ask for proof that the agent can act for you.
If we decline your request, we will explain why. You can appeal by replying to our decision with "Appeal" in the subject line.
Customer content. For information in a customer's records, we will usually send your request to that customer, because they control that information (see Section 5). The planned Service is being developed to let customer owners and administrators export or correct records; those controls are not implemented.
California residents. California law gives you the rights listed above. Sections 2, 4 and 6 describe planned Service collection, use and sharing, not a claim that this unbuilt platform has collected or shared those categories in the past 12 months. When you submit a form, we email your contact details, request and consent choice to hello@dignitasops.com. We don't keep a separate lead database; submissions stay in that company mailbox. Unpublished visitor analytics is inactive. We have not sold personal information, shared it for cross-context behavioral advertising, or used sensitive personal information to infer characteristics about anyone.
Florida and other states. Florida, Virginia, Colorado, Texas and other states have privacy laws that may give you similar rights. We will honor requests as the law that applies to you requires.
Marketing and texts. Use the unsubscribe link in any marketing email, or reply STOP to any text.
13. Health information
Funeral homes and removal services generally are not HIPAA covered entities solely because they perform funeral or removal services. HIPAA applicability depends on the entity's activities and relationships. Under 45 CFR 164.512(g)(2), covered entities may disclose protected health information to funeral directors, consistent with applicable law, as necessary to carry out their duties concerning the decedent. This permission does not automatically authorize disclosure to every removal provider or software vendor. DignitasOps is not currently offered for uses requiring it to act as a HIPAA business associate. Do not use the Service for such a purpose unless we first confirm support and execute any required agreement. DignitasOps protects information with encryption, role-based access and audit logs. The Service is not designed to store medical records. Please do not enter medical information into the Service.
14. Children
The Service is for businesses and adults. It is not directed to anyone under 18, and we do not knowingly collect personal information from children through our website or app. If you believe a child has given us personal information, email hello@dignitasops.com and we will delete it.
15. Users outside the United States
The planned Service is intended for businesses in the United States. Customer-platform information storage and processing are planned in the United States, subject to validation before launch; this is not a verified claim about the marketing host’s processing locations. If you use the Service from another country, you understand that your information will be transferred to the United States, where privacy laws may differ from those in your country.
16. Changes to this Policy
We may update this Policy from time to time. We will post the new version on this page and change the effective date at the top. If we make a material change, we will also notify account owners by email or in the Service before it takes effect. If you keep using the Service after the effective date, the updated Policy applies to you, to the extent the law allows.
17. Contact us
We handle all privacy questions and requests by email.
Email: hello@dignitasops.com
Company: DignitasOps, a DBA of DSHG Sonic
Location: Sarasota, Florida