Privacy Statement

We collect what we need to reply.
Nothing extra for the sake of it.

This statement covers spentalabs.com and the email that comes from it. Client work is governed by the agreement you sign with us, including any data-processing terms in that engagement.

Effective October 15, 2026 Austin, TX 78701

01 / Snapshot

The short version.

If you only read one screen, make it this one. The rest is the same story with the legal bases filled in.

01

Contact

Name, work email, and the message you send. We use it to reply.

02

Blog subscribe

Just an email, if you opt in. You are on the list as soon as you submit. We send a confirmation note; silence is the confirm, unsubscribe if it was a mistake.

03

Stays in your browser

Listen uses your device’s speech engine. Share buttons send you to LinkedIn, X, and the rest. Not through our servers.

04

What we don’t do

We don’t sell personal data, run ad trackers on this site, or buy lists. No account is required to read the public site.

Who we are

Controller

Spenta Labs (“we,” “us”) operates this site from Austin, Texas. For privacy questions about the website, email hello@spentalabs.com. We are a small studio. There is no separate data-protection officer; that inbox is the right place.

02 / Collection

What we collect

We collect information in these situations:

  • Contact form. Name, email, and message. The Contact form is meant for work inquiries, so personal webmail addresses (Gmail, Yahoo, and similar) may be declined. Use a work email, or write us directly.
  • Blog subscribe. Email address only, if you opt in on the blog. Personal addresses are fine there. Submitting puts you on the Signals list immediately. We then email a confirmation that treats doing nothing as the opt-in, with a one-click unsubscribe if you did not mean to join.
  • Direct email. Whatever you include when you write hello@spentalabs.com or reply to us.
  • Hosting logs. Standard server records such as IP address, browser type, referring URL, and timestamps. Our host keeps these to run and secure the site.
  • Site operation. WordPress may set cookies if you log in (administrators). Public readers do not need an account. We store aggregate post view counts; those are not tied to you.
  • Courses or accounts (if you enroll later). If we open training or a product that requires an account, that service will collect what it needs to run (typically name, email, and progress). We will update this statement when that happens.

We do not scrape extra profile data off the public internet to attach to your inquiry. We do not require payment details on this site.

03 / Use

How we use it, and on what basis

We use the information above to:

  • Reply to inquiries and decide whether an engagement is a fit.
  • Send Signals posts if you subscribed, and stop when you unsubscribe from an email or write us.
  • Operate, secure, debug, and improve the site.
  • Meet legal, tax, or accounting duties if a conversation becomes a contract.

If you are in the EEA, UK, or a similar regime, we rely on:

  • Consent : blog subscribe (form submit, confirmed by the follow-up email unless you unsubscribe), and any optional cookies we may add later.
  • Legitimate interests : answering a message you sent, keeping the site secure, understanding which posts are read (in aggregate).
  • Contract : if we work together, the information needed to perform that agreement.
  • Legal obligation : when the law requires us to keep or disclose records.

Listen on blog posts uses the Web Speech API in your browser. We do not receive the audio or the article text from that feature.
Share buttons open LinkedIn, X, Facebook, or Bluesky with the post title and URL; those companies then handle the visit under their own policies.

04 / Cookies & similar

Cookies, fonts, and analytics

  • Essential. WordPress login and admin cookies for people who sign in to manage the site. The public site does not require them.
  • SEO. We use Rank Math to manage titles, descriptions, and related metadata. It does not run an advertising network on our pages.
  • Fonts. Type is loaded from Google Fonts. Google may see your IP address and browser data when the font files are requested. You can block third-party requests in your browser if you prefer system fonts.
  • Analytics and ads. We do not currently run a marketing pixel or sell inventory on this site. If we add privacy-respecting analytics later, we will name the tool here and, where required, ask first.

You can block or delete cookies in your browser. Essential admin cookies are needed only if you log in. Do Not Track and Global Privacy Control signals: we do not sell or share personal information for cross-context advertising, so there is nothing extra to opt you out of on that front.

05 / Sharing

Who else sees it

We do not sell personal information. We do not share it for cross-context behavioral advertising.

We use processors who help us run the studio:

  • Hostinger : website hosting.
  • Email delivery : transactional mail (including form notifications) via our mail plugin and its provider (currently Resend).
  • Signals list : subscriber addresses, signup time, and unsubscribe state are stored in Resend, which also delivers the confirmation note and post broadcasts. WordPress does not keep a second mailing list.
  • Google : font delivery, as above.

They process data on our instructions, not to build their own marketing profiles from your inquiry. We may also disclose information if the law requires it, to protect people or the studio, or as part of a merger or asset sale, in which case this statement still applies until you are told otherwise.

This site is hosted in the United States. If you contact us from elsewhere, your information is transferred to the U.S. so we can answer. Where a processor offers standard contractual clauses or a comparable transfer tool, we rely on that. Sending a form or email is how you ask us to receive the message.

We keep contact messages as long as we still need them to reply, follow up, or keep a reasonable business record, then delete or archive them. Subscribe records last until you unsubscribe. Hosting logs follow the host’s default retention.

06 / Rights

Your rights

Depending on where you live, you may have the right to access, correct, delete, or export personal information we hold; to restrict or object to certain processing; to withdraw consent (that does not undo work already done); and to complain to a supervisory authority. In California and similar U.S. states you may also request to know, delete, or correct, and to opt out of “sale” or “sharing”, we do not sell or share as those laws define it, and we will not discriminate against you for exercising a right.

Email hello@spentalabs.com with the request and enough detail to find you (the address you used is usually enough). We may need to verify who you are. Authorized-agent requests should include proof of authority.

This site is not directed at children under 13, and we do not knowingly collect their data. If you think we have, write us and we will delete it.

We use reasonable administrative and technical measures for a studio site of this size. No website is perfectly secure. Do not send passwords or payment card numbers through the contact form.

07 / Updates

Changes and how to reach us

We will update this page when our practices change and bump the date at the top. Material changes will be obvious here; we do not bury them.

Spenta Labs
Austin, TX 78701 USA
hello@spentalabs.com

This is our public website statement, not legal advice, and not a substitute for the contract on a paid engagement. If something here conflicts with a signed agreement, the agreement controls for that work.

Still a question?

Write us.
We’ll answer the actual question.