Cookies Policy

Wedding Seat uses cookies and similar technologies to operate the Service, keep accounts secure, remember settings, and improve reliability. Some technologies are required for the Service to function (“strictly necessary”). Others are optional and may be used only if enabled or configured.

• We do not sell personal information through cookies.
• We minimize tracking and aim to use privacy-friendly defaults.
• You control optional technologies through your browser settings and, where applicable, consent tools.

Cookies are small text files stored on your device by your browser. They can remember preferences, maintain sessions, and support security features.

In addition to cookies, we may use “similar technologies,” including:

• Local storage / session storage: browser storage used to remember settings or session state.
• Pixels / tags: small snippets that measure whether a page was viewed or an action was taken (typically optional).
• SDKs: software libraries used in our apps for functionality or measurement (typically optional).
• Server logs: technical logs created automatically when you access the Service.

We refer to all of the above as “technologies” in this policy.

Below is a practical overview of the technology categories. The specific set can evolve as features change, but categories and controls remain consistent.

• Strictly necessary: required for login, security, load balancing, and core functionality.
• Preferences: remembers language, UI settings, and user choices.
• Analytics: helps us understand usage patterns and performance (only if enabled).
• Marketing: helps measure campaigns or show relevant ads (only if enabled).

When we use optional categories, we aim to configure them to reduce identifiability (for example, aggregated reporting where possible).

These technologies are required for the Service to function. They enable account login, security protections, and essential features. Because they are essential, they cannot be disabled through a cookie banner; however, you can block them in browser settings, which may cause parts of the Service to stop working.

• Authentication and session cookies to keep you logged in.
• Security technologies to prevent abuse, fraud, and unauthorized access.
• Infrastructure/load balancing to deliver the Service reliably.
• CSRF protection and request validation.

Preference technologies remember your choices so the Service feels consistent. This may include language selection, theme (light/dark), layout preferences, or dismissed notices.

• Language preference (i18n) and region settings.
• UI state (for example, dismissed banners or onboarding steps).
• Non-sensitive customization settings.

We may use analytics technologies to understand how users interact with the Service, diagnose issues, and improve performance. Analytics helps us answer questions like which pages are slow, where errors occur, and which features are used most.

When analytics is enabled, we aim to limit collection and use it in a way that supports privacy-friendly measurement (for example, aggregated reporting where possible).

• Performance and error monitoring (crash/error logs).
• Aggregated usage statistics and feature adoption.
• Debug telemetry to troubleshoot reliability problems.

We may use marketing technologies to measure campaign performance (for example, whether a signup happened after an ad click), and to avoid showing irrelevant or repetitive ads. Marketing technologies may be set by us or by third parties.

If marketing technologies are enabled, we will apply them in accordance with applicable law and consent requirements.

• Conversion measurement (attribution).
• Audience measurement and frequency control.
• Fraud prevention and campaign security checks.

Some technologies may be provided by third parties that help us run the Service (for example, payments, email delivery, analytics providers, or embedded content). Third parties may place their own cookies or use similar technologies, subject to their policies.

Where a third party acts as our service provider, we configure and use them for Service purposes. Where a third party acts independently (for example, an embedded platform), your relationship may be governed by that third party’s terms.

We use Google Maps / Places for venue search and map display. When these features load, Google may set its own cookies or use similar technologies under Google’s privacy policy; in the EEA/UK they load subject to your consent.

You can control cookies and similar technologies in several ways:

• Browser controls: Most browsers let you block or delete cookies and manage site data.
• Device controls: Some devices provide additional privacy controls.
• Consent tools: Where we provide consent settings, you can change your choices at any time.

Blocking all cookies may prevent the Service from functioning correctly (for example, login and account features may break).

If you are located in the European Economic Area (EEA) or the United Kingdom, we will obtain consent for non-essential technologies where required by law. Strictly necessary technologies do not require consent because they are required to provide the Service you request.

You can withdraw consent at any time through the controls described in this policy. Withdrawing consent does not affect the lawfulness of processing before withdrawal.

Some browsers offer a “Do Not Track” (“DNT”) signal. There is no uniform industry standard for how to respond to DNT signals. As a result, we do not currently respond to DNT in a standardized way. We will continue to monitor developments and may update our approach if standards emerge.

We may update this Cookies Policy from time to time. The “Last updated” date at the top reflects the most recent revision. If changes are material, we will provide notice as required by law.

Questions about this policy? Contact us and we’ll help.

Go to Contact page