Intspec
FeaturesPricing About
Sign in Join the waitlist
Resources Guides Schedules, spec sheets, the paperworkFAQs What studios ask firstSupport A person answers, within two days
Who it is for For architects The schedule for the set, from the linksFor interior designers Spec sheets from the links you already have
Something not answered here? Write to us
Legal

What Intspec holds, and for how long.

The privacy policy in full: what the service holds, why, and how to get it back or have it deleted.

PrivacyTermsSubprocessors
Last updated 2026-11-06

Who is responsible

Intspec is operated by Marko Rimár, a sole proprietor established in Slovakia. For the purposes of the General Data Protection Regulation (GDPR) the operator is the data controller. For anything on this page, write to hello@intspec.studio.

Intspec is offered to businesses and professionals. If you are using it in a business capacity, the data you put in about your suppliers and clients is yours, and we process it on your instructions to provide the service.

What we hold

Your account

  • Email address, display name, and a hashed password (never the password itself).
  • Your country, time zone, language and currency. We set them at sign-up from your browser's time zone and language and the country Cloudflare reports for the request, and you can change them in Settings.
  • Studio details, if you enter them in Settings: name, address, email, phone, website and a logo. They print on your schedules.
  • Session records: when you sign in we store the IP address and browser identifier of the session alongside it. A session stops working after 7 days of inactivity.
  • Email verification and password-reset tokens, valid for one hour.
  • Security counters that limit sign-in and password-reset attempts and the use of heavy features. They are keyed by a hashed email address, a hashed IP address or your user id, and pruned after 48 hours. The sign-in library keeps a short-lived counter per IP address and path for the same purpose.

What you put in

  • The supplier links you paste, with the page title, domain and product image address we read from them, and the name of any file you imported links from.
  • Projects, schedules, categories, fields, notes and the values in them, including edits you make.
  • The values our extraction produced for each link (name, supplier, brand, code, type, dimensions, material, finish, price, image address) with a confidence for each.
  • Share links you create. A link you make in Share ends after the 7, 30 or 90 days you choose, or runs until you turn it off. The link printed as a schedule's QR code never expires: it runs until you hide the QR code, and anyone holding the printed sheet can open it. We note when each link was last opened. Links are stored hashed, and a public link also as an encrypted copy so that you can copy it again. The key is not in the database, so a copy of our database does not contain working links. The record of a link stays after the link ends.
  • The email addresses and names of the people you invite to a project. Those addresses belong to third parties, so you are responsible for having a basis to share a project with them. A person's own link works for 90 days from the invite. A new invite starts the 90 days again and ends the old link. Each invite also saves the address and name in your People address book, which suggests them next time. Removing someone from People only takes them out of the suggestions. Their link is ended in Share.
  • Through their own link, a client may approve items, ask for changes and comment, and a contractor may comment. Each of those marks is stored with their address and the time, as part of your project, and stays after you remove the person or the link expires, until you delete the project. The people you invite see each other's marks, under the name you gave them or their role, never their address. A public link shows none of them.
  • PDFs you generate. An Items PDF is kept until you export the same project again, or for 7 days. A schedule's PDF is a kept version: the file and the document behind it, with the values and studio details as printed, stay until you delete the schedule, the project or the account, with no time limit. Deleting a version takes it off your list and ends its download. Its file is deleted 30 days later, until when Undo can bring it back, and the document behind it stays until the schedule, the project or the account is deleted.

Supplier pages we read

When Intspec reads a supplier page it keeps a digest of it in a shared cache: the title, headings, description text, product data, prices and image addresses found on the page, with what the language model read from them. The whole page is not kept. An entry holds the page's address and nothing about you or your account. For 24 hours it serves any account that extracts the same link, so the page is not fetched or read again. It is dropped 7 days after the page was last fetched.

What we do not keep

  • Questions you ask the assistant and its answers are not stored. They are sent to the language model for the answer and dropped.
  • Files you import are read in your browser. Only the links or the text extracted from them reach our servers. The file itself does not.
  • No payment card details. Payments, when paid plans open, are handled by our payment provider.

Billing and usage

  • Your plan and an append-only ledger of extraction allowance, its grants, reservations and refunds.
  • Usage records for each extraction. The supplier's domain, how the page was processed, whether it succeeded, and the cost and token counts of the provider calls involved.

