Skip to content
Dayscent
  • How it works
  • Friends
  • Dayscent+
  • FAQ
  • Help
  • Support
@dayscent.app

Privacy policy

This page covers the Dayscent app and the dayscent.app website.

Effective date: November 20, 2026

Dayscent (“the app”, “we”, “us”) is a fragrance companion app: you keep your collection, and it suggests a scent for today based on the weather, the occasion and your preferences. Dayscent is run by Calvix Ventures LLC, a Kansas limited liability company, which is the data controller (the company responsible for how your personal data is used). Dayscent was run by its founder, Carlos Alvarez, until November 13, 2026, when it moved to Calvix Ventures LLC; your data and settings carried over unchanged. Questions: [email protected].

This policy explains what we collect, why, who else receives it, how long we keep it and what you can do about it. We don’t sell your personal information, we don’t share it for advertising, we don’t track you across other companies’ apps or websites, and we don’t show ads.

Dayscent is currently available outside the EU/EEA, the UK and Switzerland. The app is not offered in those regions, and our app-store territory settings exclude them. Before a European launch, we will add the relevant legal-basis, transfer and supervisory-authority information. The website and waitlist may still be visited from Europe; section 10 explains your choices.

1. What we collect

Before you sign up

  • The intro asks about your taste and the bottles you own. Your answers stay on your phone until you create an account; then they are saved to your profile and collection. The bottle search in the intro uses a small list built into the app, so those search words stay on your phone. Bottle images, app updates, crash reports and usage analytics can still contact the services described below before you sign up.

Your account

  • Your email address, used to send you a 6-digit sign-in code. Or, if you choose Sign in with Apple or Google, the account details they give us: your email (with Apple this can be a private relay address). Apple may also give us your name on the first authorization. Google also passes your name and profile picture link. We may use your first name from either provider to fill your display name if it is empty; you can change or remove it. We do not use the provider picture.
  • If you sign in with Apple, a sign-in token from Apple, kept only so we can cancel your Apple sign-in when you delete your account.
  • Basic sign-in records kept by our hosting provider, such as when your account was created, when you last signed in, and technical logs with your IP address and device/app type.
  • Sign-in codes and session tokens, used to verify you and keep you signed in. Session tokens are also saved on your phone and removed on sign-out.
  • We never show your email to other users, and nobody can search for you by email or phone number.

Your profile and settings

  • Optional display name, username, bio, profile photo and signature scent.
  • Your preferences and switches: temperature unit, scent families you like, notes to avoid, pick variety, and the sharing choices described in section 3.
  • If you turn on the streak board, your time zone, so your week is counted correctly.
  • Badges the app works out from your own activity.
  • When you accepted the Community Terms, and records of suspensions or restrictions used to enforce them.

Your collection

  • The fragrances you add, when you added them, favorites, ratings and personal notes.
  • Optional photos of your own bottles, and fragrances you add by hand.
  • Bottles a shelf scan found that you saved for later (“Found on your shelf”).

What you wear and share

  • Your wear log: which fragrance, when, the occasion you picked, and a small weather snapshot (temperature, humidity and a condition such as “rain”). It does not include your location.
  • Your answers to “How did it go?” after a wear, “Good pick” / “Not today”, and compliment counts. Answers can include whether you were inside or outside and the time of day. They only tune your own suggestions.
  • If you use Friends: posts you choose to share (with an optional caption, rating, tag, time, weather, occasion, poll or your own photo), Help me pick polls, poll votes, reactions, comments and replies, who viewed your posts, your friends and friend requests, people you blocked, suggestions you dismissed, and the in-app notifications (the bell) about this activity.
  • GIF comments: a comment can include one GIF. We store which provider it came from (KLIPY or GIPHY), the GIF’s id and size, and for KLIPY GIFs its image address. For GIPHY GIFs we store no image address; the app asks GIPHY for the picture each time the comment is shown.
  • Reports you make, and reports other people make about you (see section 6).

Your location (if you allow it) or typed city

  • The app asks for your location only while you use it, to get the weather. On your phone, we round your position to about 1 km. To get the weather, the app sends our server an even rougher area (about 11 km) and your time zone. The request uses your sign-in session for access and rate limits. We cache weather for that rough area for up to about 6 hours, without an account link. We don’t save a location history. The finer rounded position and city name stay on your phone.
  • Before you sign up: if you allow location during setup, the app sends our server the same rough area (about 11 km) and your time zone so your first pick can use today’s real weather. It isn’t linked to any account, and we keep it only in our weather cache, which is cleared within about 6 hours. To stop abuse, we briefly use a scrambled version of your internet address and delete it within 30 minutes.
  • If you type a city instead, that city and its rounded coordinates are saved on your phone for weather-based picks.

