Your words stay under your control.

1. Scope and privacy roles

This notice applies to TRQR, the 1o.io website, organizer tools, attendee caption pages, support, billing, and related communications. TRQR is operated by Data.Flowers Inc., a New Hampshire corporation.

For account and service administration

Data.Flowers Inc. determines why and how organizer account, billing, security, support, and product analytics data is handled. In data-protection terms, Data.Flowers Inc. is the controller or business for that processing.

For event speech and transcripts

The organizer decides why an event is transcribed, who may speak, which languages are enabled, who receives the captions, and when transcript history is cleared. The organizer is normally the controller or business for that event content, and Data.Flowers Inc. processes it to provide TRQR. An organizer may request our data processing addendum at hello@1o.io.

If you are an attendee or speaker, the organizer is usually the first point of contact for a request about the content of that event. We will assist the organizer and will also respond when applicable law requires us to do so directly.

2. Data we handle

Organizers and applicants

• Name, email address, organization label, event notes, and support messages.
• Account identifiers, signed access-link metadata, event configuration, language choices, and translation context supplied by the organizer.
• Purchase, credit-balance, usage, receipt, and refund records. Stripe receives payment-card details; TRQR does not store full card numbers or card security codes.
• The organizer's network address when a capture session starts, plus operational session data such as timestamps, duration, language count, caption count, and error state.

Speakers and attendees

• Live speech sent through the organizer's microphone, including anything said near it.
• Source and translated transcript text, caption timing, and selected language.
• A random event-scoped listener identifier stored in the attendee's browser, connection timing, and basic network/request metadata. Attendees do not need an account.

Website and product analytics

Browser analytics is off until a visitor chooses “Allow analytics.” If enabled, TRQR records only an allowlisted set of page, application, listener, checkout, and error events. Autocapture, session replay, precise location collection, and form-content capture are disabled. Caption text, audio, names, email addresses, event names, event codes, raw organizer IDs, and microphone/device details are not permitted analytics properties.

TRQR uses local storage for the analytics choice and for limited product state such as an attendee's event-scoped listener identifier and caption progress. Essential signed organizer sessions use an HTTP-only cookie.

3. Audio and transcript control

Raw audio

TRQR streams microphone audio to a selected speech provider to create live captions. Data.Flowers Inc. does not record or retain that raw audio in the current service. Providers may process it transiently and may retain limited technical metadata under their own enterprise terms.

Final transcript text

TRQR stores finalized source and translated text so attendees can reconnect, join late, and review captions from the current event. The organizer controls this retention. Transcript text remains available until the organizer uses the product's clear-history control or asks us to delete it. There is no separate fixed transcript-retention period imposed by TRQR.

Clearing history removes the transcript from the active service and makes it unavailable to attendees. Limited residual copies may remain only where required for security, recovery, dispute handling, or law, and are isolated from ordinary product use until deleted.

Sensitive content

Speech may incidentally reveal health, political, religious, biometric, ethnic, sexual-orientation, union, or other sensitive information. TRQR does not ask speakers to provide these details and does not use speech to identify people, create voiceprints, advertise, or train Data.Flowers models. Organizers should avoid using TRQR for regulated or highly sensitive content unless they have completed the necessary legal, security, and contractual review.

4. Why we process data

We do not make decisions that produce legal or similarly significant effects about people using solely automated processing.

5. Service providers and recipients

We disclose data only as needed to operate TRQR, follow the organizer's instructions, complete a transaction, protect the service, comply with law, or complete a corporate transaction subject to appropriate safeguards. Providers are contractually restricted to their role where required by law.

Speech and translation provider pool

TRQR may use one or more of the providers below for language coverage, regional availability, quality, resilience, or customer requirements. Inclusion in this alphabetical list does not indicate whether Data.Flowers currently works with a provider. An event's content is not sent to every listed provider; a selected provider receives only the audio, transcript, context, language, and technical data needed for the requested function.

We will update this notice before sending event content to a materially different speech or translation provider. Where an organizer has contracted for subprocessor notice or approval, the applicable data processing addendum controls.

Other service providers

• Grafana Cloud for infrastructure metrics and alerting. We do not intentionally send transcript or raw audio content to Grafana.
• PostHog EU Cloud for opt-in, restricted product analytics and pseudonymized operational events.
• Resend for beta, invitation, service, and support email delivery.
• Stripe for hosted checkout, payment processing, receipts, fraud controls, and refunds.
• Infrastructure, hosting, security, professional advisers, auditors, and authorities when needed for the purposes described in this notice.

We do not sell personal information. We do not share it for cross-context behavioral advertising or use it for targeted advertising.

6. Retention

When data is no longer needed, we delete or anonymize it. If immediate deletion from a protected backup is not feasible, the data remains isolated from ordinary use until the backup is overwritten. A legal hold or binding legal duty may temporarily override a deletion schedule.

7. International data transfers

Data.Flowers Inc. is based in the United States, and TRQR and its providers may process data in the United States, the European Economic Area, the United Kingdom, or other countries where they operate. Those countries may have different data-protection laws.

Where European data-protection law requires a transfer safeguard, we use an applicable adequacy decision, the European Commission's Standard Contractual Clauses, the UK addendum, or another lawful mechanism, together with supplementary safeguards where appropriate. A copy of applicable transfer safeguards may be requested at hello@1o.io; confidential details may be redacted.

8. Your privacy rights

Depending on where you live and our role for the data, you may have rights to:

• know whether and how personal data is processed;
• access, correct, or delete personal data;
• receive a portable copy of data you provided;
• restrict or object to processing, or withdraw consent;
• opt out of sale, targeted advertising, or qualifying profiling;
• appeal a refusal and not be discriminated against for exercising a right.

TRQR does not currently sell personal data, share it for cross-context behavioral advertising, or conduct qualifying legal-effect profiling. Where applicable, we treat a recognized opt-out preference signal such as Global Privacy Control as a request to opt out of any processing to which the signal legally applies.

Email hello@1o.io with “Privacy request” in the subject. We may verify your identity and authority, and an authorized agent may submit a request with proof of authorization. We aim to respond within one month for GDPR requests and within the period required by applicable US state law. If we deny a request, you may appeal by replying to our decision.

People in the EEA or UK may complain to their local data protection authority. US residents may contact their state attorney general or other competent regulator. These rights are subject to statutory exceptions.

9. Security and incident handling

We use measures designed for the nature of the data, including encrypted transport, signed organizer links, restricted organizer sessions, access controls, secret separation, provider credential redaction, data minimization, and operational monitoring. No internet service can guarantee absolute security.

Organizers must protect signed setup links, restrict access to authorized people, use trusted devices and networks, and promptly tell us if a link or account may be compromised. We will notify affected parties and authorities of a personal-data breach when applicable law requires it.

10. Children

Organizer accounts and purchases are for adults who can enter a binding contract. TRQR is not directed to children and does not knowingly create attendee profiles for them. Because TRQR can be used at events attended by minors, the organizer must obtain any parental, school, venue, or other authorization required for live speech processing and must provide age-appropriate notice. Contact us if you believe a child's data was processed improperly.

11. Changes to this notice

We may update this notice as TRQR, its providers, or the law changes. We will change the effective date and, for material changes, provide a prominent notice or contact organizers when reasonably possible before the change takes effect. An organizer's signed agreement or data processing addendum may require additional notice.

12. Contact Data.Flowers Inc.

Email: hello@1o.io or info@data.flowers