Unidentified Information

A $75 top-up meant for one Meta ad account landed in the other. Meta's automated support, the advertiser reports, offered one fix: close the account, and the balance would go back to the original payment method. The account was closed. Three months on, no refund has arrived, and a new AI ticket calls the payment mode non-refundable. That is why a Meta ad balance refund needs a documented answer before anyone clicks close.

Can you get a Meta ad balance refund the way Google and TikTok allow?

Google and TikTok both publish a route for refunding an unspent ad balance, each with a stated timeline, while the Meta Help Centre pages we could find carry no title naming a balance refund request.

Start with the cleaner model. Google Ads Help, in its page on billing after cancelling an account (no update date shown, read 6 November 2026), says remaining funds go back to the original payment method and promotional credits are not eligible. Bonus credit never returns; only money you paid does. There is no request form, and status shows on the Billing Summary page.

Timing is stated too. Google typically processes card and direct-debit refunds within 2 weeks, and your bank can add up to 10 business days. Add them and you get roughly 4 weeks end to end, exactly where Google says to contact Support. That sum is our reasoning, not Google's: a slow bank leaves no slack between waiting and chasing.

TikTok is slower and stricter. TikTok Ads Help (last updated June 2025) lets an admin request a refund of the unspent balance, excluding taxes paid, if the account is in good standing, and says to expect it within 60 days. Taxes already paid do not come back, so the refund can be smaller than your balance. A closed ad account cannot be reopened. Leaving a platform always costs something, as we priced for cloud providers under the EU Data Act and for a Google Photos Takeout.

Four figures settle whether a refund is worth requesting, and two are our arithmetic, not a platform's.

TikTok's own page treats two months as normal, so a refund still pending at week five is overdue on Google and routine on TikTok. Lost credit is different: it is not delay, it is money that never returns.

What do Google and TikTok promise, and what does Meta publish?

Google promises a refund in about 2 weeks plus bank time and TikTok within 60 days; for Meta we confirmed no timeline, because the relevant Help Centre page was closed to our fetch.

Meta is the gap. Its manual payments page blocks automated fetching, so we read no Meta policy text, only the titles of several Help pages. A title is not a page, and we found nothing either way on moving a misdirected top-up between accounts.

The Meta row is a prompt to get an answer, not a finding about Meta.

Worked example: assume $1,000 sits unspent. On Google, $150 of it is promotional credit, so $1,000 less $150 returns $850. On TikTok, assume 8% of it is tax already paid, so $1,000 times 0.92 returns $920. Google's worst case is 14 days plus 10 business days (two weeks), so 28 days; TikTok's 60 is 32 days longer. These are assumptions, not a forecast. Enter your own figures below; it takes under a minute.

What goes wrong when the only route is a chat assistant?

The risk is irreversibility: TikTok says a closed account cannot be reopened, and one advertiser reports that closing a Meta account on an assistant's advice left the balance with no route out.

Closing feels like the tidy move, or at least the one the assistant offered. Google's page is titled for billing after cancelling, so the vendor expects you to need billing screens once the account is gone. In our view a route that vanishes with the account is the weaker design, and it leaves you as stuck as owners of Nest thermostats a year after end of support.

Failures are quiet. TikTok's page says a failed refund shows a banner: "Your refund request was unsuccessful. Update your bank details to try again." The cause is a stale bank record. Whether a payment mode labelled non-refundable can lawfully hold a balance after closure, these pages do not say, and we would not assume either way.

• Promotional credit: Google will not refund it, so your paid balance is smaller than the total.
• Taxes paid: TikTok excludes them from the refund.

The decision is whether to close an ad account now or hold it open until the refund route is confirmed in writing: hold it open. This week, list your ad accounts, note each balance, and ask each platform's support in writing how it would be refunded and whether closing is required. Skip that only for suspended accounts or TikTok Business Center accounts, where other processes apply.

