This policy explains what MyDraftDesk collects, why, who it goes to, and how to get rid of it. It is written to be read, not to be survived.
MyDraftDesk is operated by Blue Tide Exteriors LLC, 1780 E. Bert Kouns Industrial Loop, Suite 907, Shreveport, LA 71105, United States.
1. What we collect
Everything below is either something you typed into the app, a file you chose to attach, or something the app produced from those two.
| Category | What it is |
|---|---|
| Account | Your email address and an encrypted password hash. We never store your password in readable form. |
| Contractor profile | Company name, contractor license number and primary state, entered by you at setup so they can be printed on the plan set. |
| Project details | The six details you enter per project: category, project address, dimensions, structure options such as attachment and roof and post material, selected features, and finish choices. |
| Site information | Anything about the site that you enter or that the app researches for the address, including jurisdiction, applicable code references, zoning and setback findings. |
| Uploaded intake files | Photos, site plans and written estimates you attach to a project, held in our file storage under your account. |
| Generated plan sets | The fourteen sheets and their content, the structural assumptions, the code findings, the version history, and any PDF export. |
| Questions and answers | Clarifying questions the pipeline raised and the answers you gave, which are carried into later regenerations. |
| Revision requests | The plain-language changes you ask for, whether typed or dictated, kept as text against the project. |
| Review records | Whether a set was approved or returned for changes, by which architect account, and any redline notes written on it. |
We do not collect your location in the background, advertising identifiers, your contacts, or your browsing activity on other sites. We do not use tracking cookies for advertising, and we do not sell data to anyone, ever.
Note that a project address is a real property address, usually a customer's home. Treat it accordingly, and only enter what you are entitled to enter.
2. Why we collect it
- To run your account and keep your projects separate from every other contractor's.
- To generate the plan set. The project details and any files you attach are the input. Without them there is nothing to draft.
- To research the right code. The project address is what tells us which jurisdiction's requirements to look up.
- To put your details on the drawing. Company name, license number and state appear on the sheets because a plan set identifies who prepared it.
- To let an architect review it, which is the step between generation and a set being marked ready.
- To keep a version history, so you can compare a revised set against the one before it.
3. How a plan set is generated
When you submit a project, our server sends the following to Anthropic, our AI provider: the project details you entered, the contents of any photo, site plan or estimate you attached, and the project address so that code and zoning requirements can be researched for it. That research step uses web search.
Anthropic processes this to produce the per-sheet content, the assumptions and the code findings. A second, independent pass checks the result before anything is saved. Your email address, your password and your payment details are not sent to Anthropic.
Structural sizing is computed by a deterministic calculator on our server, not written by the AI model. Every figure it produces is stored as an assumption you can verify or correct, and a value you have corrected is used on later regenerations instead of being recomputed.
4. Voice input and biometric unlock
Dictation. When you dictate a revision, the transcription is performed by the speech recognition built into your own device and operating system. We receive the text it returns and store that text against the project. We do not store audio recordings, and depending on your device settings your operating system vendor may process the audio under their own privacy policy.
Biometric unlock. Face or fingerprint unlock is checked entirely on your device by the operating system. We never receive, see or store biometric data. All we receive is a yes or no from the device.
5. Architect review
Every generated set is submitted for review by a licensed architect before it is marked ready. That architect account can open the projects that were actually submitted for review, and only those. Access is enforced by rules in the database rather than by the app remembering to check, and the architect is given read access to the sheets, assumptions and code findings for the purpose of reviewing them.
6. Who we share data with
Only the service providers required to make the product work:
| Provider | What they handle |
|---|---|
| Supabase | Database, authentication, file storage for your uploads, and the server functions that run generation. |
| Anthropic | Generating sheet content and researching jurisdiction requirements, as described in section 3. |
| Your device vendor | Speech recognition for dictated revisions, and the biometric check, both handled on your device by its operating system. |
We may also disclose information where we are legally required to. We do not sell, rent or trade your data, and we do not share it for anyone else's advertising.
7. How long we keep it
- While your account is open, we keep your projects, uploads and generated sets so the product works and so your version history stays intact.
- When you delete a project, its details, uploads, generated sets and revision history are deleted with it.
- On account deletion, everything above is permanently deleted within 30 days. See the data deletion instructions.
- Backups may hold residual encrypted copies for a short period after deletion before being overwritten on the normal cycle.
8. Security and isolation
Every record carries the account it belongs to, and database-level row security rules make it structurally impossible for one contractor's account to read another's. That isolation is enforced by the database itself rather than by application code remembering to check.
Data is encrypted in transit. Generation runs on our servers, not on your phone. Uploaded files are stored in a bucket scoped to your account.
No system is perfectly secure and we will not claim otherwise. If a breach affects your data we will tell you.
9. Your rights
Wherever you live, we will honour these:
- Access. Ask for a copy of what we hold about you.
- Correction. Most of it you can edit directly in the app. Ask us for the rest.
- Deletion. See the data deletion instructions.
- Portability. Ask for your projects and generated sets in a machine-readable format.
- Object. Tell us to stop a particular processing activity.
Depending on where you live you may have additional rights under the GDPR, the UK GDPR, or state privacy laws such as the CCPA. Write to us and we will apply whichever gives you more protection. We respond within 30 days and we do not charge for it.
10. Children
MyDraftDesk is a professional tool for licensed contractors and is not directed at children. We do not knowingly collect data from anyone under 16. If you believe a child has given us data, contact us and we will delete it.
11. Changes to this policy
If we change this policy we will update the date at the top. For any change that materially affects how we handle your data, we will email you before it takes effect.
12. Contact
Privacy questions, requests or complaints: privacy@mydraftdesk.com. Anything else: hello@mydraftdesk.com.