Swiftly Privacy Policy
Version: 2026-09-19
Status: DRAFT — requires review by counsel before it is shown to any real
user.
The short version
- We collect what a property recovery requires: the property, the damage, who
is working on it, and what they did.
- Everyone on a recovery sees what their role entitles them to see. Not more.
- We do not sell your personal information. We do publish statistics with
no people or properties in them.
- Your insurance policy documents are visible only to you.
- Location sharing by a crew member is theirs to switch on, lasts for the
drive, and is deleted on arrival.
1. What we collect
You give us:
- Identity and contact details: name, email, phone (if you give one).
- The property: address, type, and where in it the damage is.
- The loss: what happened, when you noticed, how urgent it is.
- Documentation: photographs, moisture and other readings, notes, files.
- Messages you send on a record.
- Insurance details you choose to enter, and policy documents you upload.
Generated as work happens:
- Milestone and commitment timestamps — when each step started and finished.
- What failed: the component, and where known its manufacturer, model and age.
- Which organization did what, and whether commitments were met.
- Delivery records for notifications we send you.
Collected automatically:
- Basic technical data needed to operate and secure the service (IP address,
device and browser type, timestamps).
- Crew location only while a crew member has switched sharing on — see §5.
2. Why we use it
3. Who can see what
Access is decided by role on each specific record, and enforced by the
platform rather than by convention:
- Property owner / manager: everything on their own recovery, in plain
language.
- Restoration provider: the records they are dispatched to or working on.
- Carrier: the records they are a participant on.
- Financial partner: the records they are a participant on.
- Swiftly Operations: platform-wide visibility, for support, dispute
handling, and keeping the system honest.
Policy documents you upload are an exception: they are visible only to
your own organization, never to the provider, the carrier, or other
participants. When we explain a policy back to you, the explanation is
produced in isolation — the part of our system that reads your policy is never
given information about your damage, and the part that describes your damage
is never given your policy. We describe what your policy says and what the
crew found. We do not tell you whether something is covered; that is your
insurer's decision.
4. Who we share it with
- Other participants on the same record, per §3.
- Service providers that run parts of our infrastructure (hosting, email
and message delivery, object storage, error monitoring), under contract,
only to provide those services.
- When you ask us to — for example sharing your Recovery Record with a
buyer, an agent, or your insurer.
- When the law requires it, or to protect someone's safety.
- In a business transfer, if Swiftly is acquired or merges — in which case
this policy continues to apply until you are told otherwise.
**We do not sell your personal information, and we do not share it with data
brokers or advertisers.**
5. Crew location
Location sharing exists so a property owner can see that help is genuinely on
the way. It is bound by rules the platform enforces, not by our good manners:
- It is switched on by the person carrying the phone, per shift or per
job — never by their employer.
- Before the device asks for permission, we explain in plain words what will
be shared and with whom.
- Only the latest position is stored. There is no trail and no history.
- On-duty presence, shown before a provider is assigned, is **snapped to a
coarse grid** and carries no name, no identifier, and no organization.
- It stops and is deleted on arrival, when sharing is switched off, or at
a hard time cap — whichever comes first.
6. Aggregated and de-identified information
We create statistics and research from what we observe — for example how often
a class of water heater fails, how long losses of a given type take to
respond to in a region, or how much provider capacity a storm consumed. We may
publish or license these.
Before any such use, information identifying a person or a specific property
is removed. We do not attempt to re-identify it, and recipients are not
permitted to either. If we cannot produce a given statistic without a
meaningful risk of identifying someone, we do not produce it.
7. Your choices and rights
Depending on where you live, you may have the right to:
- Access the personal information we hold about you.
- Correct it if it is wrong.
- Delete it, subject to the limits in §8.
- Object to or limit certain uses.
- Take it with you in a portable form.
- Opt out of "sale" or "sharing" as those terms are defined by your state's
law — though as stated above, we do not sell personal information.
You will not be treated differently for exercising any of these rights.
To make a request: privacy@swiftly-solutions.com. We will verify who you
are before acting, and respond within the time your law requires.
8. Deletion, and its limits
You can ask us to delete your personal information, and we will — but some of
it cannot simply disappear, and it is fairer to say so than to promise
otherwise:
- A shared recovery record belongs to more than one participant. We can
remove your personal details from it, but the record of what happened to the
property, and what was done about it, remains for the others who need it.
- Records we are required to keep by law, or that we need to resolve a
dispute or enforce our agreements, are retained for that purpose.
- Append-only event history is not rewritten. Where personal information
must be removed from it, we redact rather than delete the event itself,
because an unbroken history is what makes the record worth anything.
9. How long we keep things
Active recoveries are retained while they are active, and afterwards for the
period needed for evidence, warranty and dispute purposes. Crew location is
deleted on arrival (§5). Specific retention periods are pending legal advice
and will be published here before the service is generally available.
10. Security
Files are stored in object storage and delivered through short-lived links,
never from application servers. Access is role-based and denied by default.
Every material change writes an auditable event. No system is perfectly
secure, and we will tell you promptly if something happens that affects you.
11. Children
Swiftly is not intended for anyone under 18, and we do not knowingly collect
information from children.
12. Changes
We will post changes here with a new version date. If a change materially
affects how we use your information, we will tell you before it takes effect.
13. Contact
privacy@swiftly-solutions.com