Privacy Policy

TECHi (techi.com) is a product published by TechAbout LLC, registered at 30 N Gould St Ste R, Sheridan, WY 82801, United States. There is no TECHi Media LLC. When this policy says “we,” that is TechAbout LLC. When it says “you,” that is anyone visiting the site, reading the newsletter, or holding a TECHi account.

TECHi is an AI and markets publication with reader accounts, a personalized dashboard, watchlists, analyst subscriptions, paid Stripe checkouts, and TECHi Learn courses. It is not only a news site. This policy describes those products.

There are five buckets. Anything not in one of these is not collected.

1. Account, sign-in, and newsletter

Creating a reader account asks for a name, email address, and password. The password is stored as a one-way hash and used only to sign you in. Google or GitHub sign-in sends us the basic profile those providers share: name, email, avatar URL, and account ID. A newsletter subscription stores the email you typed and whether you are still subscribed. Writing to us stores the message. Email is collected from registration, sign-in, newsletter signup, checkout, Learn, and contact forms. It is not collected only through comments or a direct email.

2. What you do while signed in

Comments, follows, bookmarks, stock votes, watchlist entries, reading history, and dashboard preferences. Two-factor backup codes are stored hashed. An analyst application stores the form you submit. An analyst subscription stores the subscription state. None of this is used as a silent marketing list.

3. TECHi Learn

A paid or free Learn seat stores the enrollment: which course, who paid, progress, and certificate state. We do not store the card number. A TECHi account is for someone 16 or older. A younger learner does not get a login.

• The TECHi account belongs to a parent or guardian who is at least 16. The child does not get a login.
• The guardian confirms they are the parent or legal guardian and consent to the child taking the course.
• The child is a profile on that account: first name and age band only.
• The guardian chooses whether the child profile, projects, or certificate can be shown publicly.
• Instructors message the guardian account. They do not contact the child directly.
• Live sessions follow the classroom safety rules: no private child contact, no public chat with strangers, and a guardian can sit in.
• The guardian pays. A child cannot check out.
• A certificate or public profile is published only with a separate guardian consent.
• The guardian can ask for the child profile and course records to be deleted.
• Child course records are kept only while the guardian account keeps the enrollment, then deleted with that account unless a longer legal hold applies.

A learner under 16 does not get a TECHi login. The parent or guardian account owns consent, payment, and messages.

4. What your browser sends automatically

IP address, user-agent (browser and device), referring URL, the pages you visit, and the timestamp. This is standard server-log data. Our servers operate on OVH in Virginia, United States, behind Cloudflare. It is used to operate and secure the site; the retention period can vary by system, incident, and provider.

5. Payment information

Analyst subscriptions, membership, and Learn checkout run through Stripe. Stripe holds the card. We see the confirmation that a charge succeeded, the last four digits, and the subscription or enrollment state (active, cancelled, past-due). We do not use that payment record to build an advertising profile.

Different data, different reason. We don’t pool all of it into a giant marketing graph.

• Account data — to authenticate you, prevent duplicate sign-ups, and let you log back in if you forget your password.
• Newsletter email — to send the messages you asked for. Every send has an unsubscribe link. We do not treat a comment email as permission to market to you.
• Learn and analyst records — to deliver the course or subscription you bought, including progress, certificates, and refunds.
• Activity data (comments, follows, watchlist) — to render your dashboard, send notifications you opted into, and personalise the home feed when you’re logged in.
• Server logs — to diagnose crashes, rate-limit abusive traffic, and meet our security obligations to Cloudflare and our hosting provider, OVH.
• Payment data — to charge subscriptions and pay analysts their share.

Google Analytics 4 measures public pages only after you accept optional analytics in Privacy choices. Before that choice, or if you reject it, the analytics tag stays off. You can withdraw consent through Privacy choices in the footer; this stops measurement and clears the first-party analytics cookies on that browser. We configure Google signals and advertising personalization off; we do not send account identifiers, search queries, private pages, or full referring URLs. Analytics cookies are pseudonymous identifiers, not a guarantee of anonymity.

For details on cookies (including how to turn them off), see our cookies policy.

We don’t sell your data. Full stop. The only third parties that touch your information are vendors we hire to help run the site:

• OVH — hosting. Our servers and our Postgres database run on OVH infrastructure in Virginia, United States. Sees your IP and the pages you request.
• Cloudflare — DNS, CDN, and edge security in front of those servers. Sees your IP and the pages you request.
• Neon — until August 2026 our managed Postgres provider. A frozen copy of the database from before that migration is retained on Neon (US East) as a rollback backup. It is no longer written to.
• Vercel — our previous host. Historical copies remain in Vercel Blob storage as an archive. Live media files are stored and served from our OVH server; the site does not fetch media from that archive.
• Stripe — payment processing. Sees card data we never do.
• Resend / SMTP provider — sends transactional and digest emails. Sees your email address and the messages we send you.
• Google Analytics 4 — readership and performance measurement on public pages, only after you accept optional analytics.

We may disclose data when required by law or a valid legal process.

If you live in the EU, UK, California, or any of the other jurisdictions with modern privacy laws on the books, you have the right to:

• See what we hold — request a copy of your account data via Settings → Export, or by emailing us. We handle verified requests within applicable legal time limits.
• Correct it — most fields are editable from your dashboard directly. For the rest, email us.
• Delete your account — Settings → Delete account. Comments and analyst reports written under your name may remain available where needed to preserve the publication record. We process verified deletion requests subject to applicable law, security safeguards, and any legal hold. Payment records are handled separately under the payment-record retention policy below, subject to applicable privacy rights and legal obligations.
• Object to processing — write to us. We’ll stop unless we have a legitimate operational reason (such as fraud prevention) and we’ll explain that reason if so.

California residents have additional rights under the CCPA — see our CCPA notice for the full list.

• Account data — Kept while the account is active. When you ask to delete an account, we process the request subject to applicable law, security safeguards, and any legal hold. We do not publish a fixed archive or purge timetable for every record type.
• Comments and posts — Published contributions may remain available after an account is closed where needed to preserve the publication record; we remove or anonymise personal account details where applicable.
• Server logs — Diagnostic and security logs are retained only for operational and security purposes. Retention can vary by system, incident, and provider.
• Payment records — Payment records are currently kept indefinitely, with no fixed deletion schedule. This describes current practice and does not limit applicable privacy rights or legal obligations. The IRS does not prescribe one retention period for every record. Card numbers stay at Stripe. IRS recordkeeping guidance.
• Email logs — Delivery providers may retain message and delivery logs under their own terms. TECHi does not publish a fixed deletion period for those records.
• Newsletter addresses — Confirmed subscribers receive newsletters until they unsubscribe. An unsubscribe takes effect immediately for future sends; we retain the subscriber record needed to honor that opt-out. We do not publish a fixed inactivity-deletion period.
• Child course records — Kept only while the guardian account keeps the enrollment, then deleted with that account unless a longer legal hold applies. Payment records that name the guardian follow the payment-record retention policy above.
• Recruitment data — Used for the hiring process and retained only as needed for that process, applicable law, a hiring dispute, or a legal hold. We do not publish a fixed deletion period for every application.
• Anything else — Retained only as long as needed for the purpose described at collection, subject to applicable law and any legal hold. The period can vary by record type.

Public site connections use HTTPS. Passwords are stored as salted one-way hashes using Payload’s PBKDF2-SHA256 password handling, and two-factor backup codes are stored as hashes. Sign-in cookies use HTTP-only, Secure and SameSite controls. Stripe processes card payments; TECHi receives payment references and billing or subscription information, not full card numbers. Internal database transport is separate from public HTTPS; we do not claim that every database connection is TLS-encrypted.

TECHi does not claim SOC 2 certification. We use established hosting, security and payment providers, but a provider’s certification does not certify TECHi or guarantee that a service is risk-free.

A careers application is a separate record from a reader account. The form asks for your name, email, phone, location, LinkedIn URL, portfolio URL, work experience, a cover letter, salary expectation, the date you can start, and work authorization. We use that only to consider you for a role.

Used for the hiring process and retained only as needed for that process, applicable law, a hiring dispute, or a legal hold. We do not publish a fixed deletion period for every application.

• Visitor — Someone reading the public site without an account. A visitor is not a user and cannot enroll in Learn.
• Child learner — A person under 16 named on a Learn enrollment. A child learner does not get a login, a password, or a public profile.
• Registered user — A person who created a TECHi account. The account holder must be at least 16. There is no 13–15 opt-in account.
• Subscriber — A registered user who pays for an analyst subscription or another paid TECHi product. Paying requires the legal capacity to contract, which we treat as 18.
• Guardian — A registered user, at least 16, who owns a child learner’s Learn seat, payment, consent, and messages. The child does not sign in.

A TECHi account requires the holder to be at least 16. We don’t knowingly let a child create one. Learn courses for younger students are taught through a parent or guardian account:

• The TECHi account belongs to a parent or guardian who is at least 16. The child does not get a login.
• The guardian confirms they are the parent or legal guardian and consent to the child taking the course.
• The child is a profile on that account: first name and age band only.
• The guardian chooses whether the child profile, projects, or certificate can be shown publicly.
• Instructors message the guardian account. They do not contact the child directly.
• Live sessions follow the classroom safety rules: no private child contact, no public chat with strangers, and a guardian can sit in.
• The guardian pays. A child cannot check out.
• A certificate or public profile is published only with a separate guardian consent.
• The guardian can ask for the child profile and course records to be deleted.
• Child course records are kept only while the guardian account keeps the enrollment, then deleted with that account unless a longer legal hold applies.

A learner under 16 does not get a TECHi login. The parent or guardian account owns consent, payment, and messages. If a child has created an account anyway, email info@techi.com so we can assess and process the request.

We update this notice when our data practices change. The “Last updated” date at the top of this page identifies the current revision.

For privacy questions, data requests, or anything else covered above, email info@techi.com.

For urgent legal notices: TechAbout LLC, 30 N Gould St Ste R, Sheridan, WY 82801, USA.