Privacy policy
What personal data staffbite.fi processes: request logs, form messages, AI architect conversations and retention periods. Cookieless visitor analytics, no tracking cookies.
This policy describes the site as it is now. The site has cookieless visitor analytics (Umami) but no tracking cookies (Privacy). The only cookie is the AI architect's __Host-sb_chat, which is set only when you send your first message to the architect.
Personal data is processed in four situations: when the server delivers a page to your browser, when you send a message with the contact form, when you talk with the AI architect and when you send us email.
Updated
Controller
Staffbite Oy, business ID 2774047-1, Helsinki, Finland.
Questions and requests about privacy: karo@staffbite.fi.
What data we process
Contact form
When you send a message with the form on the contact page, we process your name, email address and message, and your company and phone number if you give them. Company and phone number are optional. We use the data to reply to your message and to manage a possible customer relationship.
The message is stored in Staffbite's PostgreSQL database in UpCloud's Helsinki data centre (Location and data).
After storage, Lettermint B.V. (Netherlands) delivers a notification of the message to Staffbite's own email, karo@staffbite.fi. The notification contains the form's details. Lettermint processes and stores the data in the EU and by default deletes the content of the notification after 28 days. Its technical logs are usually kept for at most 14 days (Lettermint data retention). Our email is in Google Workspace, so the form's details also pass through Google in the same way as email messages.
The form does not send a confirmation message to the email address you give. After sending, the page shows a thank-you notice.
The server uses your IP address to limit the number of submissions in order to prevent misuse. The address is kept only in the server's memory, and it is not stored with the form's details (Privacy). Submitting the form leaves the same details in the request log as any other request, with the IP address shortened. The form's content, such as your name, email address or message, is not written to the logs.
Email messages
When you send us email, we process your name, email address and the content of the message, as well as any other information you give in it. We use them to reply to your message and to manage a possible customer relationship.
The site's email link opens your own email program. The message travels as email, not through the site's server.
Using the site
When you open a page, your browser sends technical details to the server, such as your IP address and your browser's user agent. The server needs them to deliver the page.
The server's request log records the time of the request, the address, the response status and the browser's user agent. The IP address is shortened before it is stored (Privacy): the last part of an IPv4 address and the end of an IPv6 address are removed, so that an individual device cannot be identified. The logs are used to investigate faults and misuse, and they are deleted after 14 days.
Fonts, scripts and other content come from the site's own server. The only exception is our own visitor analytics, described just below. The only cookie is the AI architect's conversation cookie, described under AI architect.
If you choose the dark or light theme, the choice is stored only in your browser's local storage (localStorage). It is not sent to the server.
Visitor analytics
We follow how the site is used with Umami, software we run ourselves at stats.experiencelevi.fi. The same Umami also serves the experiencelevi.fi site. The server is in Hetzner's data centre in the EU. When you open a page, your browser loads Umami's script from there. The script sends the page's address and title, the address of the previous page (referrer), the screen size and the browser language to the same server. From the request, the server works out the browser, operating system, device type, country, region and city.
Umami sets no cookies and does not store the IP address in its database. It links the visits from the same browser and IP address within a calendar month with an identifier calculated from the IP address and the browser's user agent with a salt that changes every month, so visits cannot be linked for longer than a month. If your browser sends a Do Not Track request, the script sends nothing. Analytics is off on the share pages of solution sketches, because their address is the key to the sketch. On the Prosessistudio page Umami also counts, as named events, clicks on the Request a pilot button, the Sign in to the pilot link and the pilot form's send button. An event stores its name with the same visit data as a page view, but not the form's content.
We use the statistics to develop the site: we see which pages are read and where visitors come from, including AI services. Analytics does not see the content of conversations or forms.
AI architect
The AI architect is an AI assistant that answers questions about Staffbite's services based on the site's public content. We process the conversation in order to answer your question, to improve the architect's answers and the site's content and to investigate misuse.
What is stored and who reads it
Conversations are always stored, and Staffbite can read them (Privacy), even if you do not send your contact details. We store your messages and the architect's answers, the page of the site from which you opened the architect, technical details of each answer (the model name, token counts, cost and response time), the cards shown with the answer including their content (for example the contact card's summary and the EU readiness assessment), and the conversation's solution sketches. Conversations are in Staffbite's database in UpCloud's Helsinki data centre.
If you write an email address or a phone number in a message, the server replaces it with the marker [sähköposti] or [puhelin] (Finnish for email and phone) before the message is stored or sent to the model. Other information, such as names, is not masked, so do not write sensitive information in the conversation.
The conversation does not store your IP address, your browser's user agent or the external page you came from. The server uses the IP address to limit the number of messages, as with the form, but the address is kept only in the server's memory. The content of the conversation is not written to the logs.
Solution sketches and share link
Based on the conversation, the architect can draft a solution sketch that describes your situation, your goal and a proposed way to implement it. The sketch is produced by AI, and it is not an offer. It is stored with the conversation in the same database, and Staffbite can read it just like the conversation.
Each sketch has a share link with a random identifier. Anyone who has the link can open the sketch without signing in, so share the link only with people you want to see it. The sketch page is marked noindex for search engines (Privacy), and it is not in the sitemap or the llms.txt files. The page sets no cookie, the browser does not cache it, and a link opened from the page does not reveal the sketch's address to the next site.
The sketch is not emailed to you or to anyone else, unless you send a contact card yourself.
EU readiness assessment
The architect can make an indicative EU readiness assessment of your AI use case: what kind of data the use case involves, where it is processed, which providers are involved and what the AI Act might require. The assessment is based on what you say in the conversation and on the site's public content. It is produced by AI, and it is not legal advice.
The assessment is stored with the conversation like the other cards, and it is kept and deleted together with its conversation. Staffbite can read it just like the conversation.
Conversation cookie
When you send your first message to the architect, the site sets the cookie __Host-sb_chat. It contains a random identifier that lets the server find your conversation when you come back, and the database stores only a hash of the identifier. The cookie is valid for 30 days (Privacy), and the page's JavaScript cannot read it. It is necessary for continuing the conversation, and it is not used for tracking or analytics.
Contact card
With the architect's contact card you can send Staffbite your email address and, if you wish, your name, company, phone number, a message and how you would like to be contacted. A sent card is processed and stored in the same way as a message sent with the contact form, and Lettermint delivers a notification of it to Staffbite's email in Google Workspace. The conversation is attached to the contact request, and its last 8,000 characters at most, together with links to the conversation's solution sketches, are included in the notification. No email is sent to you.
The card the architect offers may include a section called “What I understood about your needs”: your need, company size, timeline and role. The AI infers these profile details from the conversation, and it has been instructed to use only what you have said. You see the details in the card before sending, but you cannot edit them. If you send the card, the profile details are stored with the contact request in Staffbite's database in UpCloud's Helsinki data centre, and they are included in Staffbite's notification. They are kept with the contact request for 24 months. If they are wrong, you can say so in the card's message. The message does not change the stored details, but you can ask for incorrect information to be corrected or deleted at karo@staffbite.fi. If you do not want them included at all, you can use the contact form, whose messages have no profile details attached.
Internal summary of a contact request
When you send a contact card from an architect conversation, Staffbite may make an internal summary of it with Google's Gemini model in Vertex AI's EU multi-region. The summary helps us prepare to reply to your contact request. No summary is made if the architect is taking a break, the daily limit for summaries is reached or the conversation is very short. No summary is made of messages sent with the contact form.
The model receives the card's message and your preferred contact method, the page from which you opened the architect, the conversation masked in the same way as in the notification (at most its last 8,000 characters), the conversation's solution sketches and the site's public content about our services and scopes. The card's name, email, company and phone fields are not sent to the model. However, what you have written yourself in the card's message and in the conversation is included: the card's message is sent as it is, and in the conversation only email addresses and phone numbers are masked. Names are not masked, so do not write sensitive information in the message or the conversation.
The summary contains a short description of your need, an assessment of how well your need fits our services (a number from 0 to 1 with reasoning), an assessment of which of our services would fit and how large the work would be, a suggested next step, questions for the first conversation and possible risks. It may also include the size of your company, your role and the timeline, if you have mentioned them. Otherwise they are marked as not known. The summary has no price.
The summary is stored with the contact request in Staffbite's database in UpCloud's Helsinki data centre, and only Staffbite reads it. It is not sent by email. The summary is a working tool: no automated decisions are made on its basis; a person reads the contact request and decides how we reply. The content of the summary is not written to the logs.
Retention and deletion
A conversation from which you do not send a contact card is deleted automatically 6 months after the last message. A conversation attached to a contact request is kept with the contact request for 24 months and then deleted. Solution sketches are kept and deleted together with their conversation, and their share links then stop working. EU readiness assessments and the other cards are also kept and deleted together with their conversation. The internal summary is kept with the contact request for 24 months and deleted with it.
By choosing Delete conversation below the conversation, you delete the conversation with its messages and solution sketches from the database immediately, and the cookie from your browser. A contact request you have already sent, with its profile details, and the internal summary made of it remain, and a notification already sent remains in email like other email messages. The Start a new conversation button only removes the cookie, and the old conversation and its sketches are deleted under the normal retention period. Once the page no longer recognises your conversation, you can ask for it to be deleted at karo@staffbite.fi.
The database is backed up every night. Staffbite keeps its own backups on its UpCloud server in Helsinki for 14 days, and the backups of UpCloud's database service are kept for 3 days. Data that has been deleted, by you or at the end of its retention period, may therefore remain in backups for up to 14 days. Backups are used only to restore the database after a failure or a mistake.
Google Vertex AI
The answers, solution sketches, EU readiness assessments, the contact card's profile details and the internal summaries of contact requests are produced by Google's Gemini model in Google Cloud's Vertex AI service, so the conversation is passed to Google for processing. We use Vertex AI's EU multi-region, so the model's processing takes place in EU member states (Google Cloud: Vertex AI data residency). However, Google is a US company, so the US CLOUD Act applies to it regardless of where the data is.
Google does not use customer data to train models without permission. However, Vertex AI's caching is on by default: the in-memory cache is cleared within 24 hours at the latest, and the persistent cache is also on by default. Google may also log prompts to detect abuse (Google Cloud: Vertex AI data governance). We do not use grounding with Google Search, because it stores search logs for 3 days.
Where the data is
| Service | Used for | Location | Company's home country |
|---|---|---|---|
| UpCloud | the site's server, database, technical request data, messages sent with the form, and the AI architect's conversations, solution sketches and internal summaries of contact requests | Helsinki data centre (Location and data) | Finland |
| Lettermint | notification to Staffbite of a message sent with the form or the architect's contact card | EU (Netherlands and Germany) | Netherlands |
| Hetzner (self-hosted Umami) | visitor statistics | Hetzner's data centre in the EU | Germany |
| Google Workspace | email karo@staffbite.fi, including notifications of form messages and architect contact requests | Google's data centres | United States |
| Google Cloud, Vertex AI | the AI architect's answers, solution sketches, EU readiness assessments, the contact card's profile details and internal summaries of contact requests with the Gemini model | EU multi-region, processing in EU member states (AI processing) | United States |
Google may also process email data outside the EU. Processing in Google Workspace is based on Google's data processing terms (Cloud Data Processing Addendum).
We describe our dependencies in more detail on the EU-first page.
Legal bases and retention
| Data | Legal basis | Retention |
|---|---|---|
| server request log | legitimate interest: the site's security and functioning | 14 days, IP address shortened |
| visitor statistics (Umami) | legitimate interest: developing the site and following visitor numbers | 24 months, after which they are deleted; the statistics contain no IP addresses, and the visit identifier changes every month |
| database backups | legitimate interest: restoring data after a failure or a mistake | Staffbite's own for 14 days, UpCloud's database service's own for 3 days; deleted data leaves the backups within 14 days at most |
| messages sent with the contact form | legitimate interest: replying to the contact request; steps prior to a contract when the message concerns an offer or an assignment | 24 months from sending, after which the message is deleted from the database automatically |
| AI architect conversations and the cards shown in them, such as EU readiness assessments | legitimate interest and your request: answering your question, improving the architect and the site's content, and investigating misuse | 6 months from the last message, after which the conversation is deleted automatically; immediately when you choose Delete conversation |
| the architect's solution sketches | as for conversations | with the conversation: 6 months from the last message, or 24 months when attached to a contact request; immediately when you choose Delete conversation |
| data sent with the architect's contact card, including the profile details (What I understood about your needs), and the conversation attached to it | as for contact form messages | 24 months from sending, after which they are deleted from the database automatically |
| internal summary of an architect contact request | as for contact form messages | with the contact request, 24 months from sending |
the architect's cookie __Host-sb_chat |
necessary for continuing the conversation | 30 days, or until you start a new conversation or delete the conversation |
| email messages, including notifications of form messages and architect contact requests | legitimate interest: replying to the contact request; steps prior to a contract when the message concerns an offer or an assignment | 24 months from the last contact, unless the message is needed for longer because of a contract or accounting |
Your rights
Under the General Data Protection Regulation you have rights such as the right to:
- know what data we process about you and get a copy of it
- ask for incorrect data to be corrected
- ask for your data to be deleted
- ask for processing to be restricted and object to processing
Send your request to karo@staffbite.fi.
If you think your data is being processed unlawfully, you can lodge a complaint with the Office of the Data Protection Ombudsman in Finland (tietosuoja.fi).
Changes to this policy
We will update this policy before we introduce new processing, sub-processors or AI features. The date of the update is shown at the top of the page.
Get in touch
Start planning now
Tell the AI architect what you are planning. It answers right away and can put together a solution sketch from the conversation that you can share with your team.
- karo@staffbite.fi
Staffbite is based in Helsinki (Location and data). Read about EU-first