Legal & privacy
Privacy policy
How wayfold handles account data and provides privacy-first analytics for customers.
Last updated: 11 October 2026
Who is responsible
minddraft AG, Säntisstrasse 12 6345 Neuheim Schweiz, operates wayfold. We determine the purposes of processing for our own website, customer accounts, contracts, billing and support. For analytics on a customer website, its operator remains responsible and we process the submitted data on their behalf. The visitor data policy describes this analysis; the data processing agreement sets out the contractual framework.
Customer accounts and collaboration
For authentication, access and collaboration we process email addresses, optional display names and avatars, login providers, workspace membership, roles and invitations. This includes onboarding state, team changes, support requests and necessary administrative records. For paid services we store plan, contract and payment status and payment-provider references. Full card and bank details remain with the payment provider. This data is not attached to visitor events.
Test Mode: a deliberately activated team feature
Test Mode requires login and permission for the website concerned. An authorized team member starts it themselves from wayfold or through the Test Mode launcher. An ordinary website visit does not activate it. We process the pins deliberately placed and comments written by the team member, the scrubbed page path, a structural element reference, position, status, timestamps and authorship. Authorized team members see the author’s name and, where available, profile picture. These records support collaborative troubleshooting and are not linked to visitor sessions. Public visitor analytics does not start while a Test Mode credential is present in that tab. Access is limited to the registered website and one tab and expires after no more than eight hours. Ending Test Mode revokes authorization and removes the tab credential. Saved issues remain until the team deletes them or deletes the website. Authorized testers may explicitly enable screenshots in Test Mode and share the tested tab through their browser. Placing a pin prepares a still image. Before saving, they can remove the image or redact areas. Only saving uploads the image to wayfold. It is stored privately on the issue, served only after a fresh property-permission check, and deleted with the issue or property. Captures may contain visible personal information; the responsible team reviews it before sharing. No video or audio recordings are stored, and images are never linked to visitor analytics.
Browser storage by purpose
Public visitor analytics sets no cookies and stores no visitor identifier in localStorage or sessionStorage. A deliberate analytics opt-out is stored separately as a website-specific preference in localStorage for up to 180 days. It is not transmitted to analytics. Dashboard authentication retains login state in browser storage. Deliberately activated Test Mode uses sessionStorage for its temporary tab credential and the position of its controls. These uses support the requested login or testing feature; they are not identifiers for visitor analytics.
Visitors to an analysed website
Depending on enabled features, we process scrubbed paths, events, order and coarse elapsed times within a visit, referrers and campaign values, and coarse browser, device and country information. Optional heatmaps contain counted grid cells; performance data contains measurement buckets. IP addresses and user agents are processed transiently when requests arrive, but are not stored as raw values in analytics. Short-lived mappings connect events within a visit. The absence of a direct identifier is not a blanket assurance of legal anonymity. Details, limits and deletion periods are described in the visitor data policy.
Analytics on our own website
We measure the website and signed-in application at wayfold.ch with wayfold itself, under the same rules as customer websites: no cookies, no visitor profile, and no storage of IP addresses or full user agents. We record sanitized pageviews and enabled analytics signals. Private identifiers in application paths, such as workspace, website and report identifiers, are replaced with fixed placeholders before transmission. Account names, email addresses, form values and report content are not attached to analytics. We rely on our legitimate interest in understanding and improving our offer (Art. 6(1)(f) GDPR, where applicable). You can disable analytics at any time through “Analytics settings” in the footer; Global Privacy Control is respected. Public visitor analytics is suppressed while Test Mode is active.
Purposes and legal bases
We use customer data to deliver the requested service, manage contracts and billing, enable collaboration, provide support and protect security. Where the GDPR applies, contract performance and pre-contract requests rely on Article 6(1)(b), legal obligations on (c), and necessary security and operational purposes on (f). For team members who are not personally a contracting party, necessary account management relies on the interest in secure team access requested by their employer or client. Separate consent is sought only for voluntary purposes identified as such. Activating Test Mode is a request for that feature, not blanket consent to other processing. The operator of each customer website determines the applicable legal basis and any required permissions for its analytics.
Data location and security
The application runs with Hetzner in Germany. The separate production database is hosted by Supabase in Zurich, Switzerland. The application checks workspace membership and roles, separates visitor analytics from account administration and validates incoming data. HTTPS protects transmission to the hosted service. Integration tokens are encrypted on the server. The production database has daily managed Supabase backups with a rolling recovery window of approximately seven days. Point-in-time recovery (PITR), an additional independent backup and a guaranteed recovery time are not included in the standard service. Uploaded files are not covered by database backups. These backups do not replace customers’ own exports of important data.
Recipients and optional integrations
The service provider overview separates infrastructure, customer services and customer-selected integrations. Supabase supports the database, authentication and file storage. Stripe supports payments. Google may be involved in deliberately selected Google login, in a separately authorized Search Console connection and in an import from Google Analytics 4. Integration credentials stay server-side; imported daily search and analytics totals are not linked to individual visitor sessions.
International transfers
The application is hosted in Germany and the primary database in Switzerland. Supabase Pte. Ltd. is based in Singapore; affiliates and support may access necessary data, including from the United States. Google and Stripe/Link may also process account, connection or payment data in the United States. A Swiss database location does not exclude these transfers. Transfers to countries without a recognised adequate level of protection require appropriate safeguards. Supabase’s published data processing agreement includes EU Standard Contractual Clauses and Swiss adaptations. Google and Stripe describe their respective transfer mechanisms in the privacy resources linked below. Information and a copy of the safeguards applicable to our processing can be requested at support@wayfold.ch; confidential contractual information may be redacted.
Retention and deletion
Session-linked analytics data is removed by scheduled cleanup after a retention window of 365 days from the last server-side receipt. Limited daily statistics are retained for at most 730 days, technical receipts for seven days and monthly usage counters for up to 84 months. Usage counters contain no visitor paths or session identifiers. Issues, comments and voluntarily shared screenshots remain until the issue or website is deleted. Account data is needed for the duration of access. Support correspondence is retained for as long as necessary to resolve the request, fulfil existing obligations or establish, exercise or defend specific claims. The same criteria apply to contractual and security records. Accounting books and vouchers subject to Swiss statutory retention requirements are generally retained for ten years from the end of the financial year. Processed billing webhook IDs are retained for 400 days; resolved or long-expired invitations and transfers are removed after 90 days. The trial deletion process provides a further 30-day warning period after the trial expires and requires notifications. Automatic deletion is not promised if these notifications have not been sent. Deleted data may remain in database backups until the rolling backup window expires. Backups are used for recovery, not continued routine use of deleted data.
Requests and rights
Contact minddraft AG using this channel: support@wayfold.ch. Depending on applicable law, you may request access, correction, deletion, portability, restriction or objection and withdraw consent for the future. For an analysed customer website, its operator is the first contact; we assist under the processing agreement. We do not keep a named visitor list or collect additional tracking identifiers to handle a request. Where a record cannot be attributed to a person, we explain this limitation. You may contact the Swiss Federal Data Protection and Information Commissioner or a competent EU/EEA data protection supervisory authority.
Security reports
Send privacy and security reports to support@wayfold.ch. Please provide only information necessary for investigation and do not include passwords, access tokens or unredacted visitor data. We investigate reports, restrict access where necessary and notify affected customers without undue delay of a breach involving their entrusted data. Legally required notifications to authorities or individuals follow applicable law. The data processing agreement additionally governs notification and assistance obligations for customer data.
Changes
We update this policy when the product, providers, or legal requirements materially change. The date above identifies the current version.