1. Who we are
FragBook is a fragrance collection application for cataloging perfume and cologne bottles, tracking remaining volume and value, recording wear history, discovering fragrances, and preparing bottles for sale. In this policy, “FragBook,” “we,” “us,” and “our” refer to the FragBook application and its operator.
2. Information stored in your collection
Your personal collection is designed to remain on your device. Depending on how you use the app, this can include:
- Fragrance names, brands, concentrations, sizes, and bottle details.
- Remaining volume, purchase information, estimated value, favorites, notes, and personal scent tags.
- Wear history and private For Sale listings, including asking prices.
This personal collection data is stored locally by the app using device storage. It is not uploaded to a FragBook collection database and is not automatically synchronized to another phone. If you export a CSV, the export is created for you on the device and is handled by the sharing or file tools you choose.
3. Optional account information
You do not need an account to use FragBook. If you choose to create an account or sign in, the authentication service may receive account information such as your email address, name, authentication provider, and account or session identifiers. FragBook uses this information to establish and maintain your optional identity and sign-in session.
Signing in does not upload, back up, or sync your personal collection. We will update this policy before introducing cloud collection storage or cross-device synchronization.
4. Catalog discovery and technical information
When you search Discover or load catalog details, your search terms and catalog requests may be sent through the FragBook API to retrieve fragrance information and imagery. These requests are separate from your personal collection records.
The app and service may also process ordinary technical information needed to operate securely, such as request timestamps, IP address, device or browser characteristics, crash or error details, and authentication or security events. We do not use FragBook for targeted advertising, advertising identifiers, cross-app tracking, or sale of personal information.
5. Service providers
We use service providers to operate specific product functions:
- Clerk: optional authentication and session management. Clerk may process account and authentication information according to its privacy practices.
- Replit: hosting and operation of the public FragBook pages and API service.
- Open Beauty Facts, Fraganty, and Fragella: external fragrance catalog services used to provide discovery results, subject to their own terms and privacy practices. Search queries may be shared with the provider needed to fulfill a catalog request.
- Yora Fragrance House: first-party catalog content bundled with the app; it is not a personal collection storage service.
These providers receive only the information needed for their function. FragBook does not send your locally stored bottle records, notes, wear history, or private sale prices to catalog providers as part of ordinary discovery.
6. How information is used
Information is used to provide and secure FragBook, respond to catalog searches, authenticate optional accounts, maintain service reliability, diagnose errors, prevent abuse, comply with legal obligations, and communicate important service changes. We do not use personal collection records for advertising or sell them to third parties.
7. Storage and security
Data sent to FragBook services is transmitted using standard encrypted web connections where supported. Account sessions are handled by the authentication provider. Locally stored collection data is subject to the security of the device and operating system on which FragBook is installed. Use a device passcode and keep exported collection files in a secure location.
8. Your choices and rights
You can use FragBook without creating an account. You can edit or delete local collection records within the app, reset the local collection, and export your collection as CSV. If you create an account, Profile includes a Delete account control that permanently deletes the optional authentication account after confirmation and signs you out. Deleting the account does not delete the device-local collection; remove that collection separately or uninstall the app. You may also have rights to request access, correction, deletion, or other handling of account information under applicable law.
Deleting the app or clearing its app storage may remove locally stored collection data. Export your collection first if you need a backup. If the in-app account deletion control is unavailable, use the FragBook Support page to request help with account deletion.
9. Cookies and similar technologies
The public marketing, support, and privacy pages do not intentionally use advertising cookies or tracking pixels. The sign-in flow and service infrastructure may use technically necessary cookies or local storage for authentication, security, and session continuity.
10. Children
FragBook is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information through an account, please use the support route so the issue can be reviewed.
11. Changes to this policy
We may update this policy when the app’s data practices change or when legal requirements change. The effective date above will be updated when revisions are posted. Material changes will be presented in a clear way where appropriate.
12. Questions about privacy
For questions about this policy or a privacy request, please use the support route available from the FragBook app listing or visit the FragBook Support page. We will use the information you provide only to review and respond to the request.