Privacy Policy
1. Data we collect and why
- From the sender: name and email, to identify who sent the rose, send purchase and management emails, and notify you if delivery fails.
- About the recipient: name and the contact you choose to provide (email, WhatsApp number, or Instagram profile). We use email for automatic delivery; the other options help the sender share the gift.
- Rose content: text, color, language, and an optional voice recording, to save and display the gift. The microphone is used only when you choose to record and grant browser permission. We do not use recordings for biometric identification.
- Order and delivery records: draft and rose identifiers, access links, payment status, transaction identifiers, amounts and currencies (including a converted payment when applicable), timestamps, email delivery attempts and failures, and the rose's first opening. These support fulfilment, delivery status, customer support, and payment reconciliation. Stripe handles card and billing information; we do not store card details.
- Security data: the application uses a keyed hash of the IP address and request timestamps to limit abuse. This is a pseudonymous identifier, not a guarantee of anonymity. Hosting and other providers also receive IP addresses and technical connection data when handling requests.
We process purchase and gift data to provide the contracted service, order records to meet applicable legal obligations and exercise rights, and necessary recipient, security, usage, and diagnostic data for legitimate interests in delivering gifts, preventing abuse, and improving reliability, subject to the LGPD and your rights. Where processing requires consent, it must be obtained separately for that purpose; accepting the Terms alone is not consent to all processing. Avoid including sensitive personal information in a gift.
2. Usage statistics and error monitoring
When enabled, PostHog measures page visits, referral sources, creation and checkout steps, payment and release, first opening, voice additions, sharing options, and page performance. Events include delivery method, payment amounts and currencies where relevant, and technical performance information. Random draft and rose identifiers can link events to each other and to our order records: these data are pseudonymous, not anonymous.
Events also carry the browser, operating system, and device type, and the page address with private links removed. Our analytics events exclude names, message content, voice recordings, contact details, and private access tokens. PostHog runs in memory, with its cookies, persistent browser storage, automatic interaction capture, and session replay disabled in the app.
When enabled, Sentry receives error reports, warning and error logs, sampled performance traces, and navigation recordings around errors to help diagnose failures. Recordings mask text and input fields and block media and the 3D canvas. The app removes private link tokens and payment-session identifiers from reported URLs and disables collection of user information, cookies, request headers and bodies, and local variables. Technical browser, device, navigation, and timing information can still be processed. Provider-side IP handling and retention depend on the provider and project settings.
The site saves the selected language and the identifier of the draft in progress in your browser's local storage so you can resume. Sentry can also keep a diagnostic session identifier and timing information in browser session storage. You can clear these through your browser; clearing the draft identifier may prevent you from resuming an unfinished rose. Stripe's checkout may use its own cookies and storage under its privacy policy.
3. How long we keep data
- Unpaid drafts expire about 24 hours after their last change. Scheduled cleanup removes expired drafts and their voice files, normally on the next hourly run; interruptions can delay cleanup.
- Paid roses and associated draft and order records remain stored to keep the gift and management link working. There is no automatic expiry for paid roses. You can request removal (section 6).
- Rate-limit hashes and timestamps older than two hours are removed by scheduled hourly cleanup, normally within about three hours.
- Payment, support, and delivery records may need to remain after a gift is removed to meet legal obligations, reconcile payments, or resolve disputes. Removal does not necessarily erase all order records immediately.
- Analytics, diagnostics, infrastructure logs, and backups follow the retention settings of the relevant providers. Contact us for information about the periods that apply to your data or to request deletion where available under the LGPD.
4. Who helps us run the service
Providers receive data relevant to their role:
- Stripe: checkout, payment processing, conversion where offered, and refunds; it also processes payment data under its own privacy rules.
- Supabase: the database, stored rose content and voice files, and backend functions.
- Resend: transactional emails, recipient addresses, email content and links, and delivery status.
- PostHog: the usage and performance data described in section 2.
- Sentry: the diagnostics and masked error recordings described in section 2.
- Cloudflare: website delivery, network security, and technical request data.
We may also disclose information when required by law or a competent authority, or when necessary to exercise rights. A private rose is accessible to anyone who has its recipient link or QR code, including people to whom it is forwarded. The management link grants access to management features. Keep these links confidential; they do not provide end-to-end encryption against the service operator.
5. International transfer
Providers may process data outside Brazil, including in the United States. Destinations depend on the provider, account region, and supporting infrastructure. International transfers are subject to the LGPD's requirements; this policy does not replace the applicable transfer mechanism. Contact [email protected] for information about destinations, providers, and the safeguards applicable to your data.
6. Your rights
Under the LGPD, you may request confirmation and access, correction, information about sharing, portability as regulated, and anonymization, blocking, or deletion where applicable. You may revoke consent when it is the legal basis, ask about the consequences of refusing it, and object to unlawful processing. You may also petition the ANPD or consumer protection bodies.
Send requests, including requests to remove a rose, to [email protected]. We may ask for proportionate information to verify your identity and protect another person's data. Requests are handled without charge within the applicable legal deadlines. Some records may be retained where the law permits or requires it; we will explain any limitation that applies.
7. Sharing to stories
Story images and videos are generated on your device; the generated file is not uploaded to our servers. If you download or share it, the chosen app or platform may process it under its own rules. Including a message reveals that content; including a link or QR code lets viewers access and forward the rose.
8. Who the controller is
The controller of the personal data processed by Send a Rose is Construtora Florence LTDA. Privacy contact: [email protected].