Privacy

What this website collects

These statements describe this website as it is built, and can be verified from its source and from your browser’s network activity:

• This site loads no third-party scripts, fonts, images or stylesheets. Every asset is served from this domain.
• This site runs no advertising pixels, session recording, fingerprinting or cross-site tracking, and sets no cookies for those purposes.
• The only information you can submit is what you type into one of the two forms described below. There is no file upload anywhere on this site.
• Standard web server request logs may record information such as IP address, user agent and requested path, as is typical of any web server.

The talk-to-us form

The form at talk to us collects your name, work email and organization, and optionally your role, an approximate team size, and a message about what you are trying to improve.

We use it to reply to you and to understand whether Phibian fits your operation. It is not sold, and it is not used for advertising.

The Design Partner application

The application at design partners collects more, because it exists to evaluate fit: your organization’s name, website and type, your name, title, work email and optionally phone; the states you operate in and roughly how many locations, staff, field workers and people served each year; an optional revenue range; which EHR, payroll and scheduling systems you run; which areas create the most manual work; two open questions about your operation; and when you might realistically implement something like Phibian.

We use it for two purposes, both of which we will state plainly. The first is to evaluate whether your organization and Phibian are a good fit and to communicate with you about it. The second is to understand the market Phibian is built for, in aggregate: what these organizations run, where the manual work concentrates, and what to build next. Individual applications are read by a person. They are not sold, not shared with advertisers, and not used to make automated decisions about you.

Please do not submit patient, client or participant information. The application never asks for it, accepts no attachments, and the open text fields carry a reminder to describe the workflow rather than the people. If you believe something of that kind was submitted, tell us and we will delete it.

How submissions are stored

Both forms post to Phibian’s own servers on this domain and are stored in a database dedicated to website enquiries. That database is separate from the systems that hold customer operational data, and access to it is limited to the people who need to read and respond to enquiries.

When a submission arrives, a notification summarizing it is sent to Phibian by email so somebody sees it promptly. The stored record, not the email, is the one we work from.

How long we keep it

A talk-to-us message or a design-partner application is kept for 24 months from the day you submit it, and is then deleted. Deleted means deleted: the record is removed, not moved to an archive.

Two shorter periods sit inside that. The record of whether our notification email reached us is cleared after 90 days, since it only exists so we can notice a delivery problem. Technical information used to limit automated abuse of the forms is kept for 24 hours and then purged; it is never attached to your submission and cannot be traced back to it.

You can also ask us to delete your submission at any point before that, which is described next.

Correction and deletion

Write to privacy@phibian.io and ask us to correct or delete what you submitted. If you have a reference number from a confirmation page, including it helps us find your submission quickly, but it is not required. You do not need to give a reason, and asking will not affect how we treat your organization.

General enquiries about a submission can also go to info@phibian.io.

Contact

Questions about privacy can be sent to privacy@phibian.io. Security reports are welcome at security@phibian.io, and our current security posture is described on the security page.