Privacy Policy

The Realm — Your dream bookshelf.

Effective Date: 4 October 2026
Last Updated: 17 November 2026


1. Who we are

This Privacy Policy explains how Allyoucanreserve Ltd ("we", "us", "our") collects, uses, shares and protects your personal data when you use The Realm mobile application and related services (the "Service" or "App").

Data Controller:
Allyoucanreserve Ltd
A private limited company registered in England and Wales (company number 10162791)
Registered office: 124 City Road, London, England, EC1V 2NX, United Kingdom

For any privacy question or request, contact: privacy@therealmshelf.app

We act as the data controller for the personal data described in this Policy. We have not appointed a Data Protection Officer because we are not required to; the email address above is monitored for privacy matters.

Our representative in the EU/EEA. We are based in the United Kingdom, so we have appointed DataRep (Data Protection Representative Limited, trading as DataRep) as our data protection representative in the European Union and the European Economic Area (Article 27 GDPR). If you are in the EU/EEA, you can raise a privacy question or exercise your rights (Section 13) through DataRep instead of contacting us directly:

DataRep is for privacy matters of people in the EU/EEA only. For help with the App, your account or a subscription, email us at support@therealmshelf.app; for any other privacy question, privacy@therealmshelf.app.


2. The laws this Policy is written for


3. The short version

The rest of this Policy is the detail behind that summary.


4. The data we collect

4.1 Data you give us directly (stored on our servers)