Errors and logs

Server errors are reported to Sentry (EU region) with the technical context needed to fix them. We do not switch on Sentry's personal-data defaults, and no error tracking runs in your browser. Our hosting provider keeps standard request logs for a short period.

The waitlist

If you leave an email address on the marketing site before early access opens, the site sends that address, the page it came from and the time as one email to our support mailbox (hello@intspec.studio, at Proton), through Resend. If you answer the optional second step, your team size and your question go the same way. That mailbox is the whole list. Nothing is stored on the site or in the application. The purpose is one message when early access opens and at most one update a month before that, and an answer if you asked something. The legal basis is your consent, which you can withdraw at any time by writing to hello@intspec.studio. The list is deleted no later than six months after early access opens.

Cookies and local storage

The application sets eleven cookies of its own:

  • The session cookie keeps you signed in. It is marked Secure and HttpOnly and lasts 7 days from your last use.
  • Two project cookies, app_last_project and app_recent, remember the project you opened last and the ones before it, by project id, so that the app can return you there and order the sidebar. They are HttpOnly and last a year.
  • Eight display preferences remember how you left the screen: app_rail and app_side (the sidebar), app_sched_settings (a schedule's settings), app_view and app_cols (the Items table), app_projects (the Projects page), and app_library and app_library_pick (the Library and its picker). They hold settings only, are written by your browser, and last a year.

The app_ cookies go only to the application. They stay after you sign out, until they run out or you clear them. None of the eleven is used for analytics or advertising, so the application shows no consent banner. There are no third-party cookies, the application loads no third-party scripts, and its content security policy forbids them. A person who opens a share link gets no cookie.

Your browser's local storage holds a few cosmetic preferences (for example which settings groups were open) and the recent list in Search, which is ids of what you opened. They never leave your browser. A note you are saving waits in that tab's session storage until the server confirms it.

The marketing site (intspec.studio, not the application) uses Cloudflare Web Analytics to count visits. It is cookieless. The script sends the page, the referrer, the browser and country, and page-load timings to Cloudflare, stores nothing on your device, and does not identify or follow you across sites. That is why there is no consent banner. The legal basis is our legitimate interest in knowing whether the site is found and which pages are read. The waitlist form keeps your address in that tab's session storage so that the second step can send it.

Why we process it, and on what basis

  • To provide the service you signed up for (GDPR Article 6(1)(b)): your account, your projects, extraction, documents and shares.
  • Our legitimate interest in running a secure, working service (Article 6(1)(f)): session and rate-limit records, error reports, usage records that tell us what an extraction costs and where it fails.
  • Legal obligations (Article 6(1)(c)): invoicing and accounting records once paid plans open.

We do not use your data for advertising, profiling or automated decisions with legal effect.

Fetching supplier pages on your behalf

When you paste a link, Intspec takes one free look at that page, on your instruction, to show its name and picture in the review. It skips that look if it read the page in the last day, or if the shop is known to need our paid page-fetching provider, Zyte. Nothing paid runs until you press Extract. Then Intspec fetches the page, unless the cache described above already holds it, and the language model reads it.

The supplier's site sees a request from our servers (or from Zyte), not from you. We read only the page behind each link and never crawl a site. One check runs without a link from you: every six hours, for each shop that has refused all our fetches, at most ten shops a run, we fetch one product page already extracted there, to learn whether the shop can be read again. Nothing of any account goes with that request.

Product images on your board and on share pages are shown straight from the supplier's servers, so the supplier sees the viewer's browser request for the image, as it would on the supplier's own site. PDF exports fetch images through our servers, and the PDF contains them.

The language model and your data

The language model that reads supplier pages, imported text and assistant questions is reached through OpenRouter's EU endpoint under a zero data retention arrangement. In plain terms, four things hold:

  • No retention. Inputs and outputs are not stored by the model provider beyond the processing of the request. Every request we send carries the zero data retention instruction, so it is routed only to model endpoints that keep neither prompts nor completions, and is refused rather than routed anywhere else.
  • No training. Inputs and outputs are not used to train, fine-tune or otherwise improve any model. This is fixed in OpenRouter's Data Processing Agreement, which forms part of the terms we have accepted, and enforced again on every request, which excludes any provider that trains on request data.
  • No prompt logging. Request and response logging on our OpenRouter account is switched off. Our own record of each request holds token counts, cost and timing, never the content.
  • EU processing. Requests go to an EU-only endpoint and the model runs on infrastructure in the European Union. OpenRouter, Inc. is a United States company. The processing is governed by its Data Processing Agreement and the European Commission's standard contractual clauses.

Who else processes your data

We use a small number of service providers, each bound by a data processing agreement. The current list, with what each one receives and where it runs, is at intspec.studio/subprocessors. The model that reads your pages and answers your questions runs on EU infrastructure through an EU-only endpoint. Some providers (the page-fetching provider, the code and backup host) run outside the European Economic Area. For those we rely on the transfer safeguards in their data processing terms, which are the European Commission's standard contractual clauses or, for US providers certified under it, the EU-US Data Privacy Framework. We do not sell data and we do not share it with anyone else, except when the law requires it.

Email we send

Seven kinds. An address verification when you sign up, a welcome once the address is verified, a password reset when you ask for one, a notice when your password changes, a note when a paid plan has used about 80 % of its month's extractions (once a month at most), the invite when you share a project with a person, and the launch note (and an answer to your question) if you joined the waitlist. The first six are sent from noreply@intspec.studio through Resend (EU region). Replies to the first five reach hello@intspec.studio. The invite goes to the address you typed, a third party, and carries your name, the project's name and their link. A reply to it reaches you. The launch note and answers are written from hello@intspec.studio. Beyond these we write to you only if a change to the terms, prices or these providers needs it.

How long we keep it

  • Your account and everything in it: for as long as the account exists.
  • Waitlist addresses: kept in the support mailbox no later than six months after early access opens, or deleted as soon as you ask.
  • Sessions: a session stops working 7 days after its last use, and its record, with the IP address and browser identifier, is deleted within hours of that. Signing out, removing it in Settings or deleting the account ends it sooner. Rate-limit counters: 48 hours. Background job records: 7 days, or 30 days for a job that failed for good.
  • Projects, links, values, share records and the marks made through share links: until you delete them or the account. A share link stops working when its time is up, as described above, and a QR link has no time limit. Items PDFs: 7 days. Schedule PDFs and the document behind each: until you delete the schedule, the project or the account, and 30 days for the file of a version you deleted. The copy Extract again keeps for its Undo: one day. Supplier pages in the shared cache: 7 days after the page was last fetched. Per-page extraction telemetry (which fetch method ran, how long, whether it succeeded): 180 days.
  • Encrypted database backups: 14 days, then deleted. Data you delete may therefore survive in a backup for up to 14 days. Backups are encrypted and used only to restore the service.
  • Usage and cost records are kept for accounting for 400 days, including after an account is deleted, with the link to the account removed. Notices from the payment provider about your payments carry your email address: after the account is deleted, each is emptied once it is 90 days old, and only the record of what was paid or refunded, and when, stays.

Your rights

Under the GDPR you can access, correct, export, restrict, object to, and erase the personal data we hold about you, and complain to a supervisory authority. In the app:

  • Export. Settings offers a JSON export of your profile, projects, library, shares (including recipient addresses), People address book, sessions and billing ledger. PDF files and the logo image are not in it.
  • Delete. Settings deletes the account after you re-enter your password. This removes your projects, links, values, shares, recipient lists, address book, PDFs, billing account and ledger immediately.
  • Correct or change an email address, restrict or object. Write to hello@intspec.studio from the address on the account. We answer within a month, as the GDPR requires, and usually much sooner.

The supervisory authority for the operator is the Office for Personal Data Protection of the Slovak Republic (Úrad na ochranu osobných údajov SR, dataprotection.gov.sk). You may also complain to the authority in your own country.

Changes to this policy

When the service changes in a way that changes this page, we update it and the date at the top, and write to the address on your account if the change matters to you.

Intspec

Links in. Specs out.

Product FeaturesPricingFor architectsFor interior designers
Resources GuidesFAQsSupport
Company Early accessAboutPrivacyTermsSubprocessors
© 2026 Intspec Hosted in the EU
Intspec