Cookie Policy
Last updated:
This policy explains what cookies and similar technologies Bedspace Manager uses, why we use them, and how you can control them. Questions? support@bedspacemanager.com
1What Are Cookies
Cookies are small text files placed on your device when you visit a website or use a web application. They allow the site to recognize your device and remember information about your visit — for example, keeping you signed in, remembering your preferences, or measuring how pages are used.
In addition to cookies, we may use similar technologies such as:
- Local storage — browser-side key/value storage used for performance caching of non-sensitive UI state.
- Session storage — temporary browser-side storage cleared when you close the tab; used for short-lived UI state.
- Device identifiers — on mobile apps (iOS and Android), we may use device-level identifiers for push notification delivery and crash reporting.
This policy covers all of these technologies collectively when we use the word “cookies”.
2How We Use Cookies
We use cookies for four purposes:
- Authentication & security — to keep you securely signed in and protect against attacks such as CSRF.
- Functionality — to remember your preferences so you do not have to reconfigure them on every visit.
- Analytics — to understand which features are used most and where users encounter friction, so we can improve the platform. All analytics data is aggregated and anonymized.
- Performance — to cache non-sensitive data locally and reduce load times.
3Types of Cookies We Set
The table below lists every category of cookie we set, what each one does, and how long it lasts. Where a category is optional, you can disable it without affecting core functionality (see Section 6).
Strictly Necessary
RequiredRequired for the platform to function. These enable authentication, security, and session continuity.
| Name | Purpose | Duration |
|---|---|---|
| session_token | Keeps you signed in across page loads and tab switches | Session / 30 days |
| csrf_token | Protects form submissions against cross-site request forgery attacks | Session |
| auth_state | Stores temporary OAuth state during Google Sign-In flow | 5 minutes |
Functional
OptionalEnhance your experience by remembering choices you have made, such as your preferred language or in-app settings.
| Name | Purpose | Duration |
|---|---|---|
| locale_pref | Stores your preferred display language | 1 year |
| ui_prefs | Remembers sidebar state, table column order, and other UI preferences | 1 year |
Analytics
OptionalHelp us understand how visitors and users interact with the platform so we can improve it. All data is aggregated and anonymized — no individual is tracked or profiled.
| Name | Purpose | Duration |
|---|---|---|
| _analytics_id | Assigns an anonymous visitor ID to measure page views and feature usage | 1 year |
| _session_id | Groups activity within a single browsing session for funnel analysis | 30 minutes |
Marketing
OptionalWe do not run advertising campaigns and do not set any advertising or retargeting cookies on the platform. The marketing website does not use any third-party ad network cookies.
4Third-Party Cookies
Some features of the platform rely on third-party services that may set their own cookies. We do not control these cookies; they are governed by each provider's own privacy and cookie policies.
Google Maps Platform
When you add or search for property addresses using the Google Places API, Google may set cookies on the page. These are used by Google to measure API usage and detect abuse. Governed by the Google Privacy Policy.
Google Sign-In (OAuth)
If you use “Sign in with Google,” Google will set authentication cookies during the OAuth flow. These are cleared once the sign-in is complete and the session token is issued. Governed by the Google Privacy Policy.
Payment Processor
When you visit the subscription checkout, our payment processor sets cookies to protect against fraud and remember card entry state. Their cookie policy is linked at checkout. We do not receive or store your card details.
Analytics Provider
We use a privacy-focused analytics tool that does not build individual user profiles and does not share data with advertising networks. The tool operates under a data processing agreement with Bedspace Manager and sets only the anonymized cookies listed in Section 3.
5Cookie Duration
Cookies we set fall into two lifetime categories:
- Session cookies — exist only while your browser tab is open. They are automatically deleted when you close the tab or browser. Used for CSRF protection and short-lived OAuth state.
- Persistent cookies — remain on your device for a set duration (see Section 3 for specifics). Used for authentication, preferences, and analytics. You can delete these at any time via your browser settings.
6Managing Your Cookies
Consent Banner
On your first visit to the Bedspace Manager marketing website (https://www.bedspacemanager.com), a cookie consent banner is shown. You can accept all optional cookies, or choose only the categories you allow. You can change your choices at any time by clicking “Cookie Settings” in the page footer.
Browser Controls
All modern browsers allow you to view, block, and delete cookies through their settings. Instructions for common browsers:
Impact of Disabling Cookies
Disabling or deleting strictly necessary cookies will prevent you from signing in and using the Bedspace Manager platform. These cookies cannot be turned off while you are actively using the service.
Disabling functional or analytics cookies will not prevent access to the platform but may mean your preferences are not remembered between sessions.
Mobile Apps
The iOS and Android apps do not use browser cookies. Device identifiers used for push notifications can be revoked by disabling notifications for the Bedspace Manager app in your device settings (iOS: Settings → Notifications; Android: Settings → Apps → Bedspace Manager → Notifications).
7Do Not Track
Some browsers offer a “Do Not Track” (DNT) signal. There is currently no industry-standard interpretation of this signal, so Bedspace Manager does not alter its data collection behavior in response to DNT headers. You can use the cookie controls in Section 6 to limit optional data collection regardless of your DNT setting.
8Policy Changes
We may update this Cookie Policy when we add new features, change providers, or in response to legal changes. The “Last updated” date at the top of this page will always reflect the most recent version. Material changes — such as adding a new category of cookie — will be notified via the consent banner on your next visit.
9Contact Us
Questions about cookies or this policy? We're happy to help.