The part that failed is not on your wall. A 2nd gen Nest Learning Thermostat still clicks the furnace on at the hour you set years ago. What broke sits in Google's data centre: since the Nest end of support date, 25 October 2025, the thermostat has been unpaired from the app and cut off from updates, and its Nest Protect shut-off no longer runs. Owners have three exits. Only one is really about money.

Will a thermostat still work after Nest end of support?

Yes: a 1st or 2nd gen Nest Learning Thermostat keeps running its pre-set schedule and every setting on the device, but anything that reached it through Google's servers stopped on 25 October 2025.

Google's end-of-support page lists what went: app status and remote control, notifications, third-party assistants, Home/Away Assist and multi-device Eco. That last pair hits the bill: an empty house now stays heated until somebody sets Away by hand.

Two lines there matter more. Protects disconnect and, in Google's words, "emergency shut off will no longer run", so a carbon monoxide alarm sounds but the furnace keeps going. And the units "continue to report logs for issue diagnostics" while getting no "software or security updates".

Four numbers frame the decision: Google's cut-off and model list, and offer amounts from 9to5Google's 25 April 2025 report, since Google says only that owners were emailed an offer.

The unpatched stretch keeps growing. That is exposure, not a known attack: any flaw found from now on stays open for as long as the unit sits on your network.

On TechSpot's forum thread about the April 2025 announcement, one commenter called replacing a thermostat every ten years "ABSOLUTELY unacceptable". We agree with the instinct, if not the capitals: this thermostat's life was set by a server, not by wear. It echoes Microsoft's extended security updates for Windows 10, minus any option to pay, and the EU right-to-repair duties that began on 31 July 2026 help little, because nothing here is broken.

Three exits, matched to the house you have

The right exit depends on facts you can check in minutes: which Nest generation is on the wall, whether a Nest Protect is paired to it, and whether you own a Mac or a Linux computer.

Find the first row that describes your home. Google lists only 1st and 2nd gen models; check yours with the guide its support page links.

No row says buy for the energy bill, and the sum below shows why.

Worked example: take a US home at the more than $900 a year in heating and cooling that ENERGY STAR's smart thermostat page cites (retrieved 30 October 2026). Assume the old Nest now wastes the full 8% an ENERGY STAR technical bulletin credits a smart thermostat with, an estimate dating from the label's 2017 launch. Pay the US offer price as of April 2025: $279.99 less $130, so $149.99. The saving is $900 x 0.08 = $72 a year; payback is $149.99 / $72 = 2.1 years, or 3.9 at full price. That 8% is a ceiling, since your schedule still runs. Halve it and the offer price takes 4.2 years. Your own bill is on your utility's annual statement; set the first slider to it.

What can go wrong with each exit?

Every exit trades one risk for another, and the trade is sharpest with NoLongerEvil: remote control without Google, set against a real chance of bricking the thermostat you meant to save.

The NoLongerEvil GitHub repository, at v1.0.1 as of 30 October 2026, needs macOS or Linux with Node.js 18 or later; Windows cannot flash it. It warns that improper firmware can brick the device, and its firmware and server code "will be open sourced soon", so you cannot yet audit what you install. AndroidHeadlines reported on 4 November 2025 that the developer advises trying it only with a backup thermostat.

The hosting choice matters too. NoLongerEvil's cloud swaps one company's server for another's; the Home Assistant add-on keeps control at home, which a second TechSpot commenter suggested via a Raspberry Pi of about £40. Only that version fixes the problem rather than moving it. Well, most of it.

Replacing has small print too. The discount came by email; Google's page tells anyone who missed it to contact Google Support. Canadians were offered $160 off and Europeans half off a tado X kit, as 9to5Google reports no new Nest thermostats for Europe. Any new connected thermostat faces its own cut-off, so, as with a Google Photos Takeout export, keep locally what you can.

• After blocking Wi-Fi, check the displayed time stays right for a few days.
• Google does not say whether a newer thermostat restores the Protect shut-off; ask Google Support before buying for that.
• No end date is published for the offer, so do not assume it will wait.

