LEGAL INFORMATION
Privacy policy
Last updated: 6 October 2026
How Leya Growth processes personal data when you use the website, contact us, book a meeting or use the customer portal. This notice also explains cookies and your choices.
1. Data controller
Leya Growth is a sole proprietorship owned by Leya Lundin. Leya Growth is responsible for personal data processing in connection with this website, contact enquiries, meeting bookings and customer relationship administration.
Contact: leya@leyagrowth.se, +46 76 564 04 45. Website: leyagrowth.se.
If customer material in the portal contains personal data about other people, the customer company may be the controller for that material and Leya Growth may process it under the customer’s instructions. Contact us if you need to know who is responsible for particular information.
2. Personal data and its sources
The contact form collects your name, email address, optional company name, selected service, selected goals and project description. You provide this information. If you email or call us, we also process the contact details and information you provide through those channels.
Booking and portal data are described in sections 10 and 11. Technical providers may also process IP addresses, browser and device information, time, visited addresses and logs for operations and security. Company contact and project information may also be provided by the customer company or Leya Growth.
Only provide information and files needed for your enquiry. Do not submit sensitive personal data or personal identity numbers through the contact form, booking notes or Leyo.
3. Purposes
We use contact information to answer enquiries, plan and manage meetings, communicate about services, and deliver and follow up customer projects. Portal data is used for access, project collaboration, file sharing, delivery reviews, support and documenting decisions.
Technical information is used for operations, security, access control, abuse prevention and troubleshooting. Analytics and advertising measurement are optional and described separately in section 9.
4. Legal basis and voluntary choices
Enquiries, bookings and services you request may be processed to take steps at your request before a contract or perform a contract. For contacts at business customers, customer communications and project administration are normally based on our legitimate interest in managing the relationship. Operations, security and abuse prevention are based on legitimate interest. Information that must be retained for legal obligations, such as accounting, is processed on the basis of a legal obligation.
Optional analytics and advertising technologies are used only with your active consent for each purpose. You can decline or withdraw consent without losing access to the contact form, booking or customer portal. The booking form checkbox acknowledges that you have read the booking information; it is not consent to advertising or cookies.
The contact form requires a name, email address, selected service, goals and project description to submit. Booking requires a name, email address and selected meeting time. The customer portal requires an invited account and permission. Company name in the contact form and booking notes are optional.
5. Contact form and email
The contact form is submitted to Formspree over an encrypted connection. Formspree receives and processes the information so Leya Growth can respond. The website has no local form archive or automatic deletion schedule. Formspree archives and any email copies are managed in the respective service; no specific archive duration is configured in the website code.
Booking emails and portal notifications use Loopia in the prepared production configuration. Contact and email information is used for your enquiry and customer relationship, not automatically for newsletters. See Formspree’s privacy information and Loopia’s privacy information.
6. Leyo and public demonstrations
Leyo responds using rules and information included in the website code. Messages are displayed and processed in the current browser page. They are not sent to an external AI service or saved by Leyo in cookies, localStorage or a server database. Messages disappear when the page is reloaded or closed.
The public customer portal demo uses sample projects and temporary state in browser memory. Demo actions do not create real customer accounts, tickets or deliveries. The portfolio booking demonstration also uses temporary state; it does not create a real booking or submit form data to the booking API. Consented measurement of opening and using the customer portal demo is described in section 9.
7. Hosting, operations and security logs
The website and its server functions are designed for Netlify. Database, authentication and private file storage use Supabase where those features are enabled. Providers may process technical information to deliver and protect the services. Security data includes sessions, permissions, administrative actions and abuse prevention. Request rate limits use hashed or keyed identifiers derived from information such as IP addresses and, in the portal, email addresses.
This security work is separate from optional visitor and advertising measurement. Provider operational logs, backups and email archives are also controlled by service account settings and agreements. A single fixed retention period for these external copies cannot be determined from the website code.
8. Fonts and external links
The website retrieves fonts from Google Fonts. When your browser fetches fonts, Google receives technical information such as your IP address and the browser request. Font retrieval is separate from Google Analytics and does not authorize analytics cookies or measurement events. It is used to deliver the website’s typography and is assessed within the purpose of website operations.
Links to external websites or Google Meet open the respective service when you follow the link. That service’s own privacy and cookie information applies to your use there.
9. Cookies, browser storage and measurement
You choose analytics and marketing separately in the cookie panel. No option is preselected on your first visit. Decline all and accept all are in the same view with equivalent styling. Continuing to use the site is not consent. Use the visible Cookie settings button to change purposes, or Withdraw cookies to withdraw all optional purposes immediately. Your choice applies to this browser and the website origin.
Analytics: Google Analytics 4 (Google) is used only after analytics consent for statistics about visits and actions. Google Signals, advertising storage and advertising personalization signals are disabled in the website tag configuration. Marketing: Meta Pixel (Meta) and TikTok Pixel (TikTok) are used only after marketing consent for advertising measurement, attribution, audiences and possible ad personalization on their platforms.
After relevant consent, page visits are measured on public information pages. A contact form counts as a lead only after a successful server response: generate_lead in GA4, Lead in Meta and SubmitForm in TikTok. A booking counts only when the booking API confirms a saved booking: booking_completed in GA4 and Schedule in Meta and TikTok. A booking start is measured when an available slot is selected and the details form opens. Opening and using the customer portal demo are separate behavior events; Meta and TikTok use ViewContent for opening and custom events for use. Starts, demo activity, button clicks and ordinary page views do not count as completed leads or bookings.
Event parameters contain the action type and conversion or behavior category. Our event code does not send names, email addresses, messages, booking notes or management links as parameters. SDKs also process technical visit information, such as IP addresses, device and browser information, page and referring addresses and cookie identifiers. Meta and TikTok may associate information with accounts on their platforms. Automatic Meta event detection is disabled in code. TikTok’s SDK can process page and interaction metadata according to pixel settings.
Measurement is present on public information pages, the new booking page and the public customer portal demo. It is disabled on private customer pages, login and administration pages, and when managing an existing booking. Actions without consent are not sent retrospectively. Withdrawal stops further events and clears known tracking cookies and storage entries accessible to this website. Cookies on Google, Meta and TikTok domains cannot be deleted by this website; manage them in your browser or with the provider. The cookie button does not automatically erase data already transferred.
The first-party cookies below are stored on the website domain but can send information to an external provider. Third-party cookies are on the provider domain. Browser storage such as localStorage has no automatic browser expiry; our consent code checks validity and clears known entries. Browser protections can shorten cookie lifetimes. Consent validity is different from a provider’s retention of event data already transferred.
Provider cookie and privacy information: Google Analytics cookies, Google, Meta cookies, Meta, TikTok cookies and TikTok.
10. Meeting bookings and Google Calendar/Meet
The booking system processes your name, email address, selected service, meeting start and end times, optional notes, language, booking status and revision number. It also stores an internal booking ID, retry identifiers, a protected management link, any calendar ID and Meet link, and timestamps. The information is used to reserve the time, manage rescheduling and cancellation, and send confirmations.
The production configuration uses a Supabase/PostgreSQL database and Loopia SMTP. Confirmation and cancellation emails contain the service, time, any Meet link, Leya Growth contact details and, where relevant, a personal booking management link. Email jobs are stored for reliable delivery and troubleshooting. Local preview does not send email.
Google Calendar/Meet is enabled in the production configuration. The system reads busy calendar times and creates or updates meetings with the service, meeting time, time zone, internal booking ID and revision number, and requests a Meet link. The current calendar integration does not send the visitor’s name, email address or notes and does not add the visitor as a calendar attendee. When you join Meet, Google processes information under its meeting terms and your use there; the website does not record the meeting.
A management link is valid until seven days after the meeting ends and is replaced on rescheduling. This does not mean booking data is erased then. Cancellation changes the status and deletes the calendar event through the integration; it does not automatically erase the database record or previous emails. The booking register has no general automatic deletion. Completed email jobs become eligible for scheduled cleanup after 30 days; pending jobs and uncertain deliveries are excluded.
11. Customer accounts, projects and files
The private customer portal is for invited users. Supabase Auth processes account IDs, email addresses, password authentication, invitations, recovery links and authentication tokens. Passwords are forwarded to the authentication service over an encrypted connection; the Leya Growth application does not store plaintext passwords. Administrators also use multi-factor authentication. The portal stores company memberships, permissions and notification language preferences.
Project data includes company names, project descriptions, phase, status, progress, milestones and updates. Files are stored in private Supabase Storage with file names, size, type, uploader IDs and labels, and timestamps. Authorized customers see material for their companies and authorized administrators manage projects. Temporary upload links last 15 minutes and direct download links last 30 seconds. These are link validity periods, not file retention periods.
Deliveries are stored as versions with content, linked files, comments, change requests and approvals. Support and change tickets include titles, messages, status, attachments, extra-work proposals, amounts/currency and decisions. Events are associated with users, roles and times. History is retained for collaboration and documenting decisions; files included in delivery or ticket history cannot be deleted through the ordinary file button.
When notifications are enabled, invitation, recovery and project emails are sent through Supabase Auth and/or Loopia. Project notifications contain the update type and a portal link, not full comment text or attachments. Delivery status, attempts and recipients are stored. Administrative permission actions are logged. These are service messages and are not treated as consent to advertising.
Accounts, projects, published files, delivery and ticket history, and audit and notification logs have no general automatic deletion period in the application. They are not erased merely because a project ends or a session expires. Deletion must be handled separately considering the enquiry, customer contract, decision records and legal obligations. Revoked company permission stops access but does not itself erase the account or history. Temporary upload objects and abandoned uploads become eligible for cleanup after three hours if the cleanup job runs.
12. Retention and deletion
Retention must be assessed based on whether an enquiry is still relevant, a meeting or project requires follow-up, material is needed for the contract or to establish, exercise or defend legal claims, and legal obligations require retention. The current implementation has no common automatic period for contact, booking and project data. This notice therefore does not state an invented deadline. Contact leya@leyagrowth.se for information about your data and to request deletion.
Login sessions and abuse-prevention records have technical validity periods and are cleaned up in bounded jobs or on requests. Customer sessions last at most eight hours, account setup/recovery session mode 15 minutes, and portal administration 15 minutes before multi-factor verification or one hour afterwards. Booking administration lasts eight hours. Portal rate-limit records expire after at most 30 minutes and booking rate-limit records after at most two hours; deletion may occur later at the next cleanup. Cookie and consent periods are listed in section 9.
Database and file copies may exist in provider backups and email services. Supabase backup periods depend on the plan and settings and cannot be established from the project code. The prepared custom backup tool includes a retention plan for 30 daily and 12 monthly snapshots, but the code marks the tool as not activated; this is not a verified actual retention period. An expired link or deleted cookie does not automatically erase these external copies.
13. Recipients and providers
Netlify provides the website and server functions. Formspree receives contact forms. Supabase provides database, authentication and private file storage. Loopia is used for email delivery in the production configuration. Google provides fonts and, where enabled, Calendar/Meet and consented Google Analytics. Meta and TikTok receive advertising measurement after marketing consent. Providers may use subprocessors and process information as processors or for their own purposes under applicable terms.
Project material is shown to authorized users at the relevant customer company and authorized Leya Growth administrators. Information may also be disclosed where legally required or needed for legal claims. Provider information: Netlify and Supabase. Contact us for information about processing agreements and safeguards for a particular service.
14. Transfers outside the EU/EEA
The reviewed booking configuration points to Supabase’s eu-north-1 region. A European database region does not mean all support, logs or subprocessors are in the EU/EEA. Formspree describes using infrastructure in the United States. Google, Meta, TikTok, Netlify and Supabase may also process data outside the EU/EEA depending on the service and subprocessors.
Such transfers require a basis under the GDPR, such as an applicable adequacy decision or standard contractual clauses with supplementary safeguards where needed. Project code does not show which agreements and account-specific safeguards are in place. Contact us for information or a copy of the safeguards for processing that concerns you.
15. Your rights
You can request access to your personal data, correction and, where the conditions are met, erasure, restriction and portability. You can object to processing based on legitimate interest. Contact leya@leyagrowth.se; we may need to verify your identity before disclosing information.
Analytics and marketing consent can be withdrawn through the cookie controls. This does not affect the lawfulness of earlier processing. We do not use contact, booking or portal information for solely automated decisions with legal or similarly significant effects on you.
16. Contact Leya Growth
Contact leya@leyagrowth.se to exercise a right or ask about personal data, retention, providers or this notice.
17. Complaints to IMY
You have the right to lodge a complaint with the Swedish Authority for Privacy Protection (IMY) if you consider that your personal data is processed incorrectly. See IMY’s complaint information.
18. Changes to this notice
We update this information when processing or services change. The last updated date is shown above. Changed purposes for optional tracking require renewed relevant consent.