Who is responsible
KREYA is the studio responsible for the personal information described in this notice.
KREYA · KVK 80939805
Kasteellaan 345, 2516 BJ, The Hague, South Holland, The Netherlands
info@kreya.design
Information and purposes
This notice covers the public website, booking and newsletter services, and summarises KREYA OS. The KREYA OS privacy notice provides additional detail about the private workspace. Read both notices when using OS.
| Activity | Information involved | Purpose |
|---|---|---|
| Browsing | Technical connection information such as IP address, request time, browser information and requested page may be processed by the hosting service. | Delivering and securing the website. |
| Free review request | Company or brand name, website or profile link, email, first name, business type, stage, financial range, any notes you add, your newsletter choice and acceptance of the review terms. | Preparing and sending the review you request, and following up about it. Answers are emailed to KREYA and a confirmation is emailed to you. Business stage and the selected financial range determine whether we offer a review or point you to our guides, and whether online booking is available. Your email and first name may be saved with our email provider so messages about your review can address you by name. You only receive the newsletter if you tick that box. |
| Booking | Your name, email, selected time, questionnaire answers and acknowledgement of this notice. | Arranging the conversation you request. Google Calendar receives your name, email, appointment time and management link; Google Meet provides the meeting. Financial answers are not included in the Calendar invitation. |
| Newsletter form | An email address entered into the field, and where your visit came from, such as a link tag or the referring website. | Adding your address to the newsletter list in Resend and sending a welcome email. You join as soon as you subscribe. We record your consent, when you gave it and where you signed up, and every email includes an unsubscribe link. Booking a call does not subscribe you. |
| Visit source | Where your visit came from: link tags such as utm_source, utm_medium and utm_campaign, or the referring website, and the first page you landed on. | Sent with a booking, review request, newsletter sign-up or job application, so we can see which channels bring enquiries. |
| Contact form | Your name, email, answers from both questionnaire steps, additional message and acknowledgement of this notice. | Sending your enquiry through Resend to info@kreya.design, with Matthew copied at his booking email address when it differs. Your email is the reply address so Matthew can respond directly. Sending a message does not book a call or subscribe you to the newsletter. |
| Contact through other channels | Information you choose to send through email or a social platform. | Responding to your enquiry. The relevant platform also processes information under its own notice. |
We use booking and project-enquiry details to take steps you request before a potential contract with you. If you contact us on behalf of an organisation, we rely on our legitimate interests in responding to business enquiries and managing that relationship. Newsletter subscriptions rely on your consent. We rely on our legitimate interests in operating a reliable, secure website for technical logs, abuse prevention and necessary records of subscription preferences. We rely on our legitimate interests in understanding how visitors find the website, through cookieless visit statistics and the visit source sent with forms. You can contact us instead of using the online questionnaire.
KREYA OS and electronic signing
KREYA OS is our invitation-based workspace for clients, collaborators and KREYA staff. We receive account details from you, the person inviting you and, if you choose Google sign-in, Google. Workspace colleagues also contribute information about projects and their participants.
Account information includes names, email addresses, profile images, roles, workspace membership and sign-in records. Workspaces hold projects, tasks, messages, attachments, brand assets, billing details, invoices, contracts and team profiles. Birthdays are optional. Account and membership details are needed to provide access; without them we cannot provide an OS account. Only add information needed for the work.
We use this information to administer access, deliver services, collaborate, provide support, manage billing and agreements, and protect accounts. Where you personally are a party to a contract, we process information necessary to perform that contract or take steps you request before it. For contacts acting for an organisation, we rely on our legitimate interests in managing the business relationship and coordinating its work. Our legitimate interests also include preventing misuse, securing the service and establishing or defending legal claims. Statutory invoice and tax records are processed to meet legal obligations. Signing consent records your decision to sign electronically; it is not blanket consent to all personal-data processing.
Information is visible to people authorised for the relevant workspace or function. KREYA owners have administrative access; other access follows assigned roles and permissions. Enabled email and Slack notifications share relevant task, message or business-record details with their intended recipients. If a client supplies personal data for KREYA to process solely on its instructions, that processing is governed by the client’s instructions and applicable data-processing agreement; the client remains responsible for its own privacy information.
Google sign-in supplies basic account and profile information through Supabase Authentication. It does not give KREYA OS access to Gmail, Google Drive or Google Calendar. The website’s host Calendar and Meet booking connection is separate.
For native electronic signing, KREYA OS records displayed signatures, signer names and email addresses, email-code verification evidence, consent, the agreement version, signing times and document checksums. Completed PDFs are emailed to both parties. Opening an agreement link records an event and notifies KREYA; that event does not prove who opened the link. KREYA OS does not offer a qualified electronic signature under eIDAS. SignWell remains relevant to agreements previously sent through that service.
See the OS access terms for account responsibilities and the electronic signing terms for the signing process.
Hosting and external services
The site is hosted on Vercel. Fonts are requested from Fontshare, and the embedded Thrive concept requests Google Fonts. Those requests disclose connection information to the relevant provider. Social links lead to LinkedIn, Instagram and X; following a link takes you to that provider’s service.
The integrations also use Neon for the website database, Resend for email delivery and subscription preferences, and Google Workspace for Calendar and Meet. These providers and their subprocessors may process information outside the European Economic Area. Their published processing terms describe transfer safeguards, including standard contractual clauses where applicable.
For OS, Vercel hosts the application; Supabase provides authentication, database and file storage; Resend delivers service emails; Stripe handles payment and billing services; Slack receives notifications in configured channels; and Google provides optional sign-in. Historical agreements may remain with SignWell. Each receives information relevant to the service used. Some providers, including Stripe for certain payment, fraud-prevention and legal-compliance activities, also act as independent controllers under their own notices.
Provider processing terms describe their responsibilities and international-transfer safeguards: Vercel, Neon, Resend, Google Workspace, Supabase, Stripe and Slack. These published terms do not mean that all processing takes place in the EEA. Contact info@kreya.design for information or a copy of the safeguards applicable to a particular transfer.
How long information is kept
Questionnaire answers stay in the active page until you book or send a message. Review requests are recorded in the request emails and handled as enquiry correspondence. They are not stored as booking records. We keep them for up to 12 months after the review is sent, unless you become a client or ask us to delete them sooner. The cleanup is configured to remove submitted questionnaire data from the active database once a confirmed, cancelled or failed booking is more than 90 days past its scheduled end. Unresolved booking operations are retried separately and may retain their submission until resolved. Newsletter requests that were never completed are removed after 7 days. An automatic cleanup runs every 15 minutes, removing expired records on its next successful run.
Subscribers remain until they unsubscribe. We retain necessary consent, opt-out and suppression records while needed to honour email preferences and prevent unwanted messages. Enquiry correspondence and minimal booking records are kept while needed to manage the conversation, follow up on requested work or resolve a related issue.
The questionnaire cleanup removes the encrypted submission from the active database. Calendar invitations, delivery logs and provider backups have separate retention arrangements. Log and backup retention depends on the provider, service and configured settings; it is separate from deletion of an active booking submission. We review requests to delete these records through info@kreya.design, subject to necessary legal or security retention.
OS records have different retention needs:
| Record | Retention period or criteria |
|---|---|
| Account and workspace content | While needed for active access, service delivery and agreed handover. At closure or on a deletion request, records must be assessed for removal and any continuing business, security or legal need. There is no automatic OS-wide deletion period. |
| Invoices and tax administration | Normally seven years under Dutch tax rules. Ten years applies to records concerning immovable property and transactions covered by the Union or Import One Stop Shop schemes, where applicable. |
| Agreements and signing evidence | For the agreement’s duration and afterwards where needed to show what was agreed, meet recordkeeping duties or establish or defend claims, taking applicable limitation periods and any dispute into account. |
| Security, activity and delivery records; backups | For the relevant operational or security purpose and provider retention cycle. Some evidence remains with a related agreement or invoice. These records do not share one universal expiry date. |
Archiving a workspace, revoking access or marking an item deleted does not by itself erase all records, attachments or provider backups. Contact us for a deletion request or the retention criteria for a particular record. We will explain any information that must be retained and why.
Your privacy choices and rights
Depending on the law that applies, you may have rights to access and correct personal information, request its deletion, restrict or object to certain uses, and receive a portable copy. These rights are subject to applicable conditions and exceptions.
Where processing relies on consent, you may withdraw it without affecting the lawfulness of processing before withdrawal. You may also be entitled to complain to your local data protection authority.
Contact info@kreya.design to exercise your rights. We may request proportionate information to verify your identity. Under the GDPR, requests are normally answered within one month; where a permitted extension is needed, we will explain it within that first month. You can complain to the Dutch Autoriteit Persoonsgegevens or another competent supervisory authority.
Newsletter, bookings and future changes
The booking confirmation and Calendar invitation include a private link to cancel or reschedule. You join the newsletter only by subscribing yourself, and every newsletter includes an unsubscribe link. Enquiring about a project or booking a call does not provide permission to receive a newsletter.
We will update this notice’s effective date and explain any material changes.