Photos and camera (only if you allow it)

  • You can take a photo in the app’s own camera or pick one from your library, for your profile, a bottle, a post or a shelf scan. A bottle photo can be used to find one fragrance; a shelf photo can find several. Only the photo you choose is uploaded, and the app re-saves it first, which removes hidden photo data such as the GPS position.
  • The “studio” bottle cut-out is made on your phone; the photo isn’t sent anywhere for it. On Android, Google ML Kit sends technical diagnostics about this feature (section 4).
  • Scanning a bottle barcode or a friend’s QR code (iPhone and Android): the code is read on your phone by Google ML Kit’s barcode scanner, which is built into the app. The camera picture isn’t sent anywhere for this. ML Kit does send Google technical diagnostics (section 4), separately from the “Share usage data” switch. If you scan a bottle barcode, the number is then looked up on our server to find the fragrance; a friend’s QR code is handled in the app.
  • Photos other people can see are checked automatically for inappropriate content before they are saved (section 4, Google Cloud Vision).
  • To load faster, we also keep a smaller copy of photos you add to your collection or posts. It has the same privacy settings as the original and is deleted when the original is.

Photograph one bottle and Scan your shelf

  • When you photograph a bottle or scan your shelf (with the camera or a photo from your library), the photo is sent once to our AI provider to read the labels (section 4, Anthropic). The app tells you this, naming Anthropic, before your first scan. We don’t store the photo. We keep a scan log (whether it worked, how many bottles it found, which AI model read it and how much processing it used, and when), linked to your account, for 35 days to count your scans, and a running count of your successful shelf scans for the free lifetime allowance. Separately, we keep the labels it read: brand, name, concentration and reading confidence, along with catalog matches, lookup counts and results. These label records are deleted after 7 days or when the scan or account is deleted (section 5). When you open the review, an unmatched label may be looked up automatically in our catalog and search cache, then through our fragrance database provider (section 4). This can happen without a separate web-search tap. The provider receives brand, name and concentration search words from our server, not your photo. You choose which bottles to add or save for later.

Dayscent+ (subscriptions)

  • If you subscribe, Apple or Google handle the payment. We and RevenueCat receive your subscription status (plan, trial, renewal and expiry dates) and the store’s receipt. We never see your card details.

Notifications

  • If friend notifications are on: your phone’s push token, your notification settings (including quiet hours and your time zone) and a short record of what was sent. On iPhone they’re on by default if you already allowed notifications for Dayscent, unless you said not now or turned them off.
  • The morning pick and the trial reminder are scheduled on your phone; nothing is sent to us. On iPhone the morning pick is on by default if you already allowed notifications for Dayscent, unless you turned it off.

Home-screen widget

  • If you add the widget, the app saves a small snapshot on your phone for it: today’s pick, the weather, tomorrow’s plan, and up to 4 friends who posted today (first name, scent and a small photo). The widget never connects to our servers.

Feedback

  • If you send feedback from the app: your message, its type, the screen name, app version, and device type and system version, plus a screenshot of the screen only if you switch that on.

Other information on your phone

  • Scentle guesses and game progress, your close-friends selection, display preferences, reminder settings, and records of picks, tips or celebrations you have already seen. Some of these local records use your account id or friends’ ids. They are separate from the server data above. A Scentle result can also be included in usage analytics when that is enabled.

Usage data and crash reports

  • Usage analytics (the “Share usage data” switch, section 7): which screens and features are used, as a fixed list of events such as “finished the intro” or “shared a post”. No names, emails, messages, photos, fragrance names or location. It’s linked to a random id before you sign up and to your account’s random id after, never your email. Earlier events can then be linked to your account too. The SDK also sends device model, operating system, app version, language and time zone. The default uses your phone’s region setting: off until you turn it on for the EU/EEA, the UK and Switzerland, and when the region is unknown; on by default elsewhere. Your saved choice overrides that default. These account-linked records are not anonymous. First steps: if usage sharing is on, during your first visit to Today, until your first wear, we also record which steps you saw, which buttons you tapped, and roughly where you tapped (one of 32 large zones, never exact positions, text or screenshots), to find confusing first steps. These records are kept and deleted like the rest of your usage analytics.
  • Crash reports: when the app hits an error, a report with the error details, the device and app version, and your account’s random id. We remove emails, codes, locations, photos and messages from these reports before they’re sent.