Category Examples
Account data Email address; or the identity from Sign in with Apple / Google Sign-In (see Section 4.4 — Apple lets you hide your real email); display name; handle; bio; avatar photo; favourite genre; the books you choose to feature on your profile (currently reading, all-time favourite); Instagram/TikTok handles if you add them
Your library Books on your lists (Read, TBR, Currently Reading, DNF, Favourites, custom lists), formats, when you added them, and the order you arrange each list in
Ratings & reviews Star ratings, short reviews ("The Verdict") and extended reviews — private by default; shared only if you turn on "Share my ratings & reviews" in Edit Profile
Shelves Shelf names, book arrangements, decor placements, rendered shelf images, captions, publish status
Social activity Follows, likes, saves, comments (including @mentions), users you block, reports you submit
Spine and cover submissions A photo you add as your own spine or cover for a book. The App uploads a copy when you add it and queues it for review by our staff, and we record whether it was approved and, if not, why (see Section 8.3 — approved photos become part of the book catalogue and can appear on other users' shelves)
Books you add yourself The details of a book you add by hand (title, author, page count and any optional details) with your cover and spine photos — queued for review like the photos above (Section 8.3)
Background-remover results The cut-out image produced when you use the background remover (Section 7)
Notification data Your notification preferences and device push tokens
Your agreement to our Terms The date you confirmed you are 18 or over and accepted our Terms, and which version of the Terms it was
Support & feedback Messages and feedback you send us by email

4.2 Your notes, cover designs and own covers: a private backup

These live in the App on your device, and the App keeps a private backup of them on our servers (Supabase, in the UK — Section 8.1), so they come back when you sign in on a new or reset phone and stay the same on every device you use. The backup belongs to your account only: no other user can see it, and our staff do not see it in their moderation and support tools. It is opened only to send you a copy of your data when you ask for one (Section 13), and each time is recorded in our staff activity log (Section 11). It is used for nothing else — not for book ranking, statistics or anything shown to others.

When you delete a note, design or cover, it leaves the backup the next time the App syncs; a short record that it was deleted (so your other devices remove it too) is kept for up to 180 days, and photos nothing uses any more are removed within about a week. Deleting your account deletes the whole backup. If a different account signs in on the same device, the App removes the previous account's notes and designs from that device — they stay in that account's backup — and it asks first if anything has not been backed up yet. Local preferences and caches (for example your last-open shelf) stay on the device only.

A cover photo you add for a book is also sent to us for review, like a spine photo (Section 8.3); and if you put one of these images through the background remover, that image is sent for processing as described in Section 7.

4.3 Data collected automatically

Category Details
Crash and error data Collected via Sentry when the App crashes or errors: a pseudonymous user id, device model, OS version, App version and the technical state of the error. It is linked to your account only through that id. Session replay is disabled. Your name and email are never sent to Sentry.
Technical data Device type, OS version, App version, language and time zone. Your IP address is inherently visible to servers when the App makes requests; we do not use it to track you.
Bot check on the sign-in screen When the sign-in screen opens, Cloudflare Turnstile checks that the request comes from a real device and not a script. Cloudflare receives your IP address and technical signals about your device and the embedded browser view the check runs in; we receive only a pass-or-fail token (see Section 11). Cloudflare also uses these signals, as an independent controller, to improve its bot detection (cloudflare.com/turnstile-privacy-policy).
Book ranking signals Counts used to rank the book catalogue (for example how often a book is added across all users). So that each reader counts only once per book, we keep a note of which catalogue books your account opened or added; it is used for nothing else and deleted after 90 days.
Fair-use counters Per-account counts that enforce limits on costly features (book search, cover analysis, background removals): how many times you used the feature in a period — not what you searched for or uploaded.
App usage A few events linked to your account, stored in our own database: that you opened the App (at most once a day), that you reached a free-tier limit (and which one), that the upgrade screen was shown (and from where), that you subscribed (and to which plan), and, for the App's built-in tips, which tip was shown to you, whether you closed it and whether you then used what it showed. We use them only to set fair free-tier limits, to see whether the paid tier is worth offering and to see which tips help — never for advertising, and they are never shared or sold. You can switch them off at any time in Settings → My Account → "Share usage statistics"; the choice applies to the phone you set it on.

We do not collect: precise location, contacts, calendars, microphone audio, browsing history or advertising identifiers. We use no third-party analytics SDKs — the usage events above never leave our own database.

4.4 Data we receive from others

Source What we receive
Apple (sign-in) Your email address — or the private relay address Apple creates if you choose to hide it — and Apple's identifier for your account. The App does not ask Apple for your name.
Google (sign-in) Your name, email address and the web address of your Google profile picture, as contained in Google's sign-in token. Our authentication provider stores them with your account; the App itself does not use the name or picture.
Apple / Google / RevenueCat (purchases) Confirmation a purchase was made, plan type and renewal status — never your card details
Google Books API, Open Library, ISBNdb Book metadata (titles, authors, covers, page counts) — data about books, not about you (see Section 8.5 for what these services receive)

We never share sign-in data with advertising platforms or data brokers, and we do not combine an Apple private relay address with information from elsewhere to work out who you are.


5. Payments — we never see your card

All purchases are processed by Apple (App Store) or Google (Google Play). We never receive your card number, CVV or billing address. Subscription status is managed for us by RevenueCat, Inc., which receives store receipts and tells the App whether your account has the paid tier (revenuecat.com/privacy). So that your purchase follows your account across devices, your Realm account id is used as the RevenueCat customer id.


6. Why we use your data, and our lawful bases

Under UK and EU GDPR every use of personal data needs a lawful basis. Ours:

Purpose Data used Lawful basis
Creating your account, signing you in, running the Service Account data Contract (Art. 6(1)(b))
Core features: library, shelves, reviews, Covers, Browse Library, shelves, reviews, social activity Contract
Showing your published content to other users Published shelves, shared ratings and reviews, comments, profile Contract — publishing a shelf and sharing your ratings are always your explicit choice
Ranking the Browse feed and book search Aggregate signals, follows, likes and saves Contract, plus legitimate interests (a useful feed)
Processing your subscription Purchase confirmations Contract
Push notifications about activity on your account Push tokens, notification preferences Legitimate interests (telling you about activity you would expect to hear about), and only while your phone's notification permission is on — switch any category off in Settings
Notifications about new features and news Push tokens, notification preferences Consent — off until you switch it on in Settings; switch it off any time
Safety: moderation of submissions and comments, blocks, reports Submissions, comments, reports Legitimate interests (a safe service) and legal obligation where applicable
Reviewing the spine and cover photos you submit and adding approved ones to the book catalogue Your submissions and the review decision Contract (you submit them to be used this way), and legitimate interests (a complete and accurate catalogue)
Protecting sign-in from automated abuse (bot check) IP address and device signals, processed by Cloudflare Legitimate interests (a secure service that scripts cannot misuse)
Fixing crashes and defects Crash and error data Legitimate interests (a working product)
Setting free-tier limits and deciding what the paid tier offers App usage events Legitimate interests (a fair free tier and a sustainable service) — switch them off any time in Settings → My Account
Seeing which of the App's tips help App usage events (tips) Legitimate interests (an App that is easy to learn) — switch them off any time in Settings → My Account
Keeping a copy of reported content and linked account details, and passing them to the authorities where the law requires it (Section 8.4) Reports, the reported content, account details Legal obligation, and legitimate interests (keeping users safe; establishing or defending legal claims)
Recording that you accepted our Terms and confirmed your age Date and Terms version Contract, and legitimate interests (being able to show it)
Complying with the law As required Legal obligation (Art. 6(1)(c))

Where we rely on legitimate interests we have balanced them against your rights, and you may object (Section 13). We make no automated decisions with legal or similarly significant effects, and we do not deliberately process special-category data (what you reveal in free-text content is your choice).


7. AI features — what leaves the App

Three features use external AI services, all narrowly:

These providers process images solely to provide the feature. We do not use your content to train AI models.

Scan a page (reading the text of a photographed book page into a note) is not one of them: the text is read on your phone, by Apple's Vision on iPhone and Google's ML Kit on Android (Section 8.1), and the photo is not sent to us or to anyone else.


8. Who we share data with

We do not sell personal data. We share it only as described here.

8.1 Service providers (processors)

Provider Role Location
Supabase Pte. Ltd Our backend: database, authentication, file storage, server functions. Project hosted in the United Kingdom (London) Singapore (company; its staff may access the project from abroad for support); your data is stored in the United Kingdom (London)
Apple Inc. App distribution, payments, sign-in, push delivery (APNs) USA
Google LLC App distribution, payments, sign-in, push delivery (FCM), Google Books API, Cloud Vision (checking new profile pictures, Section 7); on Android, the barcode scanner and Scan a page (reading a book page's text into a note) use Google's on-device ML Kit, which sends Google device and performance diagnostics (device model, system and app version, how the scanner performed) — not the images it scans USA
RevenueCat, Inc. Subscription management (when you delete your account we ask RevenueCat to delete its record of you) USA
Resend, Inc. Delivery of sign-in codes and email-change confirmation codes: receives your email address and the message containing the code USA (EU sending region)
Cloudflare, Inc. Bot check on the sign-in screen (Turnstile — Sections 4.3 and 11; for the bot check, Cloudflare also acts as an independent controller to improve that service); our domain and website; the background remover, which removes the background from an image you submit to it (Section 7) USA (global network)
Proton AG Our email: the mailboxes behind our support and privacy addresses, which receive your messages and send our replies Switzerland
Functional Software, Inc. (Sentry) Crash and error reporting — EU data residency, pseudonymous ids only USA, EU ingest
Expo (650 Industries, Inc.) Push notification delivery (receives the device push token and the notification text, which can include another user's display name); delivery of App updates — the App checks Expo's servers for a newer version of its code USA
Anthropic, PBC AI analysis of public book cover images (Section 7) USA
Data Protection Representative Limited (DataRep) Our representative in the EU/EEA (Section 1): receives the privacy, Digital Services Act and terrorist content requests people send to it and passes them to us Ireland (EU)

Each service provider in this table uses your data only to provide its service to us (apart from the independent uses this table names), under terms that require it to give your data the same or equal protection as this Policy describes and as data-protection law requires.

8.2 Other users — what they can and cannot see

New accounts are public — a book-sharing community is what the App is for — and you can make yours private at any time with the public / private switch in Edit Profile (see below). Your profile can be viewed by other signed-in users. It shows: your display name, handle and avatar; your bio, favourite genre and follower/following counts; your Instagram/TikTok handles if you added them; and the books you chose to feature (currently reading, all-time favourite).

When you publish a shelf, other users can also see: the shelf's name, caption, image, books and decor. Comments you write are visible to anyone who can see that shelf. Your public profile lists your published shelves, including via your profile link.

If you turn on "Share my ratings & reviews" (Edit Profile), other users can also see your star ratings, short reviews and extended reviews of every book in your library that you have rated, with the book's title, author and cover and the formats you read it in — on your profile, and on the book when they open it from one of your shelves. A public account shares them with anyone signed in; a private account only with the followers you have approved. Turn it off and they are hidden again at once.

Your profile link (therealmshelf.app/your-handle) also works for people who are not signed in. Without signing in, a visitor can see: for a public account, your display name, handle, avatar, bio and how many published shelves and followers you have; for a private account, only your display name and avatar.

If you set your account to private, people have to ask before they can follow you. Anyone signed in can find your account in Browse search by your display name or @handle — it is shown with your display name and avatar only, marked private — and send a follow request; you see who is asking and accept or decline it, and declining tells the other person nothing. Until you accept, they see only your display name and avatar — not your bio, counts, featured books, shelves or reviews. Your shelves, featured books and shared reviews are shown only to followers you have approved. You can remove a follower at any time (they are not told), and blocking someone also removes them. Followers you already had when you switched to private stay; if you switch back to public, requests still waiting are accepted, because what they asked to see is public by then.

Other users can never see: your reading notes, personal cover images (unless one is approved for the book catalogue — then it is shown without your name, Section 8.3), cover designs, your library lists (apart from the books you choose to feature on your profile), ratings or reviews you have not shared, your email address, or your unpublished shelves.

8.3 Spine and cover submissions

When you add your own photo of a book's spine or cover, the App uploads a copy to our servers and places it in a review queue — this happens automatically when you add the photo. Our staff look at it. If they approve it, it becomes part of the shared book catalogue — the book's own spine or cover, or an edition of the book that other users can choose — and can render on any user's shelf containing that book. Your name is not displayed with it.

Until then it is used only on your own shelves, on your own device; other users don't see it, including in the picture of a shelf you publish. We tell you in the App when a photo is approved, and when it isn't and why. A photo that isn't approved is deleted from our servers; it stays on your own device.

The same goes for a book you add by hand: its details and its cover and spine photos are uploaded and queued for review. Until it is approved, nobody else sees it — it is left out of every shelf other users see. If our staff approve it, its details and photos become a new entry in the shared book catalogue that any user can find, without your name. If they don't, its photos are deleted from our servers and the book stays in your own library. Your waiting submissions are deleted with your account.

Choosing "Revert to original spine" or "Revert to original cover" removes the photo from your device and your shelves, and deletes the uploaded copy from our servers as long as our staff have not approved it yet. A photo that has already been approved stays in use for other users; email privacy@therealmshelf.app if you want it removed. When you delete your account, your submissions are deleted — except approved photos, which stay in the book catalogue with nothing that links them to you.

We may disclose personal data where necessary in good faith to comply with law or a binding order; to protect the rights, property or safety of our users, ourselves or the public; to investigate fraud or abuse; or to enforce our Terms. In particular, UK law requires us to report child sexual abuse material to the UK National Crime Agency (with the content and the details of the account that posted it, such as username, email address and the time it was uploaded), and we pass a threat to someone's life or safety to the police. When something is reported to us for one of these reasons, we keep a copy of the reported content and the account details connected with it even if the account is deleted, for as long as Section 10 says. If we are involved in a merger, acquisition or asset sale, personal data may transfer to the successor, who must honour this Policy; we will notify you of any such change.

8.5 Book data sources your device contacts directly

To find books and show their covers, the App on your device talks directly to three independent services:

As with any internet request, these services can see your IP address. They do not receive your account details. They are not our service providers: they act independently, under their own privacy policies.


9. International transfers

Some providers process data in the United States (and Supabase, a Singapore company, may access our database from abroad for support), and Cloudflare operates a global network, so its bot check and the background remover may be handled in a data centre near you. Where personal data leaves the UK or EEA we rely on: adequacy decisions (including the EU–US Data Privacy Framework and UK–US Data Bridge where the provider is certified); the European Commission's Standard Contractual Clauses and/or the UK International Data Transfer Addendum; and additional safeguards where appropriate. You can request a copy of the relevant safeguards via the privacy email above.


10. How long we keep data

Data Retention
Account, library, shelves, reviews, social data While your account exists
Push tokens Removed on sign-out and on account deletion
Follow requests to or from a private account Until the request is accepted, declined or cancelled, or either account is deleted or blocks the other
Notifications in your activity list Deleted automatically after 180 days (90 days once read)
Push delivery log (who was notified about which kind of event — used only to stop notification spam) Deleted automatically after 7 days
Which catalogue books your account opened or added (book ranking signals) Deleted automatically after 90 days
Books you remove from your library Marked as removed so your other devices learn of it, then deleted for good after 180 days
Books and decor you remove from a shelf Marked as removed so your other devices learn of it, and kept in that state until you delete your account
Spine and cover submissions (and their review decisions), and background-remover cut-outs Until you delete your account. A photo we approved for the book catalogue stays in it after that, with nothing that links it to you
Fair-use counters Deleted automatically after 90 days; the monthly background-removal count is kept while your account exists
Crash and error data (Sentry) Deleted automatically per Sentry retention (typically 90 days)
App usage events Deleted automatically after 24 months, and at once when you delete your account
Purchase records Per the stores' and RevenueCat's retention; our accounting records up to 6 years (UK law)
Your notes, cover designs and personal covers (on your device and in their private backup) Until you delete them or your account. A deleted one leaves the backup at the next sync; the record that it was deleted is kept up to 180 days, and photos nothing uses any more are removed within about a week (Section 4.2)
Sign-in records (the time, email address and IP address of each sign-in, kept by our hosting provider's authentication log) Deleted automatically after 7 days
Backups Kept for up to 7 days, then overwritten; if we ever restore one, we delete again anything you asked us to delete
Reports (including the copy of the reported text — for example a comment, or a profile's name, handle and bio — made when the report is filed) Until 12 months after the report is closed, then the copy and the link to the accounts involved are deleted — even if either account was deleted earlier
Content and account details preserved because of a report of illegal content or a threat to safety (Section 8.4), or a profile picture our automatic check was holding for review when the account was deleted or reset 1 year from the report (or the deletion), as UK law requires for child sexual abuse material, then deleted — even if the account was deleted earlier
Our staff activity log (Section 11), including the account an action concerned 2 years, then deleted
Records of privacy requests we handled (what was asked and done, with the account id and a masked email address) 2 years, so we can show we did what you asked
Push delivery receipts (whether a notification reached your device) Deleted automatically after 7 days
A note that one of your shelves was announced to your followers (so it is announced only once) As long as the shelf exists; deleted with the shelf or your account
Your agreement to our Terms (date and version) While your account exists
A new profile picture waiting for our staff after the automatic check flagged it (and the check's rating) Until our staff approve it (it then replaces your picture) or reject it (it is deleted)
How many profile pictures you submitted each day (a limit of 20 a day) Deleted automatically after 7 days

Account deletion is built into the App (Settings → My Account → Delete Account & All Data). It deletes your server-side data — profile, library, shelves, reviews, comments, follows and uploaded images including spine and cover submissions (except photos we approved for the book catalogue, which stay there with nothing that links them to you) and background-remover cut-outs. What stays for a while is listed in the table above: reports (and preserved content, where the law requires it), our staff log and privacy-request records, accounting records, and backups kept for up to 7 days. This includes the private backup of your notes, cover designs and personal covers (Section 4.2). It also clears the App's data on the device you delete from.


11. How we protect your data

Access by our staff. A small number of authorised staff can access user data where their job requires it: to review reports (including who made a report), to review spine and cover submissions, to find an account by its email address or handle when handling a support or safety matter, to unpublish a shelf that breaks our rules, and to prepare a copy of your data when you ask for one (Section 13) — that copy includes the private backup of your notes, cover designs and own covers (Section 4.2). Changes staff make through our admin tools are recorded in an internal log — including which account a change concerned, such as a spine photo's reviewer decision — kept for 2 years (Section 10), even after either account is closed.

No system is perfectly secure. If a personal data breach is likely to put your rights and freedoms at risk, we will notify the UK Information Commissioner's Office within 72 hours and affected users without undue delay, as the law requires.


12. Push notifications and your choices

Notifications (new followers and follow requests, a shelf published by someone you follow, likes, saves, comments, release reminders) are optional. You can switch each category on or off in the App's Settings — or all of them at once with "All notifications" — or disable notifications entirely in your device settings. Release-day reminders are scheduled locally on your device. Notifications about new features and news are sent only if you switch them on; they are off until you do, and we record when you switch them on or off.


13. Your rights (UK & EEA)

You have the right to: access the personal data we hold about you; have it rectified or erased; restrict or object to processing (including any based on legitimate interests); data portability; and to withdraw consent at any time without affecting prior processing. We respond within one calendar month, free of charge (unless a request is manifestly unfounded or excessive).

To exercise them: use the in-App tools (edit profile, delete account) or email privacy@therealmshelf.app. In the EU/EEA you can also go through our representative, DataRep (Section 1).

Complaints. If you are unhappy with how we handle your personal data, you can complain to us first at privacy@therealmshelf.app. We acknowledge a complaint within 30 days, look into it, and tell you what we found and what we are doing about it without undue delay.

You may also complain to the Information Commissioner's Office (ico.org.uk · 0303 123 1113 · Wycliffe House, Water Lane, Wilmslow, SK9 5AF) or, in the EEA, to your local supervisory authority — whether or not you have complained to us first.


14. Additional information for US residents

State privacy laws (including the CCPA/CPRA) give residents of certain states specific rights. In the 12 months before the date above we collected these categories of personal information: identifiers (email, name, handle, Apple or Google account identifiers if you sign in that way, device push tokens); user content you provide (library, shelves, reviews, comments, reading notes, cover designs and photos you upload, feedback you send); commercial information (subscription status); internet or network activity limited to crash/error data, in-app usage events (opening the App, reaching a free-tier limit, seeing the upgrade screen, subscribing, seeing, closing and following the App's tips) and which catalogue books you opened or added (kept 90 days, to count each reader once in the book ranking); and inferences limited to aggregate book-ranking signals.


15. Children

The Service is for adults only (18+): it is rated 18+ on the App Store, its audience on Google Play is set to 18 and over, and it is not directed at children or teenagers. We do not knowingly collect personal data from anyone under 18 (and never from children under 13, per COPPA). When you sign in, the App asks you to confirm that you are at least 18; we record the date you confirmed it (Section 10), and we do not ask for your date of birth. If you believe someone under 18 has created an account, contact us and we will delete it.


16. Cookies and local storage

The App is a native mobile application and sets no browser cookies of its own. The bot check on the sign-in screen (Section 11) runs in a small embedded browser view, in which Cloudflare may store technical data strictly needed for that security check. The App uses local device storage to keep you signed in, remember preferences and cache content for speed. Our website at therealmshelf.app (these documents, the support pages and the pages behind profile links) sets no cookies and uses no analytics or advertising tools. It is hosted by Cloudflare, which — like any web host — processes your IP address and basic request data to deliver the pages and keep them secure. When you open a profile link in a browser, the page asks our backend (Supabase) for the public details of that profile described in Section 8.2; nothing about you is stored.


"Get This Book" links open third-party retailers (Amazon, Kindle, Audible, Bookshop.org); they open the retailer's site for the country your phone is set to where one exists (we read only the country setting, on your phone; it is not sent to us). Some of these links may be affiliate links — we may earn a commission on qualifying purchases at no extra cost to you; the App says so under the links whenever it applies. Once you leave the App the retailer's own privacy policy applies; we do not receive personal data about what you buy there.


18. Changes to this Policy

We may update this Policy as the Service or the law changes. For material changes we will notify you in the App or by email at least 14 days before they take effect. The "Last Updated" date shows the current version.


19. Contact

Allyoucanreserve Ltd, 124 City Road, London, England, EC1V 2NX, United Kingdom
Email: privacy@therealmshelf.app

In the EU/EEA: our representative DataRep — datarequest@datarep.com (with "The Realm" in the subject line), www.datarep.com/data-request, or by post to DataRep at the address for your country in Section 20.

If you need this Policy in another format (for example screen-reader friendly), contact us and we will provide one.


20. DataRep's addresses in the EU/EEA

For people in the EU/EEA writing to our representative (Section 1). Always address the letter to "DataRep" — not to The Realm, or it may not reach them — and say clearly in it that it is about The Realm.

Country Postal address
Austria DataRep, City Tower, Brückenkopfgasse 1/6. Stock, Graz, 8020, Austria
Belgium DataRep, Rue des Colonies 11, Brussels, 1000, Belgium
Bulgaria DataRep, 25 Vitosha blvd. Fl. 2, office 4, 1000, Sofia, Bulgaria
Croatia DataRep, Ground & 9th Floor, Hoto Tower, Savska cesta 32, Zagreb, 10000, Croatia
Cyprus DataRep, Victory House, 205 Archbishop Makarios Avenue, Limassol, 3030, Cyprus
Czech Republic DataRep, Platan Office, 28. Října 205/45, Floor 3&4, Ostrava, 70200, Czech Republic
Denmark DataRep, Lautruphøj 1-3, Ballerup, 2750, Denmark
Estonia DataRep, 2nd Floor, Tornimae 5, Tallinn, 10145, Estonia
Finland DataRep, Luna House, 5.krs, Mannerheimintie 12 B, Helsinki, 00100, Finland
France DataRep, 72 rue de Lessard, Rouen, 76100, France
Germany DataRep, 3rd and 4th floor, Altmarkt 10 B/D, Dresden, 01067, Germany
Greece DataRep, Ippodamias Sq. 8, 4th floor, Piraeus, Attica, Greece
Hungary DataRep, 1054 Honved street, 8 1/2, Budapest, Hungary
Iceland DataRep, Laugavegur 13, 101 Reykjavik, Iceland
Ireland DataRep, 77 Camden Street Lower, Dublin, D02 XE80, Ireland
Italy DataRep, Viale Giorgio Ribotta 11, Piano 1, Rome, Lazio, 00144, Italy
Latvia DataRep, 4th & 5th floors, 14 Terbatas Street, Riga, LV-1011, Latvia
Liechtenstein DataRep, City Tower, Brückenkopfgasse 1/6. Stock, Graz, 8020, Austria
Lithuania DataRep, 44A Gedimino Avenue, 01110 Vilnius, Lithuania
Luxembourg DataRep, BPM 335368, Banzelt 4 A, 6921, Roodt-sur-Syre, Luxembourg
Malta DataRep, Tower Business Centre, 2nd floor, Tower Street, Swatar, BKR4013, Malta
Netherlands DataRep, De Nieuwe Erven 3 Unit – 15162, 5431 NV Cuijk, Netherlands
Norway DataRep, C.J. Hambros Plass 2c, Oslo, 0164, Norway
Poland DataRep, Budynek Fronton ul Kamienna 21, Krakow, 31-403, Poland
Portugal DataRep, Torre de Monsanto, Rua Afonso Praça 30, 7th floor, Algès, Lisbon, 1495-061, Portugal
Romania DataRep, 15 Piaţa Charles de Gaulle, nr. 1-T, Bucureşti, Sectorul 1, 011857, Romania
Slovakia DataRep, Apollo Business Centre II, Block E / 9th floor, 4D Prievozska, Bratislava, 821 09, Slovakia
Slovenia DataRep, Trg. Republike 3, Floor 3, Ljubljana, 1000, Slovenia
Spain DataRep, Calle de Manzanares 4, Madrid, 28005, Spain
Sweden DataRep, S:t Johannesgatan 2, 4th floor, Malmo, SE - 211 46, Sweden

© Allyoucanreserve Ltd. All rights reserved.