Anti-Speed™ GPS spoofing for iPhone

Every tool in this category can put your phone somewhere it is not. Anti-Speed is about the other half of the problem, which almost nobody addresses: how fast you appear to be going while you get there.

This page is the long version. What it is, why speed travels alongside location in the first place, what we measured, and the parts we cannot promise.

What Anti-Speed is

Anti-Speed is a governor on the speed your iPhone reports. You set a ceiling, and the simulated location advances at or below it, no matter what the vehicle you are sitting in is doing.

It runs on the phone. Once the PinDrift app is installed, the phone reads your movement and paces its own reported location, which is why it works in a car rather than only at a desk.

Why speed is reported alongside location at all

This surprises people. A location is not just a coordinate.

When an app asks iOS where you are, it gets back a CLLocation: latitude and longitude, an accuracy radius, a timestamp, and also altitude, course and speed. Speed is a first-class field, sitting right there next to the coordinate, and any app that wants it can read it without asking you for anything extra.

Beyond that field, an app can simply do the arithmetic itself. Two positions and two timestamps give you a speed whether the field was populated or not. This matters, and we will come back to it.

How simulated movement differs from teleportation

These are two genuinely different things and conflating them is where most people get caught.

A teleport between two points 11 miles apart, four seconds apart, is not detected because the fix looked wrong. It is detected because the arithmetic is impossible. That is the single most common way anybody gets caught, and it is entirely avoidable.

How PinDrift controls simulated speed

Two modes, and they work differently.

Route replay

You draw a path and choose a pace: walking, cycling or driving. PinDrift advances the simulated position along that path at that pace, and Anti-Speed caps it. Nothing about your real movement is involved; the phone can be on a desk.

Live mode

Anti-Speed reads live movement signals from the phone, such as heading and accelerometer input, to pace the simulated location, then caps that pace at your ceiling. Real movement is an input to timing here, but the location an app receives is still the simulated one, and the cap still applies.

This is a speed-capped location simulation. It is not a change to the physical device, and it does not slow a car down.

What apps can actually see

Here is the part where we are going to be more careful than the marketing in this category usually is, because the honest answer has an edge to it.

Apps that derive speed from position see the pace you set. They take successive coordinates and timestamps, do the arithmetic, and get the capped figure. Life360's drive reports work broadly this way, which is why a drive replayed under a ceiling reads as a calm one.

Apps that read the raw speed field are a different case. In a simulated location that field is not always populated the way a real GPS fix populates it, and an app reading it directly may see a value marked unavailable rather than your ceiling. We are telling you this because it is true, not because it helps.

Apps that read motion sensors directly are outside this entirely. Anti-Speed does not modify the accelerometer, the gyroscope or CoreMotion. An app deriving speed or activity from those is reading your real movement, and nothing here changes that.

What we actually measured

A representative check we ran, so you can see what was and was not covered.

That last row is the important one, and it is the row this category never publishes.

What people use it for

• A drive that reads as a normal drive. The most common case. A route logged at a steady legal pace instead of one that spikes.
• A walk that is a walk. Route replay at walking pace, for anything that checks whether movement is plausible for a person on foot.
• Testing your own app. Feeding a build a movement profile you cannot produce by walking around the office.
• Not broadcasting a commute. A location-sharing circle that sees an ordinary journey rather than a minute-by-minute telemetry feed.

Compatibility

Fuller detail is on the compatibility page.

Limitations

Anti-Speed shapes the simulated location's speed only. It does not alter a physical vehicle or your real movement. It cannot guarantee removal from every speed report, and it cannot promise compatibility with every release of Life360 or any other app. It does not control crash detection, and it does not control accelerometer or CoreMotion data an app may read directly. App behaviour varies by app version, iOS version, device and network conditions.

It is not undetectable, and no tool can promise that. Anybody in this category telling you otherwise is either guessing or selling.

Legitimate uses, and the line

Privacy from continuous telemetry, testing an app against movement you cannot physically produce, and not broadcasting a commute to every app that asked for location once, are all ordinary reasons and they are why this exists.