Searches and AI lookups

  • The words you type when searching for a fragrance, and the name, brand and concentration you type when you ask for an AI lookup. If you tap Look it up on an unmatched bottle saved from a scan, its detected brand/name may also be searched. In the scan’s Find it picker, a web search of the text you enter runs only when you tap Search the web.
  • The words you type in the GIF search for comments, and your phone’s language and region setting, sent to our GIF providers to find GIFs (section 4). Opening the GIF picker without typing loads trending GIFs.

We don’t upload your precise location or collect your contacts, microphone recordings, health data, payment card details or advertising identifiers. Your phone may provide a more precise position, which the app rounds before using it for weather.

2. Why we use it

What we do Data used
Create your account and sign you in (email, Apple or Google) Email, sign-in records, Apple/Google sign-in details
Keep your collection, wears, photos and settings, and sync them to your phone Profile, collection, wear log, photos, preferences
Suggest today’s scent and learn from your check-ins Collection, preferences, wear history, check-ins, weather for your rough area
Look up fragrance details (typed search, automatic scan review, saved bottles and AI) and read your shelf photo Search words; detected or typed name, brand and concentration; the shelf photo
Friends: show your profile, posts, photos, polls, comments and replies to the people described in section 3 Username, display name, bio, profile photo, posts
Check photos others can see for inappropriate content The photo
Find and show GIFs in comments GIF search words, language and region setting, GIF ids and sizes; for GIPHY also the GIPHY install id
Keep the community safe: filters, reports, blocks, suspensions Reports and their copies, blocks, acceptance and moderation records
Sell and provide Dayscent+ Subscription status, store receipts
Send friend notifications Push token, settings, names of the friends involved, the bottle involved
Understand which features are used, to improve the app Usage analytics
Find and fix crashes Crash reports
Prevent abuse and control costs (daily limits, rate limits) Account id, counts of actions, IP address in logs
Answer support messages and feedback Your message, account id, technical details and optional screenshot
Handle privacy requests Contact details, request and verification information
Deliver and protect this website IP address, request details and short-lived abuse counters
Send the launch email you requested Waitlist email and sign-up date
Provide app updates, the Android bottle cutout and the barcode and QR scanner App, device and SDK diagnostics described in section 4
Remember device preferences and optional game progress Local settings, friend selections, game and seen-state records

How picks work: the app scores fragrances on your phone using weather, occasion, preferences, ratings and recent wears. Check-ins help personalize those scores. This is profiling for scent suggestions; it does not make decisions with legal or similarly significant effects on you. You can choose any scent, change your preferences or turn off check-in prompts.

3. Who can see your information

  • Only you: your email, personal notes, preferences, private hand-added fragrance entries, check-ins, compliments, found bottles, feedback, subscription status, and any wear you didn’t share. Your collection and bottle photos too, unless “Show my collection to friends” is on. It’s on by default for accounts created from November 5, 2026, and off for older accounts unless you turned it on. You can change it in Profile at any time. Fragrance names and pictures you choose to include in a shared post are visible with that post.
  • Dayscent, only to fix the catalog: if you add a bottle by hand and attach a photo of it, we may look at that photo only to identify the bottle and correct our shared catalog (its name, details and catalog picture). We never copy your photo into the catalog, post it or share it. This applies to photos attached from November 8, 2026.
  • Anyone you share a Story card with: if you share your pick as a Story card, it shows the bottle and the weather. It also shows your city name, unless you turn off “Show my city” before sharing. It never shows your exact location. Once shared, Dayscent can’t take it back from that other app.
  • Anyone signed in to Dayscent who has a username: can find you by the start of your username or by your display name. Results show your username and display name. They can open your basic profile to send a friend request.
  • People you sent a friend request to (while it’s waiting for an answer): your username, display name and profile photo. They can’t see your posts until they accept.
  • Your friends (requests accepted): your username, display name, bio, profile photo and badges; your shared posts, including any photo you added (in the Feed for 7 days, and older shared posts on your profile), your Help me pick polls (7 days), and the reactions, comments and replies on them. If “Show my collection to friends” is on: your collection (names, brands, photos and ratings, never your notes). If you turn them on: your friends list and your streak board. If you or they block the other, all of this stops.
  • Friends of your friends: your username, display name and photo while you appear in a friend’s friends list (each person chooses whether their friends list is shown).
  • People you may know: someone who shares a mutual friend with you may see your profile photo in suggestions for up to 30 days, unless either of you blocked the other or the suggestion was dismissed.
  • Post authors see who viewed their post and, for polls, who voted (other viewers see voters only if the author turned that on).
  • Anyone who sees your phone: friend notifications can show who it’s from and which bottle on the Lock Screen, never what was said. The widget can show your pick and friends’ first names; on iPhone you can hide names on the Lock Screen in Settings.
  • Us (the app owner): we can access stored data to run the service, handle reports and feedback, and answer your requests.

