Privacy
What IDOFO does with your information
Written to be accurate about the software rather than broad enough to cover anything. Where IDOFO cannot do something, it says so; where it will not promise something, it says that too.
1.What this covers
This policy describes how Boostlete LLC, a Wyoming limited liability company, which provides the IDOFO service handles information in the IDOFO service.
Two different kinds of information are involved, and keeping them apart is the point of the whole design. Your **account information** is about you as our customer. Your **business information** is what you put into the service — your records, your callers, your appointments — and that belongs to you. We hold it to run the service for you and for nothing else.
2.Information about you as a customer
To give you an account and bill you, we hold:
- Your name, email address and password, stored only as a scrypt hash.
- Your workspace name, account type, plan, and the roles of people you invite.
- Sign-in records, including the time and the network address, kept for security.
- Your subscription state and payment identifiers. Card details are handled by our payment provider and are never stored by us.
- Support conversations you start with us.
3.Information you put into the service
Held because the service cannot work without it:
- Your business details, hours, locations, services and prices.
- Contacts, appointments, tasks, messages and leads you or your assistant create.
- Calls: who called, when, how long, what was said as text, and what your assistant did about it.
- What you have told your assistant to say, and the questions and answers you have configured.
- Files you upload, and the content of a public page you publish.
- Where your organisation has told us it handles health information, records may include it. See "Health information" below.
4.What we do not hold
We do not store call audio. A call becomes text and the text is what is kept. No part of the service accepts an audio file, and there is nowhere for one to be stored.
Where speech recognition happens in a browser, the browser does not tell the page where it did the work, so we cannot tell you whether it stayed on the device. We say that rather than guessing.
We do not hold your card number, and we do not build a profile of you for advertising.
5.Why we hold it
To provide the service you asked for: answering calls, booking appointments, taking messages, and showing you the result.
To bill you, and to keep records of what was billed.
To keep accounts secure and to investigate abuse.
To meet a legal obligation.
To tell you about the service — a security notice, a change of terms, something that needs your attention. We do not sell your information and we do not share it for somebody else’s advertising.
6.How one customer is kept away from another
Every record belongs to exactly one workspace, and every read and write is bound to that workspace at the data layer rather than by a filter a developer has to remember. A query that tried to read across accounts is refused by the software, and that refusal is tested as an attack rather than assumed.
7.When our staff can see your account
Not by default. Entering a customer account needs a recorded, reasoned, expiring grant; it is read-only unless there is a reason for more; and both the grant and what was done under it appear in your own activity log. Our own reporting screens show totals, never a customer’s messages.
8.Outside services
Running the service means using other companies — to host it, to carry a telephone call, to send an email, to take a payment. The Subprocessors page lists them, what each one receives, and the agreements in place.
Where your organisation handles health information, a service that could receive it is refused by the software unless it is recorded as approved with a signed agreement. The product tells you which feature is unavailable as a result rather than failing quietly.
9.Referral and partner attribution
If you arrive through a partner or referral link we record that you did, using a random key in a first-party cookie. The cookie holds the key and nothing else — no name, no email, no reward amount — and editing it cannot change who earns anything, because every value that moves money is resolved on our side.
Attribution records are cleared from an account that asks to be erased. A partner’s own earnings record is kept, because deleting somebody’s earnings when a different party asks to be forgotten would be the wrong answer.
11.Getting your information out, and getting rid of it
You can export everything in your account at any time, in a machine-readable form, without asking us. Export and erasure are not behind a plan.
You can ask us to erase your account. Erasure walks the list of tables that hold customer data rather than a hand-written list, so a table added later cannot be quietly left behind.
Some things survive erasure, and we would rather say so than imply otherwise: records we are required by law to keep, security and audit records from which record content has been removed, and agreements we are still bound by and may have to produce. The Retention section says how long.
To make a request: privacy@idofo.com.
12.How long things are kept
Your information is kept while your account is open. You can set a shorter retention period for calls and messages, and where you do, older records are removed.
When an account closes, its information is removed on erasure or after the retention period you set.
Signed agreements — a Business Associate Agreement, for example — are kept as compliance records for as long as we may be required to produce them, separately from your access to the account. Audit and security records are kept for security purposes with record content redacted.
13.Security
The controls we operate are listed on the Security page. They are facts about the system, not promises about outcomes.
14.Health information
Most accounts never handle health information, and those accounts are never asked about it beyond one question. Where your organisation says it does, a Business Associate Agreement between your organisation and Boostlete LLC applies, and the additional controls it describes take effect.
Boostlete LLC does not claim to be HIPAA compliant.
15.Children
The service is not for children and we do not knowingly collect information from them. A caller who happens to be a child may appear in your records because they telephoned your business; that information is yours and is handled as any other record is.
16.Changes, and reaching a person
We will tell you before a material change to this policy takes effect. Each version has a number and a date.
Questions, or a request about your information: privacy@idofo.com.