1. Overview
Scentic provides a fragrance workspace: catalog exploration, collection tools, retailer price research, optional accounts, community features, and messaging. You can browse much of the site without signing in. This policy describes information the service processes when you visit or use an account.
2. Information you provide
- Sign-in. With Google, we receive your verified email, name when provided, and a stable Google account identifier. With email and password, we store your email and a password hash; email confirmation may be required before an account is fully active.
- Profile. Signed-in members may add a community profile (display name, bio, location, website, scent preferences, optional profile photo). Other signed-in members may view profiles according to connection, block, and visibility rules.
- Collection and settings. Signed-in members can sync private collection data, wishlists, favorites, and related workspace state to the account.
- Community. You may submit written reviews, posts, impressions, and similar content associated with your member profile.
- Messages. When the product allows messaging between two accounts, we store message text and optional image attachments. Attachments are stored in object storage; only participants in the conversation can access them through the service.
- Fragrance requests. Signed-in users may send catalog requests (and optional photos) to the site operator’s private creator inbox, including account identifiers tied to the submission.
- Passkeys. You may optionally register a passkey for an in-site “verified account” marker. We store public key data needed to verify the passkey, not biometric data from your device.
- Resale research. Marketplace features let you keep private notes about resale listings (platform, URLs, prices, fill estimates, notes). Saving these to your account stores them with your member data; some shortlists may also remain in your browser until synced or cleared.
3. Information collected automatically
- Cookies. Signed-in sessions use an HttpOnly session cookie (about 30 days unless ended earlier). A separate device cookie can help recognize browsers for optional security notices. Google sign-in uses short-lived cookies during the OAuth flow that are cleared after callback.
- Security and reliability. We record data needed to prevent abuse and secure accounts, such as rate-limit counters, sign-in events using hashed identifiers, and device labels derived from browser information. Where the hosting platform provides country or region metadata, approximate location may be stored for security notices—not a precise street address.
- Local storage. Your browser may store appearance choices, guest mode, and some workspace shortcuts locally. That data stays on your device unless you sign in and sync account-backed features.
4. How we use information
- Operate sign-in, sessions, and account security (including ending sessions after password changes, email changes, or deletion).
- Provide features you choose: collection sync, community, messaging, medals, optional verification marker, and retailer research tools you initiate.
- Send transactional email when outbound email is enabled (for example verification, password reset, security notices).
- Run operator-only creator tools (private request inbox and optional automated review aids) for the configured site owner account.
- Maintain service reliability and enforce limits on abusive traffic.
5. Sharing and service providers
We rely on providers to host and run the product. Depending on which features you use, data may be processed by:
- Cloudflare (application hosting, database, file storage, and request delivery).
- Google (if you choose Google sign-in).
- Resend (if transactional email is configured).
- OpenAI (only for optional creator workflows initiated by the site operator, not for routine member chat).
- YouTube (embedded review players, when you view that content).
- Supabase (only if that alternate sign-in path is enabled in a given deployment; production is intended to use Google directly).
Retailer, marketplace, and social links open third-party sites under their own policies.
6. Advertising and affiliate links
The application does not run an in-app ad network. Outbound retailer links open external merchants in a separate tab. Product research may link to Amazon and other stores using standard product or search URLs; the implementation does not add affiliate tracking parameters in application code. A sponsor placeholder area exists in the interface without a connected live ad service.
7. Your choices and account deletion
Account settings may let you change security preferences, sign out of other devices, and request account deletion. Deletion requires confirmation for email-based accounts. After deletion, sessions are invalidated and account-linked data is removed or retained only as needed to prevent reuse of old sign-in credentials, with best-effort removal of stored files such as profile or message attachments.
8. Retention in the product
- Session cookies are issued for about 30 days unless you sign out or security settings invalidate them sooner.
- Email links for verification, reset, and similar flows expire after the time limits built into those flows.
- We do not describe a separate offline backup or log retention schedule on this page; operational retention outside the application is addressed in internal operator review.
9. Security
Signed-in requests are checked against account state in the database. Cryptographic secrets and provider keys are kept in server configuration, not in public source code. No method of transmission or storage is perfectly secure; please use a strong, unique password if you use email sign-in.
10. Changes
We may update this policy when the product changes. The effective date above will change when a new version is posted.
11. Contact
Privacy questions: raphael@scentic.io.