Our call: the decision is control, not energy. Keep the thermostat and block it at your router this week, unless a Nest Protect relied on that shut-off; then price a replacement and have Google Support confirm the shut-off works with it before you pay. Flash NoLongerEvil only with the computer and the spare in hand. Replace for comfort only if you miss the app.

Unzip your first Google Photos Takeout and the pictures are not the strange part. The strange part is the second file that turns up beside them. Google's help page says anything that is not part of the original photo, such as comments, is saved to a separate JSON file. Delete your library before you know that and you are trusting a copy you never opened.

Why does every Google Photos Takeout come with JSON files?

Because Takeout stores anything that is not part of the picture file itself, such as comments, in a separate JSON file, so a photo can arrive with a companion that should stay beside it. Move the pictures without it and that extra context is lost. A file readable in only one app is how formats outlive their makers, and what happens to your Microsoft Publisher .pub files shows the cost.

The original dates survive, just not in the file date. Google's Photos help page says your operating system can stamp the file with a new timestamp, while the original date stays in the embedded metadata. A tool that reads only the file date can pile years of pictures onto the afternoon you unzipped them. Sort by date taken instead.

The Apple route has the same shape. Apple's transfer page, published 29 September 2026, says shared albums, smart albums, Live Photos and some metadata are not sent, and only the latest edit of a photo goes across, not the original. Most transfers take three to seven days, and iCloud is left as it was. Advanced Data Protection, Apple's end-to-end encryption option, blocks the export while it is on, so you choose between encryption and the copy. For the wider fight over leaving a provider, see EU Data Act cloud switching costs. Cancelling storage the moment a progress bar finishes is outdated advice.

Four numbers decide whether a photo export finishes. Two are published limits, read in October 2026, and two are our arithmetic on a hypothetical 200 GB library.

The slowest-line figure is the one to question. It is not a published limit: it divides the library's megabits by the seconds in a week and assumes the line never pauses. A household that streams in the evening needs headroom, and we would plan on double.

What should you check before you delete anything?

Four situations change what you should do, namely big libraries, accented file names, Apple's Advanced Data Protection and slow connections, and the table below gives each one action plus a default for everyone else. Find the row that sounds like you and read across.

Read down the middle column and one pattern shows: every action is cheap now and impossible later, once the source is gone.

Can your line finish a 200 GB download before the link lapses? At 5 Mbps it uses about half the week, and at 2 Mbps it cannot finish. The bars are our arithmetic, 200 GB × 8 ÷ speed against 168 hours, and assume a flat-out connection, so read them as best cases.

Worked example: take a hypothetical 200 GB library and 50 GB archives, so 200 ÷ 50 = 4 archives. The download is 200 × 8 = 1,600 gigabits, or 1,600,000 megabits. A week is 7 × 24 × 3,600 = 604,800 seconds, so on these assumptions the line must average 1,600,000 ÷ 604,800 = 2.6 Mbps. Multiply your own gigabytes by 0.0132 for your number, then compare it with a speed test taken on a busy evening.

How long does a Google Photos export link last?

Google's account help page says each export archive expires in about seven days and allows five downloads, after which you must request another, so a stalled download can force a fresh export. These are the limits as of October 2026.

The same page offers zip or tgz. Zip opens on almost any computer, while tgz may need extra software on Windows and cannot carry Unicode characters in file names. We would take zip every time.

A phone that might be reset in a repair is the same problem on a deadline: what the EU right to repair owes you covers the rights, and the export covers your photos. Four traps remain.

• Names: Apple says transferred albums and videos arrive with names starting 'Copy of', so they sort under C.
• Late changes: Google says photos added or deleted after you request an export may not appear, so request again if you kept shooting.
• Rolling backups: Google can schedule an export every two months for a year, but only with Google Photos selected alone, and not under its Advanced Protection Program.
• Motion and edits: neither company explains how every Live Photo or edited copy is handled, so test one of each.

The decision is whether to delete the originals, and the answer is not yet. This week, request one export, download every archive the day it is ready, then open three photos from different years and read the date taken. Delete only when those dates match, the archive count adds up and, on the Apple route, the transfer has finished.