Affluma uses browser storage to make selected features useful, such as remembering a saved phrase or keeping a practice record. “Storage” includes more than cookies: it can include local storage, a browser database, cached files and settings held for a single tab. This page explains the built-in features; additional providers have their own notices.
Choices you can make
You can browse public articles without creating a saved collection. Saving sets, recording and keeping audio, saving offline articles, reacting to a phrase and enabling optional services are separate choices. Use Privacy Choices for the built-in analytics preference. Your browser settings also let you inspect, block or clear site data, although blocking storage may prevent saving or restoring features.
What different storage is used for
Favorites, sets and reading preferences
Local storage holds favorites and named sets when you choose to save them. Your latest builder edits, Studio text and settings, and listening preferences also save automatically when storage is available. It can also remember controls such as a reading style, text size or an available privacy preference. These records belong to that browser and website origin. They are not automatically sent to an account or synchronized to another device.
Optional welcome name
A full name entered on a personal practice page stays in local browser storage to show your welcome. It is not sent to WordPress or analytics. Delete my data removes it; a backup you explicitly export can contain it.
Studio handoff and recordings
Moving selected phrases from an article or builder into Studio uses temporary tab storage so the next page can receive them. Completed microphone recordings and generated audio save to the browser database when space is available; a visible warning appears when they cannot be saved. Download important files separately. The journal uses a separate browser database, commonly called IndexedDB. Clearing local storage alone may not clear that database; use the relevant delete control or clear all site data.
Challenges and daily practice
Optional practice controls may keep selected challenge days, progress, preferences and related local entries so you can return later. They are not a medical record or verified attendance record. Resetting a challenge or clearing site data can remove progress. A saved daily reminder file is a separate file you choose to import into your own calendar.
Gratitude and built-in audio
Journal entries, tags and favorites are stored by date in IndexedDB. Private writing is not sent to our website. A voice model and its supporting files are loaded from this website when you preview or create audio. Your browser may cache those files automatically when supported. Audio Studio has a control to remove its model caches; your browser may retain separate HTTP-cache copies until they expire. Temporary wallpaper photos remain in page memory and do not become permanent backgrounds.
Daily time zone and reminders
The local daily window is detected automatically from trusted hosting location information when available, with the browser’s time zone as a fallback. Earlier manually chosen time-zone preferences are no longer used. When you turn on browser reminders, local storage also keeps the push endpoint and a management token needed to update or cancel that subscription. The website stores the endpoint, a hash of the token, the selected reminder time and automatically detected time zone, and technical delivery records. Server subscriptions are set to expire 180 days after creation or successful renewal; scheduled cleanup removes expired records when the website scheduler runs. Visiting a reminder panel can renew an active subscription after seven days.
Use Reminders to turn off a browser subscription before clearing its local data when possible. Deleting practice data in My Device does not cancel notifications. An imported calendar file contains 180 practice occurrences and remains under your calendar’s control; remove those events in your calendar if you no longer want them.
Reactions
Clicking Like or Love creates a random browser identifier used to manage a single current reaction for each public article or published phrase. The server stores a salted hash rather than the plain identifier. Removing a current reaction is different from clearing the identifier: clearing storage can make the website unable to associate that browser with a previous reaction. Reaction records expire after 365 days without an update.
App files and offline articles
The installable app can cache necessary static files. Public article text is available offline only when you choose to save an offline copy. Administration, contact submissions, private Studio data and service requests are not cached as public offline pages. A saved copy can be older than the live article and is labeled accordingly. Use the app controls to clear offline copies; clearing browser site data is another option.
Necessary technical storage
Form security tokens and short-lived validation or abuse controls help process requests safely. WordPress administration may use login or security cookies for people who sign in to manage the site. A visitor does not need an administrator account to use public affirmation tools. Hosting and security infrastructure may have additional technical controls needed to deliver or protect the service.
Optional analytics and advertising
Built-in aggregate analytics is off by default and uses a browser opt-out when you set one. It respects supported Do Not Track and Global Privacy Control signals. It does not use a cross-site advertising profile or store private builder answers in its reports.
Hosted image advertisements differ from third-party embedded advertisements. An embedded service is loaded after a visitor chooses to load it. Once loaded, a provider may set or read its own cookies or other identifiers under its policies. Additional regional consent controls must apply where required for the services actually used. Closing an advertisement does not necessarily delete storage it has already set.
Browser activity reports require both the owner enabling the feature and your separate choice to allow it. Only then is a random local analytics identifier created; the server stores a salted hash with permitted usage events. Opting out clears the local identifier and consent. Reports do not contain welcome names, journal text or private affirmation wording. Existing report rows follow the site’s retention policy.
Retention and clearing data
Session storage generally lasts for that browsing session. Local sets, preferences, saved recordings and caches may remain until you remove them or the browser clears or evicts them. Provider cookies have their own durations. No browser-storage duration is a guarantee that a file will be preserved.
Before clearing site data, export anything you wish to keep. Removing an app icon may not erase all site data, and clearing site data does not remove separately downloaded files or backups. If you need help understanding a storage item, email hello@affluma.com with its name and the page where you saw it, without sending private contents. See the Privacy Policy for server processing and your applicable rights.