Your information in the park.
What we collect, what becomes public, and how to reach us. Updated 6 September 2026.
Who is responsible
K & Stacks Oy, Finnish business ID 3531708-3, Unikkotie 11, 01300 Vantaa, Finland, is the controller for Silicon Village. Contact krister@inbot.io about your information.
What we use, and why
- Advertising and checkout: company or product name, website, tagline, colour, logo, building design, selected office, amount, payment/session references, optional contact email and terms acceptance records. We use these to take steps you request before a contract, supply your placement and support it (GDPR Article 6(1)(b)). When you act for a business, our legitimate interest in administering that business relationship covers your contact details (Article 6(1)(f)).
- AI previews: your description, property category, supplied company name, website hostname, tagline and optional colour go to OpenAI when the connected AI designer is used. Generated geometry is cached for reuse. The current request does not send your uploaded logo or payment details to OpenAI, and does not browse your website. The purpose is to make the preview you request (Article 6(1)(b)); business-contact information is handled under the relationship interest above.
- Payments, accounting and evidence: transaction references, amounts and relevant correspondence support accounting and legally required records (Article 6(1)(c)). Terms version, time and saved wording also evidence the agreement and help resolve disputes (our legitimate interest, Article 6(1)(f)). We do not receive full card details.
- Withdrawal notices: your name, email, payment reference and optional message are stored when you confirm, together with a numbered acknowledgment and server timestamp. We use them to record and handle withdrawal rights and related obligations (Article 6(1)(c)) and resolve the purchase (Article 6(1)(b)). Review uses a short-lived form token and a digest of the entered fields; it does not save the draft fields as a notice. Receipt links are private access links: anyone you share one with can read its contents.
- Support, content reports and security: correspondence, relevant content and technical request information help us answer you, protect the service and investigate misuse (legitimate interests, Article 6(1)(f), or Article 6(1)(c) when a legal duty applies). The application temporarily uses IP addresses to limit repeated requests. Office-link clicks increment an outbound-link counter. Separate first-party counters record visits and deliberate office-building selections. The browser supplies a random site/session identifier and, for each building selection, a random event identifier. The server stores aggregate totals and SHA-256 deduplication digests, not raw client identifiers, IP addresses, page URLs, referrers or user-agent strings in the analytics tables. Digests expire after 24 hours and are removed at startup or the next analytics event; totals remain. These figures are approximate visits and selections, not verified unique people. We do not maintain an advertising profile from those counters. Server error logs can include operational and payment references.
The online withdrawal form requires name, email and payment reference so we can handle the notice and contact you; the message is optional. If you cannot supply a reference, contact krister@inbot.io with enough information to identify your purchase. This does not remove your right to send a clear withdrawal notice another way. Do not send card numbers, passwords, identity-document copies or sensitive personal information through these fields.
What other visitors can see
Your advertising name, website, tagline, logo, design, paid amount and start time are public. Previous-resident history keeps the name, website, amount, time, colour and available logo after an outbid. The former full design and tagline are not part of that history. Public pages may be copied or indexed by others. Receipt emails, private payment references, acceptance records and withdrawal notices are not public listings.
Current placement is part of the service contract. Continuing identifiable information in resident history relies on our legitimate interest in an accurate record of the park and the advertised history feature, subject to your rights and a balancing assessment. Ask us about correction, objection or removal; purchasing does not waive those rights.
Providers and transfers
Stripe processes checkout/payment information under its applicable processor and independent-controller roles; see Stripe's privacy notice. OpenAI processes the preview inputs listed above; see OpenAI's privacy information. The API request uses store: false; this setting is not a promise of zero provider retention or a statement about all provider data uses.
Google's favicon service receives the advertised website hostname when the server requests a fallback logo. Other park pages currently load Google Fonts, which involves a visitor's browser connecting to Google. This privacy page and the withdrawal flow load only local assets. Hosting and infrastructure providers process requests, network information and stored data as necessary to operate the site; their final identities and locations have not yet been confirmed for production.
Some providers may process information outside the EEA. Before launch we must verify and document the actual processing locations, contracts and applicable transfer mechanism, such as an applicable adequacy decision or standard contractual clauses with any required additional measures. We do not currently claim that all information stays in Finland or the EEA. Ask krister@inbot.io for the arrangements and a copy or description of applicable safeguards. Authorised advisers or authorities may receive relevant records where necessary for accounting, disputes or legal obligations.
How long information stays
- Design cache: the current application reuses cache entries only while they are less than seven days old, and caps the cache at 256 entries when writing. Age-based reuse is not age-based erasure: old rows may remain until replacement or cleanup. A seven-day deletion policy, backup treatment and cleanup of separate AI usage/cost records still need operational implementation. Purchased public designs follow placement/history rules rather than the preview-cache period.
- Financial records: the intended schedule follows Finnish accounting categories: vouchers and relevant transaction correspondence generally at least six years from the end of the calendar year in which the financial year ended; financial statements, accounting records and specified core records at least ten years from the end of the financial year. These are category-specific minimums, not a blanket ten-year rule for every claim field. The operator/accountant still needs to map records, remove unnecessary personal fields and implement expiry and backup handling. Current claim storage has no timed deletion job.
- Public advertising/history: while we offer the corresponding feature, subject to rights requests, moderation and review of continued necessity. The current code does not automatically expire history. Private financial retention does not require keeping a logo or personal name publicly visible.
- Withdrawal/support records: for handling the request and necessary legal/accounting evidence afterwards. A category-specific closure, review and deletion schedule remains to be implemented; confirmed notices currently have no automatic expiry. Unsubmitted form-token records expire after 24 hours and are removed when another form is opened. The flow does not automatically send an email; keep the downloadable acknowledgment.
We may retain necessary records longer for a concrete legal obligation or unresolved claim, with access restricted as appropriate. Retention decisions and deletion from backups need operational review; the targets here must not be read as completed automation.
Cookies, choices and your rights
The application does not set marketing cookies or analytics cookies and does not offer marketing subscriptions. First-party visit counting can use a randomly generated identifier in this browser tab’s session storage; it is not derived from your device or shared with an analytics provider. Closing the session or disabling browser storage can change how visits are deduplicated. This description does not by itself establish an exemption from applicable consent requirements; the operator must review the final storage and disclosure setup before public launch. After checkout starts, this browser tab uses session storage to keep your private confirmation download link for your return from Stripe. Your browser also saves the private owner access token in local storage so you can return to manage your purchased office. You can remove it in your browser settings; keep your private purchase confirmation to regain access. The server stores a hashed owner access token and up to three saved design choices per purchase. It is not an advertising tracker. The withdrawal flow does not use cookies or browser storage. Stripe's hosted checkout and external websites have their own information and cookie practices. Accepting the park's terms or requesting immediate display is not marketing consent.
You can request access, correction, deletion, restriction and, where applicable, portability; you can object to processing based on legitimate interests. If we ever rely on consent, you can withdraw that consent without affecting prior lawful processing. Contact krister@inbot.io; we may need proportionate information to verify that the request concerns you. Rights have legal limits, including necessary accounting records. We normally respond within one month, and explain any lawful extension.
You can complain to the Finnish Data Protection Ombudsman or your competent supervisory authority. The current withdrawal intake makes no automatic decision about eligibility or refunds. AI generates a preview; it does not decide your withdrawal rights.
Keep a copy
Read the current terms or download the current terms. These are the current public terms; an earlier purchase may have a different accepted version. Use Withdraw from contract to review and submit a notice.