4. Services we use (third parties)

We use these services for the purposes below. Hosting and app service providers process data for us; store accounts, sign-in providers and separate websites also have their own privacy policies.

  • Supabase (hosting, database, file storage, sign-in and server functions). Stores the data described above in the United States (US East).
  • Resend (email delivery): receives your email address and the sign-in code so it can deliver the email.
  • Apple and Google (sign-in): confirm who you are when you choose Sign in with Apple or Google. If a stored Apple sign-in token exists, we revoke it before deleting your account. If Apple cannot be reached, deletion waits and asks you to try again. An already-invalid token counts as done. Older accounts without a stored token can still be deleted.
  • Anthropic (AI):
    • AI lookups: when you tap “Look it up with AI”, our server sends Anthropic only the fragrance name, brand and concentration you typed. If the AI doesn’t know the fragrance, it may search the web using those same words. The result is saved as a shared fragrance entry that other users can find, so please don’t type personal information into those fields. The lookup screen includes a line naming Anthropic before you send the request.
    • Photograph one bottle and Scan your shelf: our server sends Anthropic only the bottle or shelf photo you take or choose from your library and our instructions, to read the bottle labels. We don’t store the photo. The app shows a one-time notice naming Anthropic before your first scan.
    • Under Anthropic’s commercial terms, it deletes what we send (and its answers) within 30 days, unless the content is flagged for breaking its usage policy (inputs and answers may then be kept up to 2 years, and safety classification scores up to 7 years) or the law requires longer. By default it doesn’t use commercial API inputs or answers to train its models. See Anthropic’s retention policy.
    • We never send Anthropic your email, username, account id, collection, location or device information.
  • Google Cloud Vision (photo safety check): before a profile, bottle or post photo is published, our server sends the image to Google, which returns only whether it looks inappropriate. No account details are sent. Google processes the image in memory without saving it to disk, and doesn’t use it to train its Vision models.
  • Google ML Kit / Google Play services (Android bottle cutouts; the barcode scanner is the next entry): downloads the segmentation model and sends Google device and installation identifiers, device and app information, feature usage, performance and error diagnostics, and image format and size. The photo and cutout stay on your phone. These SDK diagnostics are separate from the PostHog “Share usage data” switch. See Google’s ML Kit data disclosure.
  • Google ML Kit Barcode Scanning (barcode and friend QR scanner, iPhone and Android): reads the code on your phone with a model built into the app. ML Kit does not send the camera picture or the code’s content to Google. (A bottle barcode number is then sent to our server to find the fragrance, as described in section 1; a friend QR code opens that friend’s invite.) ML Kit sends Google device and app information, a per-installation identifier that isn’t meant to identify you, feature performance numbers, and event and error diagnostics. These SDK diagnostics are separate from the PostHog “Share usage data” switch. See Google’s ML Kit data disclosure for iPhone and for Android.
  • Fragrance database provider: our server sends brand, name and concentration search words from a typed web search, an eligible unmatched label during scan review, or a saved bottle when you tap Look it up. The scan review lookup can run automatically. A Search the web tap in the scan’s Find it picker sends the text you entered. We do not send the provider the shelf photo, your account id, email, location, device information or your phone’s IP address. Results can add fragrance facts to our shared catalog; normalized search words and resulting catalog ids are kept in a cache without your account id, and paid-lookup usage records are kept as described in section 5. Please keep personal information out of fragrance search fields.
  • Bottle image hosts: some fragrance bottle pictures load from image addresses provided by our fragrance database provider, so those hosts see your IP address and request/device details, like any website image.
  • Apple Weather (WeatherKit): our server asks Apple for the weather in your rough area (about 11 km) and time zone. Apple sees our server, not your phone or your account.
  • Apple and Google (city name): your phone’s built-in location service turns your rounded location into a city name.
  • Expo (EAS Update and notifications): your phone checks Expo for app updates (Expo sees your IP address, platform, app and runtime version). If friend notifications are on, Expo receives your push token, short notification text and the post or poll id needed to open the right screen. It passes the notification to Apple Push Notification service or Google Firebase Cloud Messaging, which deliver it to your phone.
  • RevenueCat (subscriptions): manages Dayscent+ purchases. It receives your account’s random id, the store receipt and subscription status, and IP address, device and app information from its software. When you delete your account in the app, we request deletion of your customer record at RevenueCat (section 5). If you ask us by email instead, we delete it by hand. Apple App Store and Google Play handle payments and store accounts under their own policies.
  • PostHog (usage analytics, US): which screens and features are used, plus device and app details, with no names, emails or messages, linked to your account’s random id, never your email. We use it to improve Dayscent, not for cross-context behavioral advertising. Session replay is off. PostHog doesn’t keep your IP address. You can change your choice in Settings → Usage data → Share usage data. The device-region defaults are explained in section 1.
  • Sentry (crash reports, United States): error details, device and app version, and your account’s random id, with personal details removed before sending. Sentry doesn’t store your IP address.
  • Cloudflare (our website, dayscent.app): hosts this policy and our other web pages (see section 10).
  • GIF providers (GIPHY and KLIPY): we use two GIF providers for GIF search in comments. Right now we use GIPHY first and KLIPY when GIPHY has no results or isn’t available; this order may change. Each page of results comes from one provider.
  • KLIPY (GIF provider): when you search for a GIF or open the GIF picker and KLIPY is used, our server sends KLIPY your search words (or a request for trending GIFs) and your phone’s language and region setting. KLIPY sees our server, not your phone, and we don’t send it your account id, email or location. The GIF pictures themselves load from KLIPY’s servers, so KLIPY sees your IP address and request/device details when a GIF is shown, like any website image. See KLIPY’s privacy policy.
  • GIPHY (GIF provider): GIPHY requires its search to run from your phone, so when GIPHY is used the app contacts GIPHY directly. GIPHY receives your search words (or a request for trending GIFs), your phone’s language setting, your IP address and device/app details. When a GIPHY GIF is shown in a comment, your phone asks GIPHY for it by its id and loads the picture from GIPHY. As GIPHY requires, the app also tells GIPHY when one of its GIFs is shown in the picker, tapped or sent. Searches and these notices carry a random install id the app creates only for GIPHY. It isn’t linked to your account, email or name, we don’t store it on our servers, and signing out doesn’t reset it. GIPHY handles this information under its own policy, for example to deliver GIFs and improve its service. See GIPHY’s privacy policy.

