Privacy Policy
Effective date: October 20, 2026 Last updated: October 20, 2026
My Actual Me, Inc. ("Actual Me," "we," "us") operates myactual.me. This policy explains what we collect, why, who can see it, and how to remove it.
Questions or requests: support@myactual.me
The short version
Actual Me lets you connect accounts you already use, such as your calendar, code repositories and work tools. It builds an agent called Candor that answers questions about you using only data you connected. Recruiters can also send you evidence requests, which Candor answers from evidence you choose, and you decide what the recruiter sees.
Eight things worth knowing up front:
- You choose every source. Nothing connects unless you connect it.
- Connecting is not sharing. For a recruiter's request, you pick the specific work items Candor may read: repositories, projects, pages, teams or design files. Recruiter requests only ever use your work sources (GitHub, GitLab, Bitbucket, Notion, Jira and Linear, with Figma to be added once available). Your calendar, health, location, financial and other personal sources are never used for a recruiter request.
- You see every answer before a recruiter does, and you release or withhold each one. No one at Actual Me reviews your answers. We look at a specific answer only if you or a recruiter report a problem with it, you ask us for your file, or the law requires it.
- Candor speaks only from evidence you connected. If it has no evidence, it says so.
- Some data can never be shown to anyone but you, regardless of your settings.
- We use no advertising, no analytics, and no tracking.
- You can delete your account. That removes your profile, sources and requests. We keep a limited record of answers you released to a recruiter, and of your authorization for each request, for 5 years, to meet our obligations as a consumer reporting agency (section 7.2).
- Answers you release to a recruiter are a consumer report. You have rights under the federal Fair Credit Reporting Act, including to see your file and to dispute anything inaccurate (section 4.2).
1. Information we collect
1.1 Account information
At signup we collect your email address, and nothing else. During setup we ask for a display name, a handle, and your primary goal. Your browser's timezone is detected automatically. You may add a profile photo, stored with Cloudinary. We use magic-link sign-in (via Resend) and Sign in with Google. Google sign-in gives us your name, email address and profile picture, for authentication only. We never ask for a password.
Recruiter accounts are created by Actual Me. For a recruiter we store their email address and the name of their firm. The firm name is shown to candidates on the requests that recruiter sends.
1.2 Sources you can connect
Each connection is a separate, explicit act. We never request write access to any account.
Connected accounts:
| Source | What we retrieve |
|---|---|
| Google Calendar | Event titles, start and end times, duration, all-day flag, and attendee counts. You may block calendars and filter events by keyword. See section 3. |
| GitHub | For your profile: metadata (such as name, language and stars) of the repositories you select at install time and of your public repositories; your account-wide contribution counts, including a count of private contributions (never their content); and file contents (such as the README and a sample of files) of the repositories you select at install time, which we use to write a short description of each. For a recruiter request: the contents (files, commits, history) of the repositories you select for that request. |
| GitLab | For a recruiter request: the contents (files, commits, history) of the projects you select for that request. |
| Bitbucket | For a recruiter request: the contents (files, commits, history) of the repositories you select for that request, from workspaces you own. |
| Notion | For your profile: workspace activity metadata only (page counts and dates). For a recruiter request: the content and open comments of the pages you select for that request. |
| Jira | For a recruiter request: issues you created, reported, were assigned or commented on in the projects you select, your comments, and issue history. |
| Linear | For a recruiter request: issues you created, were assigned or commented on in the teams you select, your comments, and issue history. |
| Figma (not yet available) | For a recruiter request: the design files you add for that request: their pages, frames, components, text and version history. We don't read comments. |
| Slack | Activity patterns only. No message content. |
| Oura | Sleep, readiness and HRV metrics. |
| Banking | Via Plaid: transaction summaries and spending categories. |
Through the Actual Me phone app:
| Source | What we retrieve |
|---|---|
| Apple Health | With your permission in Apple Health: daily steps, active energy, exercise minutes, resting and average heart rate, heart-rate variability, VO2 max, respiratory rate and body weight, and your sleep stages. |
| Location | Only while the app is open and you have allowed location access: your position and its address (street address, neighborhood, city, state and country). We record it each time you open or sign in to the app, and again when you return to the app if at least 3 hours have passed since the last record. We never collect location in the background. |
Files you upload:
| Source | What we read |
|---|---|
| From an export you download from Instagram and upload to us: likes, posts, saves, follows, and interests. Your DMs, comments, and personal information stay on your device and are never uploaded. | |
| From an export you download from Facebook: posts, reactions, friends, pages, groups, and interests. Your DMs, comments, and personal information stay on your device and are never uploaded. | |
| Documents | Résumés, writing samples, or other files you choose to upload. |
Instagram and Facebook uploads are not yet available to all accounts. They aren't currently offered in the menu, and an upload from an account we have not enabled is refused and nothing is stored.
We are not connected to Meta and never have been. Instagram and Facebook data reaches us only because you exported it yourself and chose to upload it.
Earlier connections. We no longer offer Strava, Spotify, Fitbit or a Gmail connection. Data synced from them earlier is kept until you disconnect the source or delete your account.
Recruiter requests use only GitHub, GitLab, Bitbucket, Notion, Jira and Linear, and Figma once it is available. None of the other sources above is ever used for a recruiter request.
We do not sell your data. We do not use it for advertising. We do not use it to train AI models.
1.3 What we deliberately do not collect
- We never read email message bodies.
- We never read Slack or any other message content.
- We read Notion page content only for pages you select for a recruiter request, and only to answer that request. We never read Notion page content for your profile.
- We do not store email addresses, subject lines or message identifiers from your mailbox.
- We never request write access to any connected account.
1.4 Analytics, tracking, and logs
We use no third-party analytics, product telemetry, error tracking, session recording, or advertising SDK. No Google Analytics, no Segment, no Sentry, no ad network, no data broker.
Our servers keep operational logs, and those logs can contain your email address (when a sign-in link is sent), your account identifier, and the names of sources you connect or request. Logs never contain message content, event titles, or file contents. They exist for debugging and are held by our hosting provider, Render.
2. Who can see what
Public profiles, people search, and questions to Candor about another person's profile are currently turned off. While they are off, no one else can view your profile or ask Candor about you through them. Sections 2.1 and 2.2 describe how they work when they are on. If we turn them back on, we'll tell you first (section 12).
The boundaries below are enforced in code by filtering data before it reaches the agent — not by instructing the agent to be discreet.
2.1 Visible to any signed-in visitor
GitHub activity and repository descriptions, Calendar patterns, Slack activity patterns, and documents you have explicitly marked public.
2.2 Visible to people you approve (your Circle)
Everything above, plus health and location signals where you have connected them. You are shown exactly what Circle membership grants before you grant it, and you can revoke it at any time.
2.3 Visible only to you — permanently
Gmail metadata can never be shown to any other person, in any audience, under any setting. There is no toggle that changes this. Your mailbox is correspondence with people who never agreed to anything.
Your Notion activity data and your banking data are also owner-only. (Notion evidence you choose for a recruiter request is different: the recruiter sees short excerpts from it in any answer you release, as described in section 2.5.)
2.4 Uploaded documents
Private by default. A document becomes visible to others only if you explicitly mark it public. A résumé you publish for a recruiter is public; a performance review you upload for your own use is not.
2.5 Recruiters
A recruiter sees only the answers you release, each with short evidence excerpts and links. If you withhold answers, the recruiter sees how many were withheld, never their content. If you decline a request, the recruiter sees that it went unanswered.
If Actual Me withdraws an answer after finding it inaccurate or unverifiable, the recruiter sees "Finding withdrawn by Actual Me." in its place. That is never counted as something you withheld.
Recruiters must certify, for each request, that it is for employment purposes and that they will follow the Fair Credit Reporting Act.
3. Google user data
3.1 Limited Use disclosure
Actual Me's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
3.2 What we access and why
Google Calendar is the only Google data source currently available. Gmail metadata is described here because the capability is built, but it is not yet offered — it requires an additional Google security review we have not completed. No Actual Me user can connect Gmail today.
| Scope | Permits | Why we request it |
|---|---|---|
email, profile, openid |
Your name, email address, profile picture | Sign-in only |
calendar.readonly |
Read your calendars and events | Time-allocation patterns — how you actually spend working time |
gmail.metadata |
Read message metadata only — no bodies, no search | Response-time and sending-rhythm patterns |
These are requested at different moments. Signing in requests identity only. Google Calendar and Google Gmail are separate connections, each requested at the moment you connect that source and never at sign-in. They are independent: connecting one never grants access to the other.
3.3 Specifically regarding Gmail
As stated in section 3.2, Gmail is not yet offered and no Actual Me user can connect it today. This section describes the capability as built, for when it becomes available.
The gmail.metadata scope does not permit reading message content and does not permit search. We request message timestamps, thread identifiers, and one header (In-Reply-To).
We do not retain per-message records. Individual message identifiers and timestamps exist only in memory during analysis and are discarded when it completes. What we store is statistics: total messages sent, average per day, busiest day of week, top sending hours as percentages, percentage sent outside business hours, a consistency score, and average and median reply times.
These are facts about you, not about the people who write to you.
Gmail-derived data is never shown to any other person on the platform.
3.4 Revoking Google access
Google Calendar and Google Gmail are separate connections, and each can be disconnected from inside Actual Me. Disconnecting one is handled like any other source — see section 7.1.
Signing in with Google grants identity only. Sign-in does not connect either data source, and it does not restore one you have disconnected.
To revoke our access at Google itself, use myaccount.google.com/connections. That takes effect immediately. Deleting your Actual Me account (section 7.2) also attempts to revoke it; if that fails, we tell you, and you can revoke it at the link above.
4. How we use your data
We use your data to compute patterns about you; to let Candor answer questions from you or from people you have authorized; and to answer recruiter evidence requests, as described in sections 4.1 and 4.2. We do not use your data for advertising, sell or rent it, or use it to train any AI model.
4.1 Recruiter evidence requests
When a recruiter sends you an evidence request, here is what happens:
- You choose the evidence. You select the specific repositories, projects, pages, teams or design files Candor may use, and you may limit each one to particular questions. Before you continue, you confirm that you are authorized to share what you select. Do not select confidential, proprietary or employer-restricted material you are not permitted to disclose. We do not verify ownership or employer permission. We rely on your confirmation.
- Candor investigates only that evidence, only to answer that request's questions. Content from your selections is sent to our AI provider (section 5) for this purpose.
- Temporary copies are deleted. For Notion and Figma, the full content of your selections is held only while Candor investigates. It is deleted as soon as the investigation finishes. We keep only the answers, short evidence excerpts and links.
- You review every answer and decide, answer by answer, what to release.
- The recruiter sees only what you release (section 2.5).
Information about other people. Your evidence may mention other people, such as co-authors, commenters or editors. We may process that information only temporarily while Candor investigates. Before anything is saved, names and handles of other people that the source identifies to us are replaced with "another contributor." A name that appears only as ordinary text, for example a name typed inside a document, commit message or comment, may not be detected. Review each answer for other people's names before you release it, and withhold any answer that contains one.
Atlassian (Jira). If you connect Jira, we store your Atlassian account ID, and we report it to Atlassian periodically, as Atlassian requires of apps that store personal data, so that Atlassian can tell us if your account is closed or changed. When Atlassian reports an account closed, we delete the data tied to it, except the records described in section 7.2 that we keep for 5 years.
4.2 Consumer reports and your rights under the FCRA
When you release answers to a recruiter, Actual Me acts as a consumer reporting agency and the released answers are a consumer report under the federal Fair Credit Reporting Act (FCRA). Before a request goes ahead, you receive a disclosure and give your written authorization.
Your rights include:
- Your file. You can ask for everything we hold about you for recruiter requests, the sources used, and who received your answers in the past two years. It's free, after we verify your identity. We aim to respond within 15 days.
- Disputes. If you think an answer is inaccurate or incomplete, tell us. We investigate within 30 days, reviewing the stored record. If we find it's inaccurate, or we can't verify it, we withdraw it and tell you and any recruiter who received it.
- Adverse action. Before a recruiter or employer acts against you because of an answer, they must give you a copy of the report and the Summary of Your Rights. If they then act against you, they must tell you, give you our contact details, and tell you how to get your file and dispute it.
A full Summary of Your Rights Under the Fair Credit Reporting Act is at myactual.me/legal/fcra-summary-of-rights.pdf.
How Candor works (the AI notice). Answers are produced by automated analysis of the work evidence you select. They describe what that evidence shows about specific experience, not personal traits. Our standard: missing evidence is never treated as missing ability, and no answer may claim more than its evidence supports.
Contact for file requests and disputes: support@myactual.me, or My Actual Me, Inc., 980 N Michigan Ave, Ste 1090, Chicago, IL 60611.
5. AI processing and our AI provider
Candor is built on models from Anthropic. Anthropic's commercial terms state that API inputs and outputs are not used to train their models. Anthropic's published commercial retention policy deletes API inputs and outputs within 30 days.
What we send to Anthropic depends on the feature:
- Profile and insights: we send computed summaries, such as statistics about your calendar and activity, not your raw data, with three exceptions:
- GitHub: to write a short description of each repository, we send its README, a sample of its files and its file list;
- Documents you upload: we send the document's contents, to produce the summary we store in its place;
- Questions about your code: when Candor answers a question from you, or from someone you have authorized, it may read files from your repositories.
- Recruiter evidence requests: we send the content of the evidence you selected, such as code, page text and issue text, to the extent Candor reads it to answer that request's questions.
5.1 Sources we will not send to any AI model
Some platforms prohibit their data being used with AI models. We honor those terms by excluding those sources from AI processing entirely — even for your own private use.
- Oura — its API agreement prohibits providing Oura data as input to any AI model
- Spotify — its developer policy prohibits ingesting Spotify content into an AI model
- Strava — its API policy prohibits use of Strava data in any AI application
We still display this data to you. Candor cannot see it, and will tell you so rather than pretend otherwise.
5.2 Human access to your data
No one at Actual Me reads your recruiter-request answers or evidence as a matter of routine. Staff access a specific answer and its stored record only to:
- handle a dispute you raise;
- handle a problem a recruiter reports;
- fulfil your request for your file;
- comply with law.
Every data route derives identity from your authenticated session. There is no administrative interface and no support impersonation, and no route lets one account read another account's data beyond what that account has chosen to share (section 2).
Separately: we operate the database, and our engineers can access it directly for debugging, maintenance, and incident response. This is true of essentially every online service, and we would rather state it than imply otherwise. Access is limited to personnel who need it, and our internal practice is to work from counts and structure rather than reading individual records.
6. Data sharing
We share your data with:
- People you authorize, in the scope described in section 2;
- Recruiters: only the answers you release to them (section 2.5);
- Anthropic: AI processing (section 5);
- Atlassian: your Atlassian account ID, if you connect Jira (section 4.1);
- Render (hosting and database, United States), Netlify (web hosting), Cloudinary (profile photos), Resend (email delivery) and Plaid (if you connect a bank account);
- Legal authorities, where required by law.
These are the only third parties that receive your data. When you connect a source, we communicate with that provider (Google, GitHub, GitLab, Bitbucket, Notion, Atlassian, Linear, Figma, Slack or Oura) to retrieve the data you authorized. We do not sell your personal information.
7. Retention and deletion
7.1 Disconnecting a source
Disconnecting a source deletes the data we synced from it, deletes our stored access tokens, removes the facts that source contributed to your profile, and attempts to revoke our access with the provider. Where a provider offers no revocation endpoint (for example Bitbucket, Jira and Figma), we tell you so and direct you to revoke it in that service's own settings.
Three things to know:
- Your weekly insight history is deleted entirely — not only the parts from that source. Insights blend several sources into prose that cannot be separated afterward, so we delete rather than leave behind something we cannot honestly attribute. This is not restored.
- Your conversations with Candor are not deleted, nor are documents you uploaded. Those are separate, and you can clear or delete them separately.
- Google Calendar and Google Gmail are disconnected separately — each is its own connection, and each can be disconnected here. See section 3.4.
Disconnecting a source does not delete answers from evidence requests you have already completed. To remove those, delete your account (section 7.2).
Disconnecting GitHub does not delete the short descriptions we wrote of your repositories. They stay on your profile until you delete your account.
7.2 Deleting your account
When you delete your account we delete:
- your profile and connected-source data, and uploads;
- chat history and insights;
- access tokens (we attempt to revoke every provider token, and tell you which we couldn't);
- your evidence requests, with their answers, excerpts and records.
After deletion, a recruiter can no longer see answers you released.
What we keep, and why:
- A 5-year record of answers you released to a recruiter. It holds the answer as the recruiter received it, the question and the request's role, the evidence references (links and identifiers, not the evidence itself), the AI model version used, your email address, the recruiter and firm who received it, and the dates. We keep it to meet our obligations as a consumer reporting agency: answering disputes and disclosing who received your report. It's deleted 5 years after release.
- A 5-year record of your authorization for each request. It holds your email address, the name you typed, the versions of the disclosure and authorization you agreed to, when you agreed, and the recruiter's certification, email address and firm. We keep it to meet our obligations as a consumer reporting agency. It's deleted 5 years after you gave it.
- Requests sent to your email address that you never accepted. These hold your email address and the recruiter's request, with no answers. They expire after 14 days, and they aren't removed automatically when you delete your account. Ask us at support@myactual.me and we'll delete them.
- Operational logs keyed to requests. These hold counts, timings and costs, with no answer content.
- Questions you asked Candor on other people's profiles, and Candor's answers. These belong to the profile you visited; we remove your account from them, but the questions and answers stay.
- Invitations other people sent to your email address. These hold your email address. They expire after 7 days, and we'll delete them if you ask us at support@myactual.me.
If a recruiter deletes their account, requests they sent remain visible to you, and released answers remain visible to their firm.
Account deletion cannot be undone. You can delete your account from the Account tab in your dashboard.
7.3 How long we keep data
We keep your data until you delete it. There is no automatic expiry. The exceptions are:
- sign-in links expire after 60 minutes, and invitations after 7 days;
- evidence requests you have not completed expire after 14 days, but an expired request is not deleted;
- temporary full-content copies of Notion and Figma evidence are deleted when Candor's investigation finishes;
- the record of released answers and the record of your authorization for each request (section 7.2) are kept for 5 years, then deleted.
8. Your rights and controls
Within Actual Me you can: see every connected source and when it last synced; disconnect any source (see section 7.1); see and revoke every person you have granted access to; mark uploaded documents public or private; delete uploaded documents; clear your Candor conversation history; block calendars or filter events by keyword; (when public profiles are available) control whether your profile is discoverable; withhold or release each evidence-request answer, decline a request, and withdraw from a request before it completes; and delete your account.
Depending on where you live, you may also have rights to access, correct, delete, or export your data. To exercise these, contact support@myactual.me. For your rights under the Fair Credit Reporting Act, see section 4.2.
9. Security
Data is encrypted in transit. Sessions are signed tokens that can be invalidated centrally. Access tokens for your connected accounts are encrypted in our database at the application level (AES-256-GCM), in addition to storage-layer encryption at rest. No system is perfectly secure, and we do not claim otherwise.
10. Children
Actual Me is intended for adults and we do not knowingly collect data from anyone under 18. If you believe a child has provided us data, contact support@myactual.me and we will delete it.
11. Where Actual Me is offered
Actual Me is intended for users in the United States. Our servers are located in the United States, and if you use the service from elsewhere your data is processed here.
12. Changes to this policy
We will post changes here and update the date above. For material changes — particularly any change to what we collect or who can see it — we will notify you directly and, where required, ask for your consent again.
13. Contact
My Actual Me, Inc. 980 N Michigan Ave, Ste 1090 Chicago, IL 60611 United States