About
Trust and security
Macro by Mark handles account credentials, billing details, and saved research. This page explains how account access is protected, where information is stored, and which providers help operate the service.
Last reviewed: 2026-10-30.
On this page
Live stats
Aggregate counts refresh every 6 hours. They show security checks without identifying users. Unavailable fields show a dash.
- Security alerts awaiting review (7d)
- 0
- Reviewed privileged access paths
- 102
Snapshot generated Sun, 15 Nov 2026 22:38:23 GMT.
Account security
You can sign in with a password, Google, or a passkey. Auth.js and Supabase support account sign-in. Supabase access and refresh tokens are encrypted in sign-in cookies that browser scripts cannot read.
- Passkeys (WebAuthn). Sign in with Touch ID, Face ID, Windows Hello, or a compatible security key. Passkeys require your device to verify you and do not need a follow-up authenticator code. Checks for replayed or potentially copied credentials can reject a sign-in.
- Two-factor authentication. Add time-based codes from a standard authenticator app. Enrollment also gives you 10 single-use recovery codes. Keep them somewhere safe; only hashed versions are stored by the service.
- Captcha protection. Password sign-in, registration, and password reset use Cloudflare Turnstile to help prevent automated abuse.
- Sign-in attempt limits. Repeated attempts are limited by both account email and network address. Email addresses are hashed when used to count attempts.
- Breached-password checks. Registration and password changes check Have I Been Pwned for known compromised passwords. The lookup sends only a short prefix of a password hash, not your password or its full hash. An unavailable lookup does not block registration or a password change.
- Session lifetime. Sign-in sessions use a rolling 30-day expiry. Administrative access requires renewed verification after 8 hours, even if the normal session remains valid.
- Step-up verification. Password change, email change, account delete, passkey removal, MFA disablement, and access-token changes require a fresh password, passkey, or authenticator check. This extra verification lasts 10 minutes. Billing management opens through Stripe's hosted portal after normal signed-in authorization.
- Active sessions. You can see active devices in Account > Security and revoke any session, including sign-out-everywhere.
- Sign-in alerts. A sign-in from an unfamiliar, untrusted browser triggers an email notification.
- Extra protection for administrators. Administrative access requires an enrolled authenticator and verification within the last 8 hours.
Network and platform controls
- Browser protections. A Content Security Policy restricts which scripts and other resources the site can load.
- Secure connections. HTTPS protects information in transit. Strict Transport Security tells browsers to keep using HTTPS for the site and its subdomains.
- Abuse prevention. Limits on repeated sign-in attempts and sensitive account changes help protect against automated attacks. Upstash supports these limits, with local backup limits for account-security requests when it is unavailable.
- Account access checks. Saved account data is protected by checks in both the application and database that restrict access to the signed-in owner.
- Privileged access review. Components that need broader database access are listed with a reason. Automated checks flag additions that have not been included in that review.
- Log redaction. Logging safeguards mask email addresses and remove sensitive fields such as passwords, access tokens, and cookies from supported structured logs.
Controls verification
Automated checks run every six hours and cover secure connections, browser protections, cookies, and public-page access. Additional signed-in and release checks are run manually. Below are the last 24 hours of recorded results:
- Security check runs (24h)
- 4
- Pass rate
- 100.0%
- Last run
- Sun, 15 Nov 2026 18:17:38 GMT
Reports are available to institutional reviewers on request. If results are unavailable, this section does not count them as passing checks.
Data minimization and persistence
- Profile fields are optional and post-sign-in. Account creation asks for credentials only. Identifying profile fields (name, city, school, organization, region, professional metadata) are collected after sign-in — in account settings or through skippable prompts — and are saved to your account. Remaining drafts from the retired setup wizard expire after 7 days.
- Phone numbers are not collected at sign-up. You do not need to provide a phone number to create an account.
- Local browser storage. Your browser can store the model scenarios you save, model and simulator sessions, and preferences. It can also still hold dashboard drafts and saved local dashboards, workspace notes, projects, and saved runs created on this device before Macro by Mark stopped offering those features. These records may include information you enter. If your account kept workspace sync from an earlier plan or an access grant, the workspace notes, projects, and saved runs already on this device can also be saved to your account. You can clear device-local records through your browser.
- Analytics require your consent. Vercel Analytics and Speed Insights load only after you allow analytics in the cookie banner. Withdrawing that consent stops these tools from running on the page.
Marco assistant controls
- Plan and usage checks. Marco is part of Plus. Before requesting an answer from a model provider, it checks your plan access and usage limits.
- Answers with sources. Marco answers from Macro by Mark's own material: concept guides, schools of thought, policy and history pages, model pages, simulators, and the page you are reading. It does not report current economic values, release dates, news, or Macro Lab forecast results, which Macro by Mark no longer offers. When an answer needs a source Marco does not have, it is designed to say so.
- Private saved records. Dashboards, watchlists, workspace notes, projects, and saved runs that you saved earlier are read only when you are signed in and ask Marco about them. Account access checks apply. Marco receives compact summaries and limited workspace snippets, not raw dashboard configuration, and it does not create new dashboards or watchlists.
- Preference context. Marco may use the current locale and signed-in profile fields such as timezone, country, experience level, and focus areas to choose reply language, formatting, explanation depth, and examples. It does not receive raw cookie values, analytics history, marketing signals, or private saved records as preferences. Preferences do not establish current economic facts.
- Saved chat history. Marco conversations are saved to your account in Supabase as separate conversations with limits on their number, length, and retention. Free accounts and visitors cannot chat with Marco. You can clear or delete saved conversations from the chat controls.
- Safety boundary. Marco can explain macro conditions and risk channels, but it must not provide personalized buy, sell, hold, trading-signal, or portfolio-allocation advice.
Your data, your access
- Export. Sign in and open . Download your account data as a JSON file, including profile, preferences, dashboards, watchlists, notifications, workspace, sessions, security events, watchlist alert subscriptions, personal access token metadata, security alerts, saved Marco conversations, and billing subscriptions.
- Delete. Account > Security > Delete account. Verify with a password, passkey, or authenticator and confirm by typing DELETE. Deleting your account removes profile, preferences, dashboards, watchlists, notifications, workspace, onboarding draft, sessions, passkeys, personal access tokens, MFA factors, and recovery codes. Billing records have separate retention obligations and are scrubbed on a separate schedule.
- Correct. Account > Settings to edit profile fields. Account > Security to change your password or email.
Subprocessors
The product depends on the following third-party providers. The table lists what each provider does and the information it processes, including records some providers still hold from features that are no longer offered. Material subprocessor changes are emailed to active paid users at least 30 days before they take effect.
| Provider | Purpose | Data |
|---|---|---|
| Supabase | Authentication and primary database | Account identity, profile, preferences, sessions, MFA factors, passkeys, saved account records, classroom and course records, and saved Marco conversations |
| Vercel | Application hosting, serverless runtime, and edge delivery | Request metadata, IP address, user agent, URL, response status, and runtime logs |
| Amazon Web Services (AWS) | Storage of records from earlier Macro Lab runs. Macro Lab is no longer offered and accepts no new runs. | Lab run identifiers and job metadata, user-provided input bundles, execution logs and results, and generated artifacts from earlier Macro Lab runs |
| Upstash Redis | Distributed rate limiting and cache storage when configured | Rate-limit keys, IP-derived buckets, counters, reset timestamps, and public macro cache payloads. Before semantic search and content retrieval were switched off, it also held cached query-derived embedding vectors, each for up to 24 hours where supported. |
Retention map
| Data | Retention |
|---|---|
| Profile and preferences | Until account deletion. Included in account export. |
| Dashboards, watchlists, and workspace records | Until account deletion, which removes them. Removing them one at a time is no longer offered. Included in account export. |
| Saved Marco conversations | Signed-in accounts can save up to 50 conversations, each keeping its latest 40 messages. The default retention is 90 days; clearing or deleting a conversation, or deleting the account, removes it sooner. |
| Classroom sessions and answers | Kept until the instructor's account is deleted, which removes each session with every answer and review in it. A course student's answers are also removed when that student's account is deleted. A session stops taking answers when the instructor ends it or 24 hours after the instructor creates it. Not included in account export. |
| Courses, assignments, and grades | Kept until the instructor's account is deleted. Deleting a student's account removes that student's memberships, submissions, and grades; removing a student from a course keeps their work. Not included in account export. |
| Notifications and alert subscriptions | Until account deletion, unsubscribe, or preference removal. Delivery-provider logs follow the provider retention policy. |
Compliance documentation
Documentation for the following procedures is available on request for vendor reviews and procurement questionnaires:
- Data subject access requests (GDPR Art. 15 / 17 / 20, CCPA).
- Incident response, including severity, responsibilities, and applicable notification deadlines.
- Quarterly privileged access reviews and removal of access when roles change.
- Subprocessor list with data classes and 30-day pre-announce policy.
- Backup and recovery objectives and testing procedures.
For institutional buyer evaluations, see the consolidated .
Reporting and contact
For privacy requests, vulnerability disclosures, or DPA inquiries:
- for security and vulnerability disclosures
- for privacy / GDPR / CCPA requests, DPA, and subprocessor questions
We aim to acknowledge DSAR-style privacy requests within five days and to fulfill them within 30 days where law applies. Vulnerability disclosures are acknowledged within five business days.
See also our and .