Our public feature board at dayscent.featurebase.app is a separate website run by Featurebase. The app only opens it and does not send your Dayscent account details. Featurebase receives normal browser request details, including your IP address, and anything you provide there. Posts are public and covered by Featurebase’s privacy policy.

We may also disclose information if the law requires it, to protect people’s safety (for example, reporting child safety concerns or threats to the authorities), or if the app is transferred to a new owner (who must keep this policy’s promises).

5. How long we keep it

The periods below apply to our live service. An automatic daily clean-up job removes expired database records, old feedback screenshots, report evidence photos and unlinked uploads after their retention periods end. Provider logs and backups have separate retention.

Data How long we keep it
Your account data: profile, collection, photos, wears and your “How did it go?” answers, posts and post photos, polls, comments, replies, reactions, friends, blocks, preferences, badges, bottles saved from a shelf scan, your Dayscent+ status Until you delete it or delete your account
Post views: who viewed your posts Deleted 30 days after the view by a job that runs every five minutes, or sooner if the post or viewer’s account is deleted
Feedback you send from the app Messages: 1 year, or sooner if you delete your account. Screenshots are removed by the automatic daily clean-up job after 1 year; uploads left by a failed send are removed by that job after 1 day. Account deletion removes them sooner
Photos you replace Removed after the new one is saved, except photos kept as report evidence
Notifications (the bell) 90 days
Push notification records: what was sent to your phone 7 days. A phone’s push token: until you sign out or delete your account, or 90 days after the app was last used on that phone, or 30 days after your phone stopped accepting them
Search cache: search words, without any account link 30 days
Shelf-scan detected labels and lookup results: linked to your account and the scan; for each detected bottle its number in the scan, the brand, name and concentration we read, how confident the reading was, the catalog match, result and up to 3 suggested catalog entries, how many web and AI lookups it used, the lookup version and when it was resolved Deleted by the automatic daily clean-up job when the scan is older than 7 days, or sooner if the scan or account is deleted
Saved-bottle lookup state: linked to the saved bottle it belongs to (and through it to your account); for a bottle saved from a scan, the time of its last web lookup, the result, the result time, the matching catalog entry and up to 3 suggested entries, and the lookup version Kept with that saved bottle until you add/remove it or delete your account. A final answer is reused for 7 days; a paid attempt is limited to once per bottle per 7 days, except when a referenced catalog entry is deleted
Web lookup in progress: the search words (brand and name, normalized), your account, a request id and the start time, kept so the same lookup is not paid for twice at once Removed when the lookup ends; an unfinished one is cleared after its three-minute lease lapses, and anything older than 1 day by the automatic daily clean-up job, or when you delete your account
Suggestion history (“People you may know”, who was shown to whom) 30 days, and always deleted when either account is deleted
Usage records for daily limits (which action and when, never what you wrote) 35 days. When you delete your account, they lose their link to it
Shelf-scan log (whether a scan worked, how many bottles it found, and which AI model read it and how much processing it used; Dayscent does not store the photo) 35 days. Separately, we keep a count of your successful shelf scans for the free lifetime allowance. It holds no photo or scan result and is deleted when you delete your account.
Weather answers (an area of about 11 km, no account link) Up to about 6 hours
Reports Until reviewed, then 365 days after review, even if an account involved is deleted. Report deletion waits if an evidence photo is still awaiting removal (see section 6)
Reported profile or post photos While a report is open, then removed by the automatic daily clean-up job 30 days after it closes. Removal runs in daily batches; failures or a backlog can delay it
Deletion follow-up notes (account id, service, error code and time) PostHog/RevenueCat notes: until resolved, at most 365 days. Apple revocation failure notes: 180 days; they contain no sign-in token. A pending note for a deletion that stopped before removing the account expires after 1 day
Temporary AI lookup and deletion-attempt records Normally removed when the operation ends; abandoned records removed after 1 day
Usage analytics (PostHog) 1 year. When you delete your account in the app, we request removal of your person record and events; provider processing happens in the background. Failed requests are retried automatically for up to 30 days. Requests that still fail are flagged and handled manually by us. If you ask us by email instead, we delete these records by hand
Crash reports (Sentry) Up to 90 days, including after account deletion. They can still carry the deleted account’s random id; they are not anonymous
Subscription records When you delete your account in the app, we request removal of your RevenueCat customer record. Failed requests are retried automatically for up to 30 days. Requests that still fail are flagged and handled manually by us. If you ask us by email instead, we delete these records by hand. Apple and Google keep purchase records under their own policies
Hosting logs and backups Supabase database backups are kept for 7 days, then roll off. Server logs are kept for up to 7 days
Account-deletion correspondence Emails are kept for up to 1 year to show that the request was handled

