FAQ

What is Driftmark?

Driftmark is a hosted status page service for communicating incidents and planned maintenance. It gives you a dependable public page where customers, team members and other stakeholders can quickly understand what’s happening, what you’re doing, and when to expect the next update.

Who is Driftmark for?

Driftmark is built for small and medium-sized organisations that want a status page that’s easy to maintain, professional in appearance, and aligned with EU expectations on privacy and data handling.

What does “privacy-first” mean in practice?

It means Driftmark is designed to minimise data collection and avoid tracking-based growth patterns. We do not sell personal data, and we aim to avoid unnecessary identifiers, invasive analytics, and third-party marketing technology.

Do you use cookies?

Driftmark is designed to work without tracking cookies. Where cookies are used, they are limited to what’s necessary for core functionality (for example, sign-in/session management for administrators). Public status pages are intended to work without requiring visitors to accept cookies.

Do you track visitors on public status pages?

No “ad-tech style” tracking. Driftmark’s goal is that a status page should be readable without profiling visitors. Any analytics (if enabled) is intended to be privacy-friendly and used to understand basic usage, not individuals.

What about subscribers — is their privacy protected?

Yes. Subscriptions are opt-in, and Driftmark is designed so subscriber privacy is protected by default. We do not treat subscriber data as a marketing list, and we don’t use subscriptions as a reason to introduce tracking. Subscriber details are not shared with the creator of a status page.

What data do you process about administrators (customers)?

To operate the service, Driftmark processes typical account and service data such as login identifiers, organisation details, and configuration for your status pages. We aim to keep this limited to what’s needed to provide the service and keep it secure.

What does “EU-first” mean?

“EU-first” means Driftmark is built with European expectations in mind: privacy-respecting defaults, clear data handling, and an approach that fits EU-based teams and their customers. As the service matures, Driftmark’s infrastructure and operations are intended to remain EU-oriented.

Where is data stored and processed?

Driftmark aims to keep data storage and processing within the EU/EEA wherever feasible. Specific infrastructure details may evolve during early access, but the direction is to remain EU-based and transparent about providers and sub-processors.

Is Driftmark GDPR compliant?

Driftmark is built to support GDPR-aligned operations through privacy-by-design choices, data minimisation, and clear separation between customer/admin data and subscriber data. Compliance depends on how each organisation uses the service, but Driftmark’s design is intended to make compliant use straightforward.

Do you offer a Data Processing Agreement (DPA)?

For business customers, a DPA is typically expected. Driftmark provide appropriate contractual terms and a DPA as part of the paid offering (or when required), reflecting the roles and responsibilities under GDPR.

Can I use my own domain?

Custom domains are a common requirement for status pages. Driftmark’s roadmap is to support this in a controlled and secure way. Availability may depend on your plan and early access stage.

Can I control branding and the look?

Yes – status pages should feel like part of your service. Driftmark focuses on simple, professional branding controls (such as name and basic presentation) rather than heavy customisation that becomes hard to maintain.

Does Driftmark support multiple services/components?

Yes. You can communicate status per service/component (for example: API, dashboard, web app) and keep the overall page clear and readable.

What notification channels do you support?

Email is typically the first channel because it is universally accessible and dependable. Additional channels may be added over time, but Driftmark’s focus is on doing a small set of channels well.

Is there an API?

An API can be useful for automation (for example, posting updates from your incident workflow). API availability may depend on plan and early access stage.

What is the Early Access programme?

Early Access is a way to onboard teams gradually while the product is still evolving. You’ll get access before the general release, and your feedback can influence priorities and polish. Features may change during this period as we learn what teams actually need.

What should I expect during Early Access?

You should expect a service that is usable and stable, but still improving. Some features may be limited, some workflows may change, and documentation may be lighter than at full launch. The goal is to deliver a dependable core experience and iterate quickly based on real usage.

How do you handle security?

Security is treated as a baseline requirement. Driftmark aims to use industry-standard practices such as encrypted transport (HTTPS), sensible access controls, and secure operational defaults. As the product matures, you should expect more formal security documentation.

What if Driftmark is down during a major incident?

A status page needs to stay available when your main service is struggling. Driftmark is built with reliability as a core requirement, and we aim for a resilient setup appropriate for incident communication. No provider can promise perfect uptime, but dependability under pressure is a primary design goal.

What’s the pricing?

Pricing will be published closer to general availability. The intention is straightforward plans that work for small and medium-sized organisations, with paid tiers reflecting needs like multiple pages, custom domains, and advanced controls.

How do I get started?

Request Early Access and we’ll onboard you as capacity allows. If you have requirements (custom domain, multiple organisations, compliance needs), mention them—those details help ensure Driftmark fits your use case.