Tell us what we got wrong.
There is one inbox rather than a set of departments, because this is a small independent site and not a company with a support desk. The most valuable thing you can send is a correction — specifications, prices and availability move faster than any guide tracks, and a page nobody flags stays wrong indefinitely.
We read everything and cannot reply to everything. A correction is more likely to change a page than to produce a message back — which is usually the outcome that matters more.
Same address, useful subject line
These links open your mail app with the subject already set. It is a small thing that makes a real difference to how quickly a message gets dealt with.
Something here is wrong
A price that has changed, a figure that no longer matches Meta’s documentation, a claim that was never right. The most useful message we get.
SubjectCorrection: [page URL] Send a correctionSomething is missing
You came looking for an answer and did not find it. Tell us the question you had rather than the page title you expected — the question is what a page gets built around.
SubjectMissing: [the question you had] Suggest a pageEverything else
Questions about the site, permission to quote something, or telling us a page helped. All of it lands in the same place and all of it gets read.
SubjectHello from metaaimac.com Just say helloIf the mail links do not work on your machine, the address is hello@metaaimac.com and any subject line is fine.
Four lines make a correction easy to act on
Not a form to fill in — just the four things that turn a message into a change on the site rather than a task waiting for research.
The reason this matters is unglamorous. A correction that names the page, quotes the sentence and points at the source can be checked and fixed in the time it takes to read it. A correction that says a page is out of date starts with working out which page, which claim, and against what — which is a research task, and research tasks wait.
You do not need to be polite, detailed or certain. You need to be specific. A blunt four-line message beats a friendly paragraph every time.
Screenshots help when something looks wrong rather than reads wrong, and a link beats a description of a link. If you are not sure whether something is an error or a disagreement, send it anyway — we would rather check ten things that turn out to be fine than leave one wrong figure standing because nobody wanted to bother us.
Which page
The URL, or the page title if that is easier. Several pages here cover similar ground, so naming the product is not usually enough on its own.
What it currently says
Quote the sentence or the figure. This also guards against the page having already been fixed since you read it.
What it should say
The correct version, as best you know it. “This is wrong but I am not sure what is right” is still worth sending — say so and we will check.
Where you saw the correct version
A link to Meta’s documentation, a screenshot of the app, or the date you checked. This is the line that turns a disagreement into a fix.
Four things we genuinely cannot do
Saying so plainly is faster than a polite reply three days later. If your problem is on this list, Meta’s own channels are the only route that leads anywhere.
Anything involving your Meta account
Sign-in loops, locked accounts, verification, connected apps. We have no access to any account and no ability to look anything up. Our login problems page covers the fixes that are in your own hands; past those, it is Meta’s support.
Billing, refunds and subscriptions
We can explain what the tiers are and what they cost. We cannot see your subscription, change it, cancel it or refund it, and no message here reaches anyone who can.
Bugs, data requests and privacy complaints
A bug report sent here goes nowhere useful; it needs to reach Meta to be fixed. The same is true of anything concerning your data — our permissions and privacy page explains what the app asks for, but the data itself is Meta’s to hold and yours to request from them.
Telling you when something will arrive
We track what has been announced, not what is planned. Nobody outside Meta knows the rollout schedule, so our availability pages record the published position and stop there. If a date matters to you, it has to come from Meta.
One thing worth repeating
We never ask for account details, passwords, payment information or access to anything. Nobody from this site will ever contact you first asking for any of that, and any message claiming to is not from us.
We also do not host the app. If you are looking for the installer, it comes from Meta’s own site and nowhere else — our download guide explains why that matters.
Before you write
How do I contact MetaAIMac.com?
By email, at hello@metaaimac.com. There is one address rather than a set of departments, because this is a small independent site rather than a company with a support desk.
Will I get a reply?
Everything gets read. Not everything gets a reply, and corrections are more likely to produce a change on the site than an answer in your inbox — which is usually the outcome that matters more anyway.
What makes a correction easy to act on?
The page it concerns, the sentence that is wrong, what it should say instead, and where you saw the correct version. With those four things a fix takes minutes; without them it takes an investigation.
Can you help with my Meta account or billing?
No. We have no access to Meta accounts, subscriptions, payments or data, and no ability to escalate anything to Meta. Those belong to Meta’s own support channels.
Can you tell me when a feature will reach my country?
No. We track what has been announced, not what is planned, and nobody outside Meta knows the rollout schedule. Our availability pages record the current published position and nothing more.
Do you accept guest posts or sponsored content?
No. The site does not publish paid placement, sponsored posts or contributed articles, which is part of what keeps the editorial rules meaningful.
Can I quote or reference a page here?
Yes, with a link back. If you are relying on a specification or a price, follow it through to Meta’s own documentation as well — a quote from here is a pointer, not a source of record.
I think a page is missing. Is that worth telling you?
Yes, and it is one of the more useful messages to send. Tell us the question you were trying to answer rather than the page title you expected, because the question is what a page has to be built around.
Four lines is all it takes.
If something here is wrong, the fastest way to get it fixed is to say which page, what it says, what it should say, and where you saw that.
For anything involving your Meta account, subscription or data, Meta’s own support is the only route that leads anywhere. See also privacy and terms.