Privacy Policy
Last updated: 2026-10-13.
This Privacy Policy explains how Pavel Valynets PR Beograd, sole proprietor registered in Serbia (MB 67436644, PIB 114255826), Jurija Gagarina 231, 11070 Novi Beograd, Serbia ("UPGeoSEO", "we") handles personal data. We act as a controller for the data you give us to run your account, and as a processor (a "service provider" under US state laws) for the data we handle on your behalf to operate the Service for your sites. We are based in Serbia; you can reach us at [email protected].
1. Data we collect
- Account data (controller): your email, your name if you give one, and login credentials (passwords
are stored only as salted hashes, and if you turn on two-factor sign-in, its secret and recovery codes); billing identifiers from our payment provider (we do not store full card numbers). This is the account and billing data described in this section; we do not collect more account data than is listed here.
- Teammates and members (controller): if you invite people to your account: their email address, the
role you give them (admin, editor or viewer), the sites they may see, and the invitation itself (a single-use link, stored only as a hash). One person can belong to several accounts, for example a freelancer who works for two agencies; we then keep one membership per account, each with its own role and site limit, and remember which account they last switched to. The owner of an account decides who is a member, what role they hold and when they are removed, and an admin can do the same except for the owner; an admin can also manage billing and create API tokens for the account. A member sees only the data of the accounts they belong to, and only the sites they are allowed to see; the owner of an account is the controller of that account's site and content data, and we handle it for them (§9).
- Support requests (controller): your email address and your message; for an agency, also the package,
the site and the recent publishing status the request is about. If you ask about a custom package for a larger number of sites, by email or through any contact form we offer: your name, your email address, your agency's name, the number of sites and your message. Never a password or a token.
- Site & content data (processor): the content of the site(s) you connect, the brand information you
provide, and the content the Service generates and publishes for you. You can also run an audit on any public website, such as a prospect's: we read the public pages of that website and keep the audit results.
- Article ideas (processor): for each article we write we keep the idea it was written from (the angle, the
reader it speaks to, the hook and the section headings) and a numerical fingerprint of its outline. We use them for one purpose: to keep your articles distinct from one another and from the articles we write for other customers on the same topic. For this we compare fingerprints, which are lists of numbers, across all customers' sites. The only thing a comparison returns is a similarity score and a generic label for the kind of angle, such as "a price comparison" or "a beginner's how-to". No title, keyword, text, brand name, address or reader description of one customer is ever shown to another customer or put in front of the AI providers that write for them. Nothing is shared with other customers: fingerprints and ideas stay in our database, and are deleted with the site.
- Connected analytics (processor): when you connect Google Search Console / Google Analytics, we
read the metrics needed to plan and measure content, including how many visits to each article came from our own social posts. See the Google disclosure in §6. When you connect a Bing Webmaster account, we read the traffic, search-query, page and crawl information Bing reports for your site.
- Connected social accounts (processor): when you connect a Facebook Page, an Instagram professional
account, a Threads profile or a Telegram channel, the identifiers and, where the platform issues one, the access token needed to post to it on your behalf. See §7.
- What you ask our AI assistants (processor): the questions you put to the audit advisor, the brand-voice
advisor and the support assistant, and their answers, which are stored with your account and sent to the AI providers in §3 to produce the answer.
- Free audit (controller): the web address you audited and its results, a hashed (not raw) form of your
IP address to limit abuse, and your email address only if you ask for the report. Whether you also want marketing email is a separate, optional choice (§7A).
- Weekly results email (processor): each week we email the people on your account who can see a site a
short summary, up to three charts and a PDF report attached to the email. The PDF contains the same figures as your Performance page for that site: clicks and impressions, per-article results, indexing status, keywords, AI-search results and the work we did that week. It is sent through Resend (§3). The charts are small pictures that your mail program loads from our server when you open the email; the address of each picture holds the figures it draws and a signature, and nothing that names you, your account or your site. Anyone who has a picture's address can view that picture, so treat the email as private. Every such email carries an unsubscribe link.
- Usage data: logs and technical data needed to run and secure the Service, including the IP address
and browser details of your sign-in sessions, counters that limit abuse (keyed by IP address and deleted within two days), and logs of our servers that carry identifiers and short outcomes; we do not intentionally log article text, passwords or tokens. Failed web requests are logged at our edge with only the status, the request method, the part of the Service that answered, the host name and the timing, and without IP address or path. Error reports (identifiers only, with credentials removed) stay on our own systems.
- Website analytics: on our website upgeoseo.com, and only if you accept analytics cookies, visit
statistics through Google Analytics (see the Cookie Policy).
2. Why we use it (legal bases)
To provide the Service (contract), to bill you (contract), to secure and improve it and to answer your support requests (legitimate interests), and to keep the articles we write for different customers distinct from each other (the article-ideas comparison in §1: part of providing the Service, and our legitimate interest in giving every customer original content), and to keep the records the law requires, such as tax and accounting records (legal obligation). Where we ask first, we rely on your consent: marketing email, analytics cookies, and the connections you authorise on Google, Meta, Telegram or Microsoft; you can withdraw it at any time. We send you service and transactional emails (for example, account, security, and billing notices) as part of providing the Service. We send marketing or promotional emails to people who opted in and confirmed their address, and you can withdraw that consent or unsubscribe at any time. Separately, we may contact businesses about UPGeoSEO on the basis of our legitimate interests, as §7A describes. Where we rely on legitimate interests you can object at any time (§9).
3. Sub-processors
We use a small number of third parties to run the Service. They process data only to provide their service to us, under contractual data-protection obligations (EU Standard Contractual Clauses / UK IDTA where applicable):
- Creem (creem.io) — payment processing and merchant of record for subscriptions (billing and
payment data; card details are handled by Creem's own payment providers, not by us).
- Resend — transactional email delivery (recipient address and message content).
- Anthropic (Claude) and Google (Gemini) — AI text generation: writing and translating articles
and social captions, analysing your brand and your site audits, the assistants in §1 and the drafting of the business messages in §7A. They also do the planning work around your keywords: judging which keywords fit your business, grouping keywords that search for the same thing, and working out the features your site offers. For this they receive your brand description and topics, the features and page titles we read from your public site, and the keywords themselves. Google (Gemini) also creates the images for your articles and turns the idea and outline of each article (its keyword, title and headings) into the numerical fingerprint described in §1. What they receive is content prompts, generated text and what you type to the assistants; no end-user personal data is intentionally sent. We use their paid API products, under terms that do not allow them to train on data sent through the API, and we do not train AI models on your content ourselves.
- DataForSEO — keyword research: keyword phrases with a country and language, and the public addresses
of your site and its competitors; asking AI answer engines questions about your topics, to see whether your site is cited (the question text with a country and language); and, for §7A, searches for businesses in public listings. No account, email or Google identity is sent.
- TypeSafe — quality scoring of the text of the articles we write for you (the article text only; no
account, email or site identity is sent).
- Google (PageSpeed and Chrome UX Report APIs) — the public address of your site, to measure how
fast it loads.
- Microsoft (Bing Webmaster Tools) — only if you connect a Bing account (see §1). We also ask it for
market-wide keyword volumes; no site, account or person is sent with that request.
- Meta (Facebook, Instagram, Threads) and Telegram — only if you connect a channel; see §7 for what each
receives and returns.
- IndexNow search engines — the web addresses of the articles you publish, when you have set up IndexNow
for your site (§4).
- Google (Tag Manager and Analytics) — only on our website upgeoseo.com and only if you accept
analytics cookies; see the Cookie Policy.
- Hetzner — hosting of the application and its database, in the European Union.
During a site audit we may also load the public pages of the audited site in a browser service that runs on our own equipment; it receives only those public page addresses.
- Cloudflare — delivery and security of our websites (HTTPS, DDoS protection), and storage of
database backups and of the images we generate for your articles.
We will notify you of any intended change to this list before a new sub-processor begins processing.
4. Sharing
We do not sell your personal data. We share it only with our sub-processors, as required by law, or in a business transfer. We do not show or give one customer's account data, drafts, keyword plans, analytics or other private content to another customer. Our payment provider (creem.io, merchant of record) processes your payment data as an independent controller for that purpose. The articles you publish are public on your own site, and their web addresses are sent to search engines through IndexNow when you have set it up. Anything you give to other people is shared at your direction: teammates you invite, and anyone you send a client report link or a report to.
5. International transfers
UPGeoSEO is operated from Serbia, outside the EEA; our servers are in the European Union (Finland). Several of our providers operate from the United States or other countries outside the EEA/UK. Where personal data is transferred out of the EEA/UK, we rely on appropriate safeguards with each recipient: an adequacy decision where one applies, the EU–US Data Privacy Framework where the recipient participates in it, or EU Standard Contractual Clauses / UK IDTA. If you are in the EEA or the UK and need Standard Contractual Clauses for the data you entrust to us, contact [email protected].
6. Google user data (Search Console and Google Analytics)
This section applies only if you connect Google Search Console or Google Analytics to a site. It lists what we receive from Google, why, who else receives it, how it is protected, and how to remove it.
Limited Use. UPGeoSEO's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
What we ask Google for (scopes). You approve these on Google's own consent screen. We request two scopes, both read-only, and nothing else. We do not offer "Sign in with Google" and we request no profile, email, contacts, Drive, Gmail or advertising scope.
https://www.googleapis.com/auth/webmasters.readonly— Search Console, read-only. To find the Search
Console property that matches your site; to read that property's search performance (the search queries, pages, clicks, impressions, click-through rate and average position); and to check whether Google has indexed the pages we publish (URL Inspection). With this scope we cannot change anything in your Search Console.
https://www.googleapis.com/auth/analytics.readonly— Google Analytics 4, read-only. To find the GA4
property whose web data stream matches your site's address, and to read its reports: users, sessions, pageviews, engagement, traffic channels, top pages and visits that come from AI assistants such as ChatGPT or Perplexity.
A connection made while an earlier version of UPGeoSEO was live (September to October 2026) may hold a wider read-write Search Console permission (https://www.googleapis.com/auth/webmasters). UPGeoSEO never uses it to write anything. To remove it, disconnect and connect again, or revoke access on your Google account's permissions page (see below).
What we store. For each connected site:
- the access and refresh tokens Google issues to us (encrypted, see below), the Search Console and GA4
properties we matched to your site, and the scopes Google granted;
- per-article figures for the articles we publish: clicks, impressions, click-through rate and average
position of the article's page and of its target keyword, and GA4 organic sessions, engaged sessions and visits from AI assistants, captured periodically; and the number of GA4 sessions that reached the article through the links in our social posts (they carry standard UTM tags, §7), in total and split by platform;
- the number of sessions your site received from social networks over the last 28 days, by platform, kept only
to tell whether your analytics drops our tags, so that we do not show you a misleading zero;
- your site's total clicks for the last 28 days, and the indexing status Google reports for each article
URL we publish;
- the results of your site audits: the Search Console figures behind each finding and the search queries a
run used as evidence;
- a search query your site earns impressions for, when it is saved as a keyword or topic in your content
calendar.
The figures are totals: we read no visitor-level data (no individual's visits, identifiers or IP addresses) from Google Analytics. The charts and top queries on your Performance page are read from Google when you open the page; we do not keep a copy of the full report.
What we use it for. Only to provide the features you see in the product, for your own site: the Performance page and Overview, the weekly results email to you, measuring what the articles we publish achieved (including how many visits the links in our social posts brought), checking whether Google has indexed them, running and explaining your site audit, and choosing topics and keywords for new articles on your site, including a new language. We do not use it for anything else, and not for the benefit of other customers.
Who else receives it. Google data leaves UPGeoSEO only on these paths:
- AI providers: Anthropic (Claude) and Google (Gemini), listed in §3. They receive Search Console query
text and a few numbers, for three tasks. (1) Auditing a page: its single top search query with that query's impressions, clicks and average position, so the model can judge whether the page answers what searchers wanted; the audit assistant can also read the queries a run recorded when you ask it. (2) Planning keywords: up to 15 of your top search queries. (3) Launching a new language: up to 12 of your top queries and page names, so the model can name the topics behind them. Google Analytics data and OAuth tokens are never sent to an AI provider.
- Keyword-data provider: DataForSEO, listed in §3. A search query that has become a candidate keyword may
be sent to it as plain text, with a country and language, to look up its monthly search volume. No site, account or Google identity is sent with it.
- You, and the people you choose to share it with. The weekly results email (sent through Resend, §3)
and the PDF attached to it contain your own totals and per-article figures and go to each person on your account, or who is a member of it, who can see that site, and our API and MCP tools return your own Search Console and Analytics data to the tools you connect with your own access token. If you create a client report link or send a report PDF, that page or file shows your site's own Search Console totals (such as clicks and impressions) to whoever you give it to (anyone who has a link can open it, so share it with care); you can revoke a link at any time.
We do not sell, rent or give Google data to anyone else, and we do not share it between customers.
AI and machine learning. We do not use Google user data to develop, train, fine-tune or improve any AI or machine-learning model, ours, our providers' or anyone else's, and we do not build datasets from it. The AI providers above process it only to answer the single request we send for one site's feature, through their paid API products, under terms that do not allow them to train on data sent through the API.
No sale, no advertising, no human reading. We do not sell Google user data, we do not use or transfer it for advertising (including retargeting and interest-based ads), and we do not transfer it to data brokers. Our staff do not read it unless you ask us to and agree to specific data, it is necessary for security (for example, investigating abuse), or the law requires it. Otherwise it is only processed automatically.
How we protect it.
- In transit. Every page and API is served over HTTPS and plain HTTP is redirected to it. Our site and
our app both tell browsers to use HTTPS only (HSTS). Traffic from our network provider to our server is encrypted as well. We call Google, our AI providers and our keyword-data provider only over HTTPS.
- At rest. The access and refresh tokens are encrypted before they are written to the database, with
AES-256-GCM. The key is held in the server's environment, not in the database, so a copy of the database or of a backup does not expose a usable token. Passwords are stored as salted hashes.
- Where it lives. Our database runs on a server hosted by Hetzner in the European Union (Finland) and
is not reachable from the internet. Database backups are kept in private storage, with access separate from the application's, and expire after 30 days.
- Access control. The pages, routes and tools that read or change a site's Google connection or data
first check that the account the signed-in person is acting in owns that site and that their role allows it, so one customer cannot reach another's data. Access to the production server is limited to the people who run UPGeoSEO. The admin area shows operational information such as accounts and support requests, not your Search Console or Analytics figures. A password reset signs your other devices out.
- Secrets stay out of logs. Our error tracking sends identifiers only and redacts tokens, keys, cookies
and bearer credentials from every message before it leaves our servers.
- Minimum scopes. We ask only for the read-only permissions the features above need, and we will show any
wider permission on Google's consent screen before we use it.
How long we keep it, and how to remove it.
- Tokens and property links — until you disconnect, delete the site or close your account. Disconnecting
or deleting the site deletes them at once, asks Google to revoke the permission, and we make no further requests to Google for that site. Google keeps one permission per Google account for UPGeoSEO, shared by every site of yours that uses that account, so while another site of yours is still connected we leave it in place; you can always remove it on Google's own page (see below).
- Figures, indexing status, audit results and saved keywords — while the site exists; they are deleted
with the site. Disconnecting does not delete the figures we already stored. To have them removed while keeping the site, email [email protected] and we will complete the request within 30 days.
- Backups — copies in backups expire within 30 days.
To disconnect: sign in at app.upgeoseo.com, open your site, then Performance, and press Disconnect next to your Search Console property. Search Console and Google Analytics share one Google permission, so this disconnects both. To delete a site and all its data, including its Google tokens and figures: open the site's Settings, then Danger zone, and press Delete site. To close your account, email [email protected]; we delete its sites, and so this data, within 30 days. To revoke the permission yourself at any time, open your Google Account permissions, choose UPGeoSEO and remove access. Once revoked, our next request to Google fails and the connection shows as needing to be reconnected.
7. Social platforms (Facebook, Instagram, Threads, Telegram)
You can connect your own Facebook Page, Instagram professional (Business or Creator) account, Threads profile and Telegram channel, so that UPGeoSEO posts a short caption and the link to each new article. For this we act as your processor: the accounts, posts and audience are yours, and we handle the connection only to publish on your behalf. We receive data from Meta only through its official APIs, after you approve it in Meta's own consent screen, and we use it in line with the Meta Platform Terms and Developer Policies. UPGeoSEO is not affiliated with or endorsed by Meta Platforms, Inc. or Telegram.
What we receive
- Facebook: the ID and name of the one Page you pick in Facebook's dialog, and an access token for that
Page. Your own user token is used once, while connecting, to list your Pages and obtain the Page token, and is then discarded.
- Instagram: the ID and username of your professional account, and an access token (valid for 60 days;
we refresh it automatically while the channel is in use).
- Threads: your Threads user ID and username, and an access token (valid for 60 days; refreshed in the
same way).
- Telegram: the numeric ID, title and username of the channel to which you add our bot (we post as
that bot, so there is no personal access token), and, for the ten minutes while you connect, the Telegram user ID of the person who added the bot, so that one person's click cannot connect another person's channel.
For Facebook and Instagram we also keep the app-scoped user ID that Meta assigns to you, only so that we can find your connection if Meta tells us you removed the app or asked it to delete your data.
We do not receive or store your password, your messages, your followers or audience lists, your profile photo, or posts that we did not publish.
Why we use it. Only to publish your own articles to the accounts you connected, and to keep the connection working: refreshing the token and telling you when a connection needs to be authorised again.
Links in your posts. The link to your article in each post carries standard UTM tags (the platform as source, "social" as medium and a fixed campaign name). They put no cookie, pixel or script on your site or in the post, and we do not run a redirect of our own. If you connected Google Analytics, your own analytics shows the visits under those tags, and we read the totals back as described in §6; otherwise the tags are inert text in the address.
How we protect it. The access token, the Page, account or channel name and the username are stored encrypted at rest, with a key that is kept separate from the database. The numeric Page, account or channel ID, which is the address we post to, is stored unencrypted. Tokens are never shown in the dashboard, and are redacted from the error messages and logs we keep. A connection belongs to one of your sites and is used only for that site.
No sale, advertising or AI training. We do not sell this data, we do not use it for advertising or profiling, and we do not use it to train AI models. The captions are written by our AI providers (§3) from your article and brand description; tokens and account or channel IDs are not sent to them.
How long we keep it.
- Tokens, IDs, names and usernames — while the channel stays connected. They are deleted when you
disconnect the channel, when you delete the site or your account, and when Meta tells us that you removed our app or asked it to delete your data. A token that has expired or been revoked, or a Telegram channel from which you removed our bot, is not deleted by itself: the channel stays listed as needing a reconnect until you reconnect or disconnect it.
- Delivery record — for each post, which article went to which channel and when, whether it succeeded,
and the ID and link of the post on the platform. It contains no token. It is kept when you disconnect, so your history stays accurate, and is deleted with the article, the site or the account.
Disconnecting. In UPGeoSEO: Dashboard, your site, Social, then Disconnect next to the channel. The stored credential is deleted at once (Pause stops posting without disconnecting). In the platform: remove the app from the list of apps connected to your account (Facebook: Settings & privacy, Settings, Apps and websites; Instagram: Settings, Website permissions, Apps and websites; Threads: Settings, Account, Website permissions). Meta then notifies us and we remove the connection automatically. Telegram has no data-deletion request: if you remove our bot from a channel, the channel is marked as needing a reconnect, and the stored details are deleted when you disconnect it in UPGeoSEO or email us. Posts we already published stay on your Page, profile or channel until you delete them there.
Deleting your data. Disconnecting deletes the credential. To have the platform data we hold removed, follow the steps on our data deletion page, or email [email protected] and we will complete the request within 30 days. Where Meta sends us a data deletion request, we process it automatically and the confirmation link Meta shows you explains what was removed.
7A. Marketing email and business outreach
Marketing email you ask for. On the signup form and on the free audit there is an optional box, never ticked for you, for occasional email from us with news and offers from UPGeoSEO. If you tick it we record your email address, the exact wording you saw and its version, the language, the time, and a hash of your IP address, and we send nothing until you confirm your address. Saying no changes nothing about your account or your report. You can withdraw with one click from any marketing email, on a public unsubscribe page, or in your account settings. We then remove your address and keep only a one-way hash of it, so that we never email you by mistake, and the timestamps of the grant and the withdrawal, which we delete after three years. A grant that is never confirmed is deleted after 30 days. The legal basis is your consent.
Business outreach. We contact small agencies and freelancers about UPGeoSEO. For this we use business information the agency published on its own website or in a public business listing: the business name, website, public business email address or phone number, postal address, a named contact and role where the agency published one for business use, and the languages and services it describes. We collect it from the public web and from business-listing and search-result data we buy from DataForSEO (§3), and an AI provider (§3) helps us read the public pages and draft messages; it never chooses who is contacted, how, or what is offered. We do not collect sensitive data. Our legal basis is our legitimate interest in finding business customers (Article 6(1)(f) GDPR; Article 12(1) point 6 of the Serbian Law on Personal Data Protection); if you ticked the marketing box and confirmed your address, it is your consent. We contact people by a connection request or message on LinkedIn that a person writes and sends, by post, and by email only where the law of your country and our own rules allow it. Every message says where we found your details and how to object, and repeats this in each follow-up.
We keep this data for 180 days after our last activity, unless you reply, in which case we keep it for 12 months after our last exchange; if you sign up, we keep only the fact that you came from our outreach. You can object at any time, by the unsubscribe link in a message, by replying "stop", or at [email protected]; we stop at once and, if you ask, delete your data. To make sure we never contact you again we keep a one-way hash of your address (and, if you ask us to erase your agency's data, of its domain), not the address itself.
7B. WordPress plugin
If you install the UPGeoSEO WordPress plugin and connect it to your account, the plugin sends us your site's address, the WordPress and plugin versions and the site's language, and, to monitor indexing, the list of public page addresses on your site with their post type and last-modified time. It never sends visitor data, post content or user accounts. For each page we ask Google's URL Inspection API, through the Search Console connection you approved (§6), and store the result: the indexing verdict, the coverage state, the canonical addresses Google and your page report, the last crawl time and Google's response. We also store a site-scoped access token for the plugin, as a one-way hash and a short display prefix only; you can revoke it at any time by disconnecting the plugin. This data is used only to show you your indexing status and to tell you when it changes. We keep it while the plugin is connected, and it is deleted with the site when you delete the site from your account (§8). The legal basis is performing the Service for you.
8. Retention
We keep personal data only as long as needed for the purposes above and to meet legal obligations, unless a longer period is legally required:
- Account data — kept while your account is active and deleted within 30 days after you ask us to
close your account (or after we close it).
- Generated content and connected-site data — kept while your account is active; deleted with the
account. This includes what you asked our AI assistants and their answers.
- Article ideas and fingerprints — kept with the article and deleted with it, with the site or with the
account (§1). A chosen idea whose article was never written stops being used after three days.
- Teammates and members — kept while they belong to the account. When the owner or an admin removes
someone, or a member leaves, their access to that account ends at once, together with the API tokens they created in it. A person who was invited into this account as their only account has their login deleted; a person who belongs to other accounts keeps their login and those accounts. Content they helped create belongs to the account and stays.
- Free audit results — kept for 30 days, then deleted automatically.
- Audits of other websites — the free audit you run on another website (an agency's prospect, for example) is
not saved. A full audit is kept in a workspace that no user can open, and is deleted 90 days after the last audit of that website.
- Social connections — see §7 for how long we keep the credentials and delivery records of the
Facebook, Instagram, Threads and Telegram channels you connect.
- Marketing consent records and business outreach data — see §7A.
- Support requests — kept as long as needed to answer them and for our records, and deleted when you
ask.
- Sign-in sessions and invitations — a session ends after 30 days or when you sign out; an invitation
link works once and expires after a few days.
- Server logs and technical/usage data — kept on our own server in rotating, size-limited storage. There
is no fixed deletion date: the oldest entries are overwritten first when the storage is full, which takes weeks at today's volume. Abuse counters keyed by IP address are deleted within two days. Database backups expire after 30 days (§6).
- Weekly results emails — the PDF is generated for each email and we do not store it separately; copies
stay in the mailboxes they were sent to.
- Billing records — kept as long as required for tax, accounting, and legal obligations.
9. Your rights
Depending on where you live, you may have rights to access, correct, delete, restrict, port, or object to the processing of your personal data, and to withdraw consent. To exercise them, contact us at [email protected]; we answer within 30 days. For data we process on a customer's behalf, we will refer your request to that customer. You may also complain to a supervisory authority: in Serbia, the Commissioner for Information of Public Importance and Personal Data Protection (Poverenik za informacije od javnog značaja i zaštitu podataka o ličnosti), or the authority of the country where you live or work.
Members of someone else's account. If you were invited into an account, its owner decides which sites you see and when your access ends, and the site and content data in that account is theirs. Your own sign-in data (your email address, name and login) is yours: you can ask us to correct or delete it, and you can leave an account yourself from your Profile at any time.
Agencies and client sites. If you use the Service for your clients' sites, we process the site, content and connected-account data of those sites (for example the site's content and the business details and people named in it, its search and analytics figures, and the identifiers of connected social channels) on your behalf and on your documented instructions, which are your use of the Service and its settings: you are the controller of it, or the processor for your client, in which case we are your sub-processor. We process it only to provide the Service (to crawl, generate, publish and measure), for as long as your account is active and for the periods in section 8. We keep it confidential, make sure the people at UPGeoSEO who can reach it are bound to do the same, protect it as described in this policy, and use only the sub-processors in section 3 under written data-protection terms, telling you before we add one; you can object by ending your subscription. We tell you without undue delay if we learn of a personal-data breach that affects it. We help you answer requests from the people your clients' sites concern (section 9), delete or return the data when you ask or your account ends (a site export is available in the dashboard), and answer a written request for the information you need to check that we comply. A request from one of your clients' audience that reaches us is referred to you. For transfers of this data to us, see section 5.
Children. The Service is for business use and is not directed at anyone under 18. We do not knowingly collect personal data from children; if you think we have, contact us and we will delete it.
10. Cookies
See our Cookie Policy. We set only the cookies it lists; analytics cookies on our website are set only if you accept them.
11. Changes and contact
We may update this Policy; material changes will be notified by email and/or an in-app notice at least 14 days before they take effect. Contact: [email protected] · Pavel Valynets PR Beograd, sole proprietor registered in Serbia (MB 67436644, PIB 114255826), Jurija Gagarina 231, 11070 Novi Beograd, Serbia.
