This Privacy Policy explains how LastSave handles your information. The short version: LastSave is local-first. Your library, play history and journal are written to a database on your own machine, and the app works without a connection. Section 3 lists everything that leaves your computer, and what you can switch off.
The sections below describe how the app works today. LastSave is in active development, and some of this is expected to change: syncing your library across your devices, optional accounts, and paid plans are all planned. Section 7 explains what happens to this Policy when they arrive.
1. Where your data lives
Everything you create is written to a local database on your own computer. In this version of the app there is no sign-up, no login and no cloud sync.
A future version is expected to offer syncing your library across your devices, which would mean storing a copy on servers we run. That is a feature you would turn on, and this Policy will describe it before it ships.
2. Data stored on your device
The following information is stored locally so the app can work:
- Your library and play history — the games you add, their status, ratings, play sessions, and journal entries, and the achievements your platforms keep for those games.
- Your profile — a nickname, an optional avatar, your favorite genres and games, and a PC build snapshot (CPU, GPU, RAM, and operating system) that you can view and share within the app.
- App settings — your preferences, such as theme, language, and overlay options.
- A local cache — game metadata downloaded from IGDB, and the addresses of each game's banner and logo, kept so the app is fast and works offline.
- Your art choices — which banner and logo you picked for a game, and the two art switches in Settings.
You can delete this data at any time by removing the app's local database.
3. Information that leaves your device
LastSave connects to the internet on its own to look up the games in your library:
- Game metadata — covers, descriptions, genres and release information from the IGDB service.
- Game art — the wide banners and logos shown behind and over a game, from the SteamGridDB community and from Steam's store pages.
These lookups go through LastSave's own servers (igdb.lastsave.app and api.lastsave.app). A
lookup names the games it asks about — their IDs, titles and release years, or what you typed in a
search — together with the app's version and, unless you turn it off, an anonymous ID for your
installation (see "Usage counts" below). There is no account, and none of your play history,
statuses, notes or journal is sent. The answer is kept so the next person who asks about the same
game gets it without asking the source again. Like any connection over the internet, your IP address
is seen by our hosting provider (Cloudflare), which uses it to limit how often one machine can ask;
LastSave does not store it.
One lookup goes to Microsoft directly instead: for a game installed from the Microsoft Store or the
Xbox app, or one on your Xbox wishlist, LastSave asks Microsoft's public product catalog
(displaycatalog.mp.microsoft.com) which product it is, so it can be matched to the right game. It
sends the package's name, the Xbox title ID or the Store product ID and nothing else — no account and
nothing about you.
The pictures themselves — covers, banners and logos — are then downloaded straight from those
services' image hosts (images.igdb.com, cdn2.steamgriddb.com and shared.steamstatic.com), the
way a web page loads an image. You can turn the banners and logos off in Settings → Art; with
both off, LastSave does not look any art up on its own.
If you choose to connect an external account (for example, to import a games list), the app communicates with that service only as needed to perform the action you asked for, using the permissions you grant.
Achievements. When a game from Steam, Epic Games or Xbox is synced — by you, or by its
auto-sync — LastSave also reads that game's achievements from the same account: which ones you have
unlocked and when, their names and descriptions, and how many players have each. It asks the
services directly (api.steampowered.com and your public Steam community page on
steamcommunity.com, launcher.store.epicgames.com, achievements.xboxlive.com and
titlehub.xboxlive.com). If you connect RetroAchievements in Settings → Emulators, the username
and Web API key you enter are kept on your device, encrypted, and used to read your progress for
your emulated games from retroachievements.org. Achievements are stored in your library on your
device and are not sent to LastSave's servers. Their pictures are downloaded from those services'
image hosts (shared.akamai.steamstatic.com, shared-static-prod.epicgames.com,
images-eds-ssl.xboxlive.com, image-ssl.xboxlive.com and media.retroachievements.org). For a
game you run in RPCS3, shadPS4, Xenia or Vita3K, LastSave reads the trophies that emulator saves on
your computer; nothing about them is sent anywhere.
Your Discord status
Off unless you turn it on in Settings → Discord. When it is on and the Discord app is running on
your computer, LastSave tells that app — over a connection that stays on your machine — what to show
as your status on Discord: the game you are playing and for how long, its cover (an adult game
shows an "18+" card instead of its cover), and, as you choose there, your total hours on it, your
rating or your latest impression, and how many achievements, milestones, journal entries and
sessions it has. You can choose not to share the game you are playing. When LastSave is open and
you are not playing, or while you play a game you chose not to share, it shows one of Savvy's lines
and the figures about your library you allow there, such as how many games it holds or how many
you have completed: counts only, never the name of a game. The status carries a button that links
to lastsave.app. Discord then shows that status to the people who can see your
activity, under Discord's own privacy policy and your Discord settings ("Share my activity").
Your notes, journal, the words of your reviews, your screenshots and anything else you wrote are
never part of it. The pictures are LastSave's mascot, Savvy, which Discord fetches from
lastsave.app, and the game's cover, which Discord fetches from api.lastsave.app: that server
takes the cover from images.igdb.com and frames it for Discord, and what it is asked for is the
cover's IGDB image number. LastSave itself checks now and then that lastsave.app serves Savvy.
Turning the setting off clears the status at once and closes the connection.
Usage counts
Each time the app asks LastSave's servers for something, the server writes one line of counts about that request. They tell us how the service is used, how many installations are active and in which countries and languages, and they let us notice a fault or an abuse early. A line holds:
- what was asked (for example "art lookup"), whether it worked, how long it took, and what it cost the server: how many games it asked about — a number, never which — and how many times it had to ask IGDB, SteamGridDB or Steam;
- the app's version;
- the country the request came from and the first language your system asks for (for example
es), as your connection already reports them — never your IP address or your city; - an anonymous ID for this installation: a one-way scramble of the random installation ID described under "Reports you choose to send", so it cannot be turned back into that ID. It is not derived from your name, your accounts or your hardware.
The lines are stored with Cloudflare, are deleted after three months, and we read them only as totals: installations per day, per country, per version, and requests and costs per kind of lookup. They never contain which games you asked about, your library, or what you do in the app.
You can turn the installation ID off in Settings → Data → Count this installation. The app then stops sending it; your requests are still counted, without anything that tells your installation apart from anyone else's.
Reports you choose to send
Apart from the usage counts above, which describe requests to our servers and not what you do in the app, nothing about your use of LastSave is sent to us unless you press Send in the report dialog (bugs, feedback, ideas, or a crash report) or Send to LastSave in the Language Studio. There is no automatic crash reporting. When you send a report, we receive:
- what you wrote, any screenshots you attached, and the contact you optionally left;
- the app version, your Windows version, the app language, and the screen you were on;
- a random ID for this installation, so several reports from the same PC can be told apart. It is not derived from your name, your accounts, or your hardware, and the usage counts never carry it — only the one-way scramble of it described above;
- if you leave "Include diagnostic log" on, the most recent part of LastSave's own log file. Before it is sent, your Windows user name and your PC's name are replaced, and passwords or access tokens are never written to that log in the first place.
A translation you send from the Language Studio carries the translation itself (its files and the list of texts you changed), your note, the name you want in the credits if you give one, the contact you optionally left, the app version and the random installation ID above. It never carries the log or screenshots.
Your library, play history, journal, saves, and media are never part of a report unless you attach them yourself. Reports are delivered to a private channel on Discord, a third-party service, where only the LastSave team can read them, and are used only to fix problems and answer you.
4. Hardware and system information
To build your PC profile, the app reads your CPU, GPU, RAM, and operating system. This information is stored locally as part of your profile and is used to power features like your PC build card. It is not transmitted to us.
5. Files and processes
To find and launch your games and to track play sessions, the app reads the game folders you point it to and observes running processes. This happens locally on your computer and is used only to power the app's features. LastSave does not upload the contents of your files.
6. Children's privacy
LastSave is a general-audience application and is not directed at children. It has no account system and asks for no personal details, so it does not knowingly gather information from a child. If you believe a child has sent us a report containing personal information, contact us through the channels in section 8 and we will delete it.
7. Changes to this Policy
We may update this Policy as the app evolves. When it changes in a material way, the app will ask you to review and accept the new version before continuing. The version you accepted is recorded locally.
The usage counts in section 3 describe requests to our servers. If LastSave ever gathers statistics about play itself, they will be aggregate and not personal — how many people play a title, how many hours in total, which source a game came from — and never the library or the activity of an identifiable person. Anything of that kind will be announced in the release notes, and will be possible to switch off.
8. Contact
LastSave is an independent, local-first project. Questions about privacy, and any request about a report you sent, can be directed to hello@lastsave.app, or to the project's public channels, including our Discord community.