Operator and scope
Who this policy covers
Macro by Mark is operated by Mark Jayson Nation LLC, a Nevada limited liability company based in Las Vegas, Nevada, United States. This policy explains how the website, account system, model pages, classroom sessions and courses, Marco assistant, billing flows, support channels, and related operational systems handle information, including records you saved earlier in dashboards, watchlists, and other features Macro by Mark no longer offers.
References to "Macro by Mark," "the site," "we," or "us" mean Mark Jayson Nation LLC as the operator of Macro by Mark. Third-party data providers, payment processors, identity providers, and infrastructure platforms also apply their own privacy terms to their systems.
Data categories
Information handled by the product
The product may process the following categories of information when you use relevant features:
This section also serves as the current notice at collection for first-party platform data.
- Account identifiers such as name, email address, user id, sign-in provider, and profile state.
- Sign-in and security information, including session details and Supabase access and refresh tokens encrypted in sign-in cookies that browser scripts cannot read.
- Saved product records such as dashboards, widgets, watchlists, watchlist alert settings, notifications, workspace preferences, and account profile choices.
- Billing and plan details needed to connect a signed-in account to Stripe Checkout, Stripe Portal, subscription status, plan access, invoices, and administrative grants.
- Optional saved homework progress: only after you enable it, model and exercise identifiers, whether a server-checked answer was correct, recorded assistance and the attempt time. This progress record does not store homework text, transcriptions or raw answers. A separate control lets Marco use this progress for personalization. The control for sharing limited progress with an AI assistant connected through model tools has no effect while those connections are not available: no progress is shared with an assistant. You can disable these choices, export evidence or clear saved homework progress in account settings. Summaries shared with an assistant before connections closed cannot be recalled from that assistant.
- Classroom and course information from instructors and from students who join a classroom session or course, described in the section on classroom sessions and courses below.
- Marco assistant input, such as messages you send, saved signed-in conversation history, the current page path, request-level source cards, source availability notes, and limited profile context such as a sanitized first name when available.
- When you explicitly ask Marco about your own dashboards, watchlist, or workspace objects, scoped summaries of those saved records, such as title, indicator names, widget count, project status, saved-run metadata, capped workspace snippets, and updated date. Raw dashboard configuration is not intentionally sent in the request context.
- Text you type into profile entity search, such as an employer or organization name, which is sent to Google Places to return matching suggestions. School and city suggestions are available only when those features are enabled.
- Support, feedback, academic-access, or administrative messages you send directly to the operator.
- Operational telemetry such as route, event, device/browser, performance, error, abuse-prevention, and rate-limit signals.
Device storage
Local browser storage
Macro by Mark uses browser storage for local interface state and drafts. Examples include dashboard drafts, saved local dashboards, watchlist preferences, account workspace settings, simulator sessions, chart or model preferences, dismissed notices, and other device-local product state. Dashboard drafts, saved local dashboards, and watchlist preferences in your browser were created before Macro by Mark stopped offering dashboards and watchlists.
Local browser storage normally remains on your device. It syncs to account-backed services only when the product feature is built to do that, such as saved Marco conversation history, account preferences, or notifications. If your account kept workspace sync from an earlier plan or an access grant, the workspace notes, projects, and saved runs on this device can also be saved to your account.
Account security
Sign-in and saved account data
Auth.js manages sign-in sessions, and Supabase stores account data. Supabase access and refresh tokens are encrypted in sign-in cookies that browser scripts cannot read. Account access checks protect your profile, dashboards, watchlists, Marco conversations, notifications, and workspace records. Plan access and changes to passwords and other account details are also checked against the signed-in account.
These controls help protect your sign-in and saved information. Users should protect their email account, avoid shared-device sessions, and report suspicious account activity.
Service providers
Third-party processors and infrastructure
Macro by Mark relies on service providers to operate the product. Depending on the feature, those providers may include hosting and deployment platforms, Supabase, Auth.js-compatible identity providers, Google sign-in, Stripe, Resend, Upstash Redis, Trigger.dev, analytics and performance tools, Anthropic for Marco assistant responses, OpenAI for semantic search and content-retrieval embeddings (both switched off, so nothing is sent to OpenAI), and official or commercial economic data providers.
Stripe handles payment card collection and card processing. Macro by Mark receives billing and subscription metadata from Stripe, but does not store full card numbers. Public economic data providers remain responsible for their own systems and terms.
Google appears in two separate roles. One is sign-in. The other is profile entity search: when you type an employer or organization into a profile field, that text is sent to Google Places through an authenticated server-side proxy, which does not log, persist, or cache the query. The Subprocessors page lists every provider with its data classes and regions.
GDPR-style requests
Lawful bases and international transfers
Where GDPR, UK GDPR, or similar law applies, Macro by Mark evaluates processing under the lawful basis that fits the specific activity: contract performance for account, subscription, and requested product features; legitimate interests for security, abuse prevention, reliability, and basic product operations; consent for optional analytics and for advertising measurement with the Meta Pixel; and legal obligation for tax, accounting, valid legal requests, and required notices.
Macro by Mark is operated from the United States and uses providers with U.S. or global processing paths. For EEA, UK, or Swiss institutional reviews, transfer terms, DPAs, and Standard Contractual Clauses are reviewed through the vendor and buyer contract path rather than implied by this public page.
Assistant data
AI training and model-provider handling
Macro by Mark does not intentionally use Marco messages, saved dashboards, watchlists, or workspace records to train a Macro by Mark foundation model. Marco requests may be sent to the configured model provider when an answer needs AI generation.
Provider handling follows the provider terms and data-processing terms in force for the relevant account. Do not enter regulated, confidential, or highly sensitive information into Marco unless the applicable provider and contract terms have been reviewed for that use.
Semantic search and content retrieval are switched off, so they send nothing to OpenAI and no new query-derived embedding vectors are created or cached. Earlier requests sent normalized user search or assistant query text, together with public indicator metadata or public content chunk text, to OpenAI to generate embeddings. Query-derived embedding vectors were cached in Upstash Redis for up to 24 hours where supported; the normalized query text was hashed for the cache key rather than stored as the key itself.
Teaching tools
Classroom sessions and courses
Instructors can host live classroom sessions, run courses with assignments, and share practice links. Students join a session with a six-digit PIN, as a guest or with an account, and join a course through an invitation link or, where a campus has connected its LMS, through the LMS. What Macro by Mark handles depends on how a person takes part:
- Instructors: the lessons and questions they write, and each saved version of a lesson; the title, questions, and PIN of each session they create; the practice links they share; course titles, assignments, and due dates; the marks, points, and comments they give when they review answers, and when they publish grades; named groups and the students placed in each; and, for faculty collections, departments, and partner articles, their titles, the label and role given to each invited colleague, institution and department names, the email addresses of department staff and of colleagues invited to a department, and the publisher, title, summary, link, and credits of each partner article. A colleague invited to a collection is identified by a keyed hash of their email address, not the address itself.
- Students who join a session as guests: no name, email address, or account. The browser keeps a random code in cookies for up to 24 hours, and Macro by Mark stores only a one-way hash of that code, with a seat number in the session. For each answer, Macro by Mark stores the answer itself (a choice, a written answer of up to 500 characters, a number and its unit, or a graph answer, with written reasoning of up to 1,000 characters where the question asks for it), when it was submitted, the automatic mark or points, any review and comment from the instructor, and whether the student allowed the instructor to show a written or graph answer to the class. An exit ticket that an instructor shares after class works the same way, with its own cookie that lasts until the ticket closes.
- Students who answer a practice link that an instructor shares: no name, email address, or account. Macro by Mark checks each answer and sends the result back, but does not store the answers. The link works until the instructor takes it offline.
- Students who take part through a course: their account ID and the verified email address on their account, recorded when they join or ask to join; whether the instructor has approved or removed them; the answers they submit to assignments, with the automatic mark or points and any review and comment from the instructor; their seat and group in course sessions, with any time during a session when they could not vote because their enrollment changed; and the points they earned in a course session once the instructor publishes grades.
- Where a campus has connected its LMS: the LMS sends a signed launch. From it, Macro by Mark reads only the person's LMS user ID, whether they are an instructor or a learner, the course, the assignment, and the technical details it needs to check the launch and to exchange rosters, grades, and assignment links with the LMS; it does not keep any name or email address the launch carries. Macro by Mark links that LMS user ID to the Macro by Mark account that opened the launch, never matching accounts by email address, and keeps the assignment link, the LMS grade column, and a record of each grade it sends. A launch record holds what Macro by Mark read from the launch and the account that opened it. It can be used for 20 minutes, and an expired launch record is deleted when a later LMS launch starts; the launch cookies last 20 minutes at most. A student whom the LMS roster lists as an active learner is added to the course when they connect from the LMS. Syncing the roster reads the LMS user IDs, roles, and enrollment status of the course's members and removes students that the LMS connection added and the LMS no longer lists; Macro by Mark does not store names or email addresses from the LMS. Sending grades gives the LMS each released assignment total as a percentage, with the student's LMS user ID.
Classroom records
Who sees classroom records and how long they are kept
Macro by Mark uses classroom information to run sessions and courses: to let students join, record and mark answers, show results, let instructors review work and publish grades, keep groups and course rosters current, and, where a campus has connected its LMS, sync the roster and send released grades. It is not used for advertising, Macro by Mark does not use it to train AI models, and classroom answers are not sent to Marco or to any AI model provider. Classroom pages do not load Vercel Analytics, Speed Insights, or the Meta Pixel, whatever the cookie choice. If you allowed analytics or marketing cookies and reached a classroom page from another page of the site, the tools that page loaded stay in the browser tab until the page is reloaded or closed; Vercel Analytics and Speed Insights then discard anything that carries a classroom page's address.
Who can see it:
- The instructor who hosts a session sees every answer and its mark. Answers in a session that is not part of a course carry no name.
- The class display shows how many students have answered; the results, once the instructor reveals them; in challenge mode, a leaderboard of seat numbers or team standings; and a single written or graph answer only if its author allowed it and the instructor chose it, shown without a name.
- A student sees their own answers. They see their own marks and comments only on questions the instructor set to show whether an answer is correct: in a live session once the instructor reveals the results, on an exit ticket once they submit it, and on an assignment once its due date passes. In a course, a student sees the points they earned in a course session once the instructor publishes grades. Apart from what the class display shows, students do not see other students' answers, marks, or email addresses.
- In a course, the instructor sees each student's verified email address, enrollment status, submissions, marks, and grades.
- Colleagues in a faculty collection see the lessons published to it and their credits. Department owners and managers see staff email addresses and roles, pending invitations, and the titles and enrollment counts of linked courses, not students' identities or work.
- Macro by Mark's classroom support page shows a session's title, status, times, and seat count, not its answers or who gave them. Browsers cannot read classroom records directly; the server checks every request against the instructor's or student's account, a guest's code, an LMS launch, or a display or share link the instructor created before it responds.
- Grades sent to a campus LMS are then handled by that institution under its own terms.
Classroom records are stored with Supabase and served through Vercel, which the Subprocessors list already names. No other service provider receives classroom records.
Macro by Mark has no automatic deletion schedule for classroom records. A session stops accepting new students and answers when the instructor ends it or 24 hours after the instructor creates it, but the session, its answers, and the instructor's reviews stay in the instructor's session history and reports. An exit ticket accepts answers until the deadline the instructor sets, from 1 to 14 days, and its answers are kept. Course and department invitations stop working after 7 days, faculty collection invitations after 48 hours, and LMS launch records after 20 minutes.
Deleting an instructor's account deletes their lessons; their sessions, with every answer and review in them; their courses, with the assignments, submissions, and grades in them; the collections and departments they own; and their LMS links. Deleting a student's account deletes their course memberships, submissions, grades, group placements, answers in course sessions, and LMS links. When an instructor removes a student from a course, the student loses access, but their submitted work and grades stay in the course records. There is no way to delete a single session, answer, or course from the site, and account export does not include classroom records. To ask for a copy of classroom records or for their deletion, use our contact form. Guest answers are stored without a name, email address, or account, so Macro by Mark generally cannot identify the answers of a particular guest.
Classroom features do not ask a student's age or date of birth. Like the rest of Macro by Mark, they are not directed to children under 13, as the section on children below explains.
Model tools
Connecting Macro by Mark to an AI assistant
Connections between Macro by Mark's model tools and AI assistants, such as ChatGPT or Claude, are not available, and no plan includes them. No new connection can be approved, and a connection approved earlier cannot run the model tools. While connections are not available, the model tools do not count requests or write entries to their request log.
From the Model tools page in your account, you can still revoke a model access token or disconnect an assistant you connected earlier. Disconnecting does not delete conversation history that an assistant keeps on its side; what an assistant does with earlier answers is covered by that assistant's own privacy policy and terms.
While connections were available, approving one let Supabase, our sign-in provider, share your account ID and the email address on the account with the assistant so it knew which account it was using. The tools received the question and model settings the assistant sent, such as which model and which shock to work through, and computed answers from Macro by Mark's published model content. If you had turned on progress sharing, they could also read and add to your saved homework progress. They did not read or change your dashboards, workspace records, Marco conversations, or billing details. Each request counted against a rolling 30-day allowance, and our request log recorded the tool name, the outcome, how long the request took, and the identifiers of the connection, not your question text or the tool arguments.
If Macro by Mark offers these connections again, this section will be updated to describe them before a new connection can be approved.
Purpose limitation
How information is used and shared
Information is used to:
- Operate the website, account system, billing, and support workflows.
- Maintain saved records, including dashboards and watchlists you saved earlier, as well as preferences, plan access, notifications, and security controls.
- Run Marco, including source-backed answer context, rate limiting, abuse prevention, and safety checks.
- Run classroom sessions and courses, including results, reviews, grades, and, where a campus has connected its LMS, roster and grade transfers.
- Debug errors, improve reliability, measure feature quality, and protect the service.
- Comply with law, enforce terms, investigate misuse, and respond to valid legal or platform requests.
Information may be shared with service providers acting on behalf of Macro by Mark, at a user's direction, during a business transfer, to comply with law, or to protect rights, safety, security, or service integrity. Macro by Mark does not sell personal information for monetary consideration.
Signed-in Marco conversation history is saved as capped account-backed threads so it can follow the user across browser sessions. Marco is part of Plus, so Free accounts and visitors cannot chat with it. Server logs for Marco are designed to record operational fields such as tier, route mode, source availability, model, latency bucket, tool status, and error class, rather than raw private message text or raw saved-object contents.
Retention and rights
Retention, deletion, and privacy rights
Account-backed records are retained while needed to provide the product, maintain security, resolve billing or support issues, comply with law, or preserve legitimate operational records. Classroom records are kept and deleted as the classroom section above describes. Users can delete device-local browser storage through their browser. Account deletion or data requests can be sent to our contact form.
Depending on location and legal thresholds, users may have rights to access, delete, correct, opt out of certain sales or sharing, limit sensitive personal information use, object to or restrict certain processing, portability, and non-discrimination for exercising privacy rights. Macro by Mark will evaluate requests under applicable law, including Nevada privacy law, the CCPA/CPRA where applicable, and GDPR/UK GDPR-style requests where applicable.
The Privacy Choices page lists current self-service export, correction, deletion, cookie, and manual request paths.
Nevada residents may submit a verified request not to sell covered information. Macro by Mark does not sell covered information, but the same privacy contact is the designated request path for Nevada privacy questions.
When a browser exposes a Global Privacy Control signal, the site treats it as an opt-out from non-essential analytics and marketing categories in the local consent store.
Age and updates
Children, changes, and contact
Macro by Mark is not directed to children under 13 and does not knowingly collect personal information from children under 13. If you believe a child under 13 provided information through the site, contact the operator so it can be reviewed and deleted where appropriate.
This policy may be updated as the product, providers, or legal requirements change. The effective date will be updated when material changes are made. Privacy, browser storage, account sync, analytics, and data-request questions can be sent to our contact form.
If a security incident creates a legally required personal-data notice, Macro by Mark follows the incident-response runbook and applicable notification windows.
Referencias principales
Fuentes utilizadas para preparar esta página. No la convierten en asesoramiento legal.
- Nevada Revised Statutes Chapter 603A
Nevada's internet privacy notice and verified opt-out request framework.
- California DOJ CCPA Overview
California consumer privacy rights, including access, deletion, correction, opt-out, and non-discrimination.
- CPPA CCPA Monetary Threshold Update
Current CPI-adjusted CCPA business and enforcement thresholds effective January 1, 2025.
- European Commission GDPR Overview
EU privacy principles and individual data protection rights used as a request-handling benchmark.
- European Commission DSR Handling
Reference for responding to individual privacy-rights requests in a timely, documented way.
- FTC COPPA Rule
Federal children's privacy rule used for the under-13 handling posture.
Páginas relacionadas
Más información sobre las políticas y el servicio de Macro by Mark.
Política de cookies
Cookies necesarias, analítica opcional, renovación del consentimiento y tratamiento de Global Privacy Control.
Opciones de privacidad
Exportación, corrección, eliminación, controles de cookies, GPC y vías de solicitud manual.
Subencargados
Proveedores actuales, clases de datos, notas regionales y ruta de revisión institucional.
Términos de uso
Reglas de uso, límites de asesoramiento, propiedad intelectual y protecciones del servicio.
Uso aceptable
Límites de seguridad, automatización, sanciones, uso de fuentes y medidas de aplicación.
Política de reembolsos
Cancelación de suscripciones, regla general de no reembolso, revisión de conversiones de prueba y ruta de soporte.
Contratos
DPA, MSA, formularios de pedido, revisión de seguridad, seguros y solicitudes de compradores institucionales.
Derechos de autor
Copyright, atribución, crédito de fuentes, retirada de contenido, derechos de proveedores y estado del agente DMCA.
Ruta SOC 2
Estado actual sin atestación, runbooks mapeados, brechas de evidencia y ruta de revisión para compradores.
Estado público
Postura manual de comunicación de incidentes, áreas de servicio monitoreadas y canales de soporte y seguridad.
Registro legal
Índice público actual de cambios legales, de privacidad, seguridad y políticas de confianza.
Ética y cumplimiento
Transparencia de fuentes, postura de no aval, contención del modelo y reglas de integridad investigadora.
Declaración de accesibilidad
Postura de accesibilidad, limitaciones actuales y cómo reportar una barrera o pedir una adaptación.