Privacy Policy

What DineFile collects

DineFile collects two kinds of information: what you give it when you sign in, and what the extension reads from your own TikTok collection page.

• Your email address — through our authentication provider, when you sign in with Google or sign up with email.
• From your TikTok collection page, through the extension: the video id, the video URL, the uploader's handle, and the caption. Nothing else.
• The extension does not read your TikTok password, does not read your TikTok cookies, does not read your browsing history, and does not read anything from any page other than a TikTok collection page you opened yourself. DineFile's own use of cookies is described under "Cookies" below.
• The extension's reach: a content script that runs on TikTok pages, and a popup that talks to DineFile. It does not run anywhere else.

What DineFile does with it

DineFile processes each saved video to find the restaurant it features.

• DineFile downloads the video's subtitles and metadata itself, using yt-dlp running on our own server.
• A video's URL may go to a third-party transcript provider to obtain that video's transcript.
• The resulting text goes to a third-party language-model provider so a model can find the restaurant.
• Each restaurant's name and city goes to third-party geocoding providers to locate the venue.
• The result becomes a spreadsheet, stored for you.

Who receives your data

DineFile shares data with two kinds of recipients: providers that receive your content and process it for the stated purpose, and infrastructure that stores or carries it on our behalf.

The categories below are complete. A current list of the named sub-processors behind them is available on request at support@dinefile.com, and a change to that list is a change to this policy.

• A language-model provider — receives each video's title, description, tags and transcript text so a model can identify the restaurant. That provider routes the request onward to a model provider; its own retention practice is governed by its policy, not asserted here. The request also carries your account identifier and the internal job and video identifiers, so model usage and cost can be attributed to the account that requested it.
• Geocoding providers — receive a restaurant name and a city to find the venue.
• A transcript provider — may receive a video's URL in order to obtain that video's transcript.
• Application infrastructure — stores your sign-in, the application database, and the spreadsheet files DineFile generates for you; hosts the application, so your request traffic passes through it; and carries job identifiers between processing steps. Infrastructure that carries job identifiers does not carry video content.
• A bot-protection provider — Cloudflare Turnstile protects the sign-in, sign-up, and password-reset forms. When you open one of those pages, Cloudflare receives signals from your browser, such as your IP address and interaction data, so it can tell a person apart from an automated bot. Cloudflare's handling of that data is governed by the Cloudflare Turnstile Privacy Policy Addendum at https://www.cloudflare.com/turnstile-privacy-policy/, referenced here as Cloudflare requires; it is not asserted by us.
• A product-analytics processor — see "Analytics" below.
• Google receives nothing from the extraction pipeline. The map link in your spreadsheet is a URL DineFile composes locally from the restaurant's name and location — no request is made to Google to build it. Google is involved in one place only: if you choose to sign in with Google, you authenticate with Google and DineFile receives your email address from it.

Analytics

Product analytics are associated with your signed-in account.

This is so we can understand whether the product works — not for advertising. A third-party analytics processor handles this data on our behalf.

Your analytics processor receives and stores your account's email address alongside your account identifier.

When something goes wrong, DineFile sends a diagnostic report to the same analytics processor. It includes technical details of the failure and which part of the product it happened in. These reports are filtered to exclude credentials and provider response bodies.

The browser extension also sends those same diagnostic reports when it fails.

OpenRouter's Broadcast service sends video captions, descriptions and transcript text — the material sent to the language model and the response it returns — to the analytics processor. This user content reaches the analytics processor separately from product analytics and error reports.

Those Broadcast records now carry your account identifier, together with the internal job and video identifiers, so the analytics processor associates them with your account rather than only with ours.

Cookies

DineFile sets cookies in your browser to keep you signed in. These are necessary for the site to work — without them, every page would forget who you are.

DineFile does not use advertising cookies and does not sell or share cookie data.

The analytics processor described above also sets its own cookies in your browser so it can recognise a returning browser. These cookies are set automatically when you visit DineFile; DineFile does not ask first. When you sign in, analytics recorded in that browser before you signed in are linked to your account.

If you declined analytics on an earlier visit, that choice is still honoured in that browser.

What we store, and for how long

DineFile stores your account and job records in a hosted Postgres database, and the generated spreadsheet files in that provider's object storage.

We keep this data until you delete your account. Nothing is purged on a schedule.

The shared results cache

This cache holds no personal data.

The cache is keyed on a public TikTok video id and holds the restaurant rows extracted from that video. It carries no account identifier and no link to any account.

Deleting your account

Deleting your account removes your account, your jobs, the restaurants extracted from them, and the spreadsheet files we generated for you.

You can delete your account from the account page. This cannot be undone.

TikTok

TikTok is not a partner and receives nothing from DineFile. See the terms of use for DineFile's position on TikTok's own terms of service.

Chrome Web Store Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

That sentence is required verbatim by Google and is reproduced here unchanged. In DineFile's own words: the data the extension reads is used only to build your spreadsheet, it is never sold, never used for advertising, and never shared beyond the processors named above.

Contact

Questions about this policy: support@dinefile.com.

Akashe Strategies LLC, 2501 Chatham Rd, Suite N, Springfield, IL 62704, USA.

Changes to this policy

Material changes to this policy are reflected here, and the last-updated date at the top of this page changes with them.