Privacy Policy

1. Who we are

Florence is a data visualization platform for journalists, designers, and clients. The Dataface is the organization responsible for Florence. Contact: hello@thedataface.com.

2. Information we collect

Depending on how you interact with Florence, we may collect:

• Account information — email address, name or display name, and authentication details when you sign in (for example via magic link).
• Workspace and project content — projects, frames, blocks, datasets, styles, comments, and other content you create or upload in the editor.
• Waitlist and invite data — email and related details you submit to request beta access, used only to manage invites.
• Feedback and support — messages you send, optional screenshots, browser/viewport context, and recent client errors so we can reproduce issues.
• Product analytics — usage events and diagnostics that help us understand product performance and improve Florence (for example via PostHog when configured).
• Technical data — IP address, device/browser type, and similar log data needed to operate and secure the Service.

3. Google user data (Google Sheets and Google Drive)

If you choose to connect a Google account to Florence for Connected Datasets, Florence requests access to Google user data through Google's OAuth consent flow. We access only the Google data you authorize, limited to what is needed to provide the feature.

What Google user data we access

• Google account identity needed to complete OAuth and associate the connection with your Florence project (for example basic account identifiers returned by Google during sign-in).
• Google Drive file access (via the drive.file scope) for spreadsheets you explicitly select with Google Picker. Florence does not list or browse your entire Drive; access is limited to files you choose (and files Florence creates, if any).
• Google Sheets content (via read-only Sheets scope) for the spreadsheet tabs you select — cell values and structure needed to build a tabular snapshot in Florence.

Florence uses Google Sheets in read-only mode and Google Drive's per-file scope so you can pick a spreadsheet. We do not write back to your Sheets or Drive files in the current Connected Datasets feature.

How we use Google user data

• To create and refresh a snapshot of a selected Sheet tab as a Florence Dataset.
• To let permitted project editors refresh that snapshot so charts and transforms stay current.
• To store encrypted OAuth tokens so the project can maintain the connection until you disconnect or tokens expire.
• To provide related product functionality you request (for example showing connection status and reconnect prompts).

We use Google user data only to provide or improve user-facing features of Florence. We do not sell Google user data. We do not use Google user data for advertising. We do not use Google Workspace APIs or Google user data to develop, improve, or train generalized or non-personalized AI and/or ML models.

4. How we use other information

We use non-Google account and product data to operate Florence: authenticate users, provide the editor and publishing features, send transactional emails (invites, magic links, notifications), improve reliability and UX, respond to feedback, and protect the Service against abuse.

5. Sharing, transfer, and disclosure

We do not sell personal information or Google user data. We may share information only as needed to provide the Service:

• Service providers that host or operate infrastructure on our behalf (for example database hosting, authentication, email delivery, analytics). These providers process data under our instructions and are not permitted to use Google user data for their own purposes.
• Project collaborators — people you invite to a Florence workspace or project can see project content, including dataset snapshots you have connected.
• Legal requirements — if required by law, regulation, or valid legal process, or to protect the rights, safety, and security of Florence, our users, or the public.

We do not transfer or disclose Google user data to third parties for purposes other than providing or improving Florence's user-facing features, except as required by law or with your direction.

6. Storage and security

We store Service data (including Connected Dataset snapshots and encrypted OAuth tokens) on our hosting providers. Security procedures are in place to protect the confidentiality of your data, including encryption in transit (HTTPS/TLS) and encryption of OAuth credentials at rest. Access to production systems is limited to authorized personnel. No method of transmission or storage is completely secure; we work to protect data but cannot guarantee absolute security.

7. Retention and deletion

We retain personal information and Google user data for as long as needed to provide the Service and fulfill the purposes in this policy, unless a longer period is required or permitted by law.

• Connected Google data — Sheet snapshots remain in your Florence project until you delete the dataset, detach the connection (which keeps a static snapshot and drops the live link), or delete the project. Encrypted OAuth tokens are kept while the connection is active and removed when you disconnect or the connection is replaced.
• Revoking Google access — you can revoke Florence's access at any time in your Google Account permissions. After revocation, Florence can no longer refresh from Google until you reconnect; existing snapshots in Florence remain until you delete them as described above.
• Account deletion requests — email hello@thedataface.com to request deletion of your Florence account and associated personal data. We will delete or anonymize data when the retention period ends or when you validly request deletion, subject to legal retention obligations.

8. Your choices

• Connect or disconnect Google Sheets / Drive integrations from within Florence (when available).
• Revoke Google OAuth access in your Google Account settings.
• Request access, correction, or deletion of your personal data by contacting us.
• Stop using Florence and request account closure.

9. Cookies

Florence uses a few cookies that the product needs in order to work. They are not advertising cookies, and Florence does not show a consent banner for them.

• Sign-in — keeps you signed in.
• Presentation password — when you enter a guest password, this browser is remembered for 7 days. The same cookie unlocks the presentation, the embed, and the project link.
• Guest comments — if you comment without an account, a cookie keeps the name you entered and lets you edit or delete your own comment.

Product analytics, when configured, is separate from these cookies and is not loaded on a public presentation or embed.

10. Children

Florence is not directed to children under 16, and we do not knowingly collect personal information from children under 16. If you believe a child has provided us personal information, contact us and we will take steps to delete it.

11. Changes to this policy

We may update this Privacy Policy from time to time. When we change how Florence uses Google user data, we will update this page and, where required, notify you and obtain any additional consent needed before using Google user data in a new way. The “Last updated” date at the top reflects the latest revision.

12. Contact

Questions about this Privacy Policy or Florence's data practices: hello@thedataface.com.