Deleting your account does not immediately erase existing Anthropic inputs or safety records, Google SDK diagnostics, GIF provider records, or providers’ delivery and security logs. Anthropic’s periods are in section 4. Resend and Cloudflare logs, Expo/APNs/FCM delivery logs and ML Kit diagnostics are kept under each provider’s own retention policies: Resend, Cloudflare, Expo, Apple (APNs), Google (FCM and ML Kit), KLIPY and GIPHY. Contact us to ask about these records or request deletion. Shared fragrance facts added through an AI lookup remain in the catalog after their account link is removed. Fragrance facts added through a fragrance database lookup (a typed web search, scan review or Look it up) are stored without an account link and also remain in the shared catalog.

On your phone: the offline copy is kept up to 7 days (weather up to 3 hours). Sign-out and in-app account deletion clear account-linked data stored on that phone, including offline data, setup progress, the widget snapshot, cached pictures, Scentle progress and close-friends selections. After deletion by email, this happens when the app reconnects and detects that your session is no longer valid. Device-only settings such as theme and the marker that remembers the intro was seen stay. You can also uninstall the app to remove its local data.

6. Reports and moderation

  • Automatic photo check: profile, bottle and post photos are checked by Google Cloud Vision before anyone else can see them. A photo that looks inappropriate is not published and its pending upload is removed.
  • Reports: you can report a person, a comment, a Help me pick poll or a post photo. We save a copy of what was reported (for example the username, display name, bio, the post’s fragrance name, the comment or the poll) and the reason, so we can review it even if it’s later changed. If a reported comment has a GIF, the copy also keeps the GIF’s provider, id and size, and for KLIPY GIFs its image address. Like other report copies, it is kept until reviewed, then 365 days after review (section 5). A report can also preserve the person’s profile photo. Reported profile and post photos stay while a report is open and are removed by the automatic daily clean-up job 30 days after it closes, even if the original photo was replaced or the account was deleted. Removal runs in daily batches; failures or a backlog can delay it (section 5).
  • Automatic hiding and review: three distinct reporters with open reports hide the reported wear post, post photo, comment or reply, Help me pick poll, or profile photo until review. Profile-level reports wait for our review and do not automatically suspend Friends access. Repeated reports by one person count once. Authors see “Hidden while we review reports” and cannot re-share a held post. We can restore or remove it after review. We aim to review reports within 24 hours.
  • The reported person isn’t told who reported them. Reports are only visible to us. When an account is deleted, its live account link is removed, but the copy may still identify someone. It stays until the report is deleted (365 days after review, subject to the evidence cleanup described in section 5).

7. Your rights and choices

Everyone can:

  • See and correct most of your data in the app (profile, collection, preferences).
  • Delete content in the app (collection items, photos, wears, posts, post photos, polls, comments, reactions, found bottles).
  • Delete your account in the app: Profile → Settings (menu at the top) → Account → Delete account. Or email us: see dayscent.app/delete-account. When you delete your account in the app, we request deletion of your usage analytics at PostHog and your customer record at RevenueCat. Failed requests are retried automatically for up to 30 days. Requests that still fail are flagged and handled manually by us. If you ask us by email instead, we delete these records by hand. Deleting your account doesn’t cancel a Dayscent+ subscription: the app warns you and links to Manage subscription, so cancel it in your App Store or Google Play subscriptions first.
  • Turn off usage analytics (Settings → Usage data → Share usage data; the regional defaults are explained in section 1), friend notifications and each kind of them (Settings → Notifications), “Share what I wear”, “Show my collection to friends”, “Show my friends list to friends”, comments on your posts, the streak board, “Ask how it went after wears”, and on iPhone “Hide names on the Lock Screen”.
  • Turn off location, photo, camera and notification access in your phone settings.
  • Ask us for a copy of your data, or anything else about your data, at [email protected]. We may need proportionate information to confirm you own the account. We aim to answer within 30 days and follow any deadline required by the law that applies to your request. If an extension is allowed and needed, we’ll explain why. Account deletion by email has the 30-day timetable on our deletion page.

California (CCPA/CPRA): the categories we collect are identifiers (email, account and device ids, IP addresses), personal records such as names, purchase information, internet/app activity, approximate location, photos and other user content, and inferences such as scent preferences. Sign-in credentials and session tokens are sensitive personal information used to authenticate you. Sources are you, your device, your activity, sign-in and payment providers, and other users who interact with or report you. Sections 1–6 explain the purposes, recipients and retention for each. We disclose the relevant categories to the services in section 4 and to other users only as described in section 3.

Where the CCPA/CPRA applies, California residents have the right to know what personal information we collect, use and disclose; to access it; to correct it; to delete it; and not to be discriminated against for using these rights. We don’t sell or share personal information for cross-context behavioral advertising, and we don’t use sensitive personal information to infer characteristics. Do Not Sell or Share: we do not sell personal information or share it for cross-context behavioral advertising, including information about users under 16. PostHog is product analytics, not an advertising service. There is no sale or advertising sharing to opt out of, including when your browser sends a Global Privacy Control signal. You can still turn off “Share usage data”. You can use an authorized agent; we may ask for proof of authority and verify the request. Email [email protected].

Other US states: several states (for example Virginia, Colorado, Connecticut, Utah and Texas) give similar rights. We honor the same requests for everyone in the US, and you can appeal a decision by replying to our answer.

Wherever you live: you can ask for access, correction, deletion or a portable copy of your data, ask us to limit its use, or object to a use. You can withdraw consent at any time without affecting earlier lawful use, and appeal a decision by replying to our answer. We honor applicable privacy rights. Optional permissions and analytics are not required to keep an account; a feature that needs a permission may not work without it.

Where data is processed: Calvix Ventures LLC operates in the US. Supabase hosts app data in US East; PostHog and Sentry process it in the US. Other services above may process data in the US and other countries, where privacy laws can differ from yours.

8. Children

You must be at least 13 to use Dayscent, including Friends (or older where the law requires it; see the Community Terms). We don’t knowingly collect data from children under 13. If you believe a child under 13 has an account, email [email protected] and we’ll delete it.

9. Security

  • Your data is protected by row-level security in the database: each account can only read and change its own rows; friends only see what the rules above allow.
  • Uploaded profile, bottle and post photos are in private storage, reachable through short-lived signed links: the app requests links to other people’s photos that expire within 5 minutes, and links to your own photos that expire within 60 minutes. They wait in a private area until the safety check passes. Feedback screenshots are also private; shelf photos are processed without being saved by Dayscent.
  • Secret keys for our providers stay on our servers, never in the app. The app does contain GIPHY’s public app key, because GIPHY requires its search to run from the app; that key gives no access to your data.
  • Connections use HTTPS. Paid lookups, scans, photo checks and sign-ins are rate-limited.

No system is perfectly secure. If we learn of a breach that affects you, we’ll tell you as the law requires.

10. This website and the waitlist

This section covers dayscent.app, including visitors from Europe. Joining the waitlist means you consent to launch emails. You can withdraw that consent and ask us to delete your waitlist data at any time.

  • Hosting: the site runs on Cloudflare (Cloudflare Pages). Like any web host, Cloudflare processes your IP address and basic request details to deliver the pages and protect them from abuse.
  • Waitlist: if you join the waitlist, we store your email address and the date you joined in Cloudflare Workers KV (Cloudflare’s key-value storage). We use it only to email you when Dayscent launches. We don’t share or sell the list.
  • Welcome email: when you sign up, we add you to the waitlist immediately and send one welcome email through Resend. Resend receives your email address for that. We send the launch email when Dayscent is ready. Older confirmation links can still be used for 48 hours after they were sent.
  • Abuse protection: to stop automated sign-ups, the form runs Cloudflare Turnstile, a bot check that processes your IP address and basic browser signals. We also keep a short-lived counter tied to a one-way hash of your IP address and the current hour. It expires after one hour, and we never store your raw IP address in the waitlist database. Cloudflare separately processes request and security logs.
  • No tracking: the website doesn’t use analytics or advertising trackers. Poll links use the device cookie described below and may display bottle photos from approved fragrance photo hosts; the site’s fonts come from dayscent.app.
  • Leaving the waitlist: email [email protected] and we’ll remove your address. We’ll delete the whole waitlist once the launch email is sent, or after 12 months at the latest.

Poll links (draft — needs owner OK)

When you vote through a poll link, Dayscent stores your choice, an optional first name (visible only to the person who asked), and a keyed hash of a random device cookie to limit repeat votes. For abuse limits, your network address is stored only as a hash in rate counters, removed within about 20 minutes (a 15-minute window plus cleanup). Cloudflare Turnstile checks for bots. Votes are deleted 30 days after the poll was created.

11. Changes to this policy

We’ll update this page when the app changes what it collects or who it shares with, and change the effective date above. If a change matters, we’ll tell you in the app before it takes effect.

12. Contact

Calvix Ventures LLC, 4925 S Broadway Ave #1220, Wichita, KS 67216, USA. Email: [email protected].

Copyright complaints go to our designated agent: see Copyright complaints (DMCA) in the Terms.

Dayscent

Your scent for the day. Out now on iPhone.

Download on the App Store

Help

  • Support
  • Delete your account
  • [email protected]

Follow

  • Instagram @dayscent.app
  • TikTok @dayscent.app

Legal

  • Privacy policy
  • Terms

© 2026 Dayscent. Emoji art: Noto Emoji by Google. Font: Figtree (SIL OFL 1.1). Apple, the Apple logo, and App Store are trademarks of Apple Inc.