[{"data":1,"prerenderedAt":10},["ShallowReactive",2],{"legal-privacy-en":3},{"data":4},{"slug":5,"locale":6,"version":7,"effective_date":8,"html":9},"privacy","en",2,"2026-07-19","\u003Ch1>fitliftly — Privacy Policy\u003C/h1>\n    \u003Cp class=\"meta\">\u003Cstrong>Effective from:\u003C/strong> 19 July 2026\u003C/p>\n\n    \u003Ch2>1. Data Controller\u003C/h2>\n    \u003Cp>The controller of personal data is:\u003C/p>\n    \u003Cp>\n        \u003Cstrong>Stelix holding s.r.o.\u003C/strong>\u003Cbr>\n        Company ID (IČO): 01443909, VAT ID (DIČ): CZ01443909\u003Cbr>\n        Registered seat: Ke stadionu 1953, 272 01 Kladno, Czech Republic\u003Cbr>\n        E-mail: \u003Ca href=\"mailto:info@stelixholding.cz\">info@stelixholding.cz\u003C/a>\n    \u003C/p>\n    \u003Cp>(hereinafter the \u003Cstrong>\"Controller\"\u003C/strong> or \u003Cstrong>\"we\"\u003C/strong>)\u003C/p>\n    \u003Cp>In accordance with Art. 37 GDPR, the Controller has not appointed a Data Protection Officer (DPO), as it is not a public authority and its core activity does not consist of large-scale systematic monitoring of data subjects nor large-scale processing of special categories of data. The above contact e-mail will, however, fully address any data protection enquiries.\u003C/p>\n\n    \u003Ch2>2. Who This Policy Applies To\u003C/h2>\n    \u003Cp>This Policy applies to:\u003C/p>\n    \u003Cul>\n        \u003Cli>registered \u003Cstrong>Users\u003C/strong> of the fitliftly application (all roles: user, trainer, venue, partner);\u003C/li>\n        \u003Cli>\u003Cstrong>Visitors\u003C/strong> of the website fitliftly.com without registration;\u003C/li>\n        \u003Cli>persons who \u003Cstrong>contact the Controller\u003C/strong> via e-mail or through the in-app feedback widget.\u003C/li>\n    \u003C/ul>\n\n    \u003Ch2>3. Categories of Personal Data Processed\u003C/h2>\n\n    \u003Ch3>3.1 Identification and contact data\u003C/h3>\n    \u003Cul>\n        \u003Cli>first name and surname\u003C/li>\n        \u003Cli>username\u003C/li>\n        \u003Cli>e-mail address\u003C/li>\n        \u003Cli>phone number (optional)\u003C/li>\n        \u003Cli>address (street, city, postal code — optional, used i.a. for invoicing)\u003C/li>\n        \u003Cli>date of birth (optional)\u003C/li>\n        \u003Cli>gender (optional)\u003C/li>\n    \u003C/ul>\n\n    \u003Ch3>3.2 Profile data\u003C/h3>\n    \u003Cul>\n        \u003Cli>profile picture (avatar)\u003C/li>\n        \u003Cli>biography and other optional profile details\u003C/li>\n        \u003Cli>privacy settings (\u003Ccode>public\u003C/code>, \u003Ccode>friends\u003C/code>, \u003Ccode>private\u003C/code>)\u003C/li>\n        \u003Cli>language and timezone\u003C/li>\n    \u003C/ul>\n\n    \u003Ch3>3.3 Social account data\u003C/h3>\n    \u003Cp>If you sign in via Google, Apple or Facebook, we obtain from the identity provider:\u003C/p>\n    \u003Cul>\n        \u003Cli>the user identifier with that provider\u003C/li>\n        \u003Cli>the e-mail address\u003C/li>\n        \u003Cli>the name (and possibly avatar)\u003C/li>\n    \u003C/ul>\n\n    \u003Ch3>3.4 Service usage data (operational)\u003C/h3>\n    \u003Cul>\n        \u003Cli>records of workouts created, completed and cancelled\u003C/li>\n        \u003Cli>venue entry records (QR check-in/check-out)\u003C/li>\n        \u003Cli>statistics (volume, streaks, XP, level)\u003C/li>\n        \u003Cli>badges, challenges, leaderboards\u003C/li>\n        \u003Cli>friend list, follow relationships, followed venues\u003C/li>\n        \u003Cli>chat messages, polymorphic comments, reactions\u003C/li>\n        \u003Cli>uploaded photos of workouts and venues\u003C/li>\n        \u003Cli>sport pass records (card type, number, validity)\u003C/li>\n    \u003C/ul>\n\n    \u003Ch3>3.5 Payment and invoicing data\u003C/h3>\n    \u003Cul>\n        \u003Cli>records of credit wallet transactions\u003C/li>\n        \u003Cli>invoices (number, IČO/DIČ, billing address) — for trainer/venue/partner roles\u003C/li>\n        \u003Cli>payment card details are not stored in the App — card payments are processed via the \u003Cstrong>Stripe\u003C/strong> gateway, which is an independent data controller; the App records only the amount, variable symbol and top-up status\u003C/li>\n    \u003C/ul>\n\n    \u003Ch3>3.6 Technical data\u003C/h3>\n    \u003Cul>\n        \u003Cli>IP address\u003C/li>\n        \u003Cli>device type, operating system, browser version\u003C/li>\n        \u003Cli>last-seen timestamp\u003C/li>\n        \u003Cli>cookies and similar technologies (see Art. 8)\u003C/li>\n        \u003Cli>push notification token\u003C/li>\n    \u003C/ul>\n\n    \u003Ch3>3.7 Health data — special category of personal data (Art. 9 GDPR)\u003C/h3>\n    \u003Cp>\u003Cstrong>If you grant explicit consent to the Health Sync feature\u003C/strong>, the App synchronises data from \u003Cstrong>Apple HealthKit\u003C/strong> (iOS) or \u003Cstrong>Google Health Connect\u003C/strong> (Android), in particular:\u003C/p>\n    \u003Cul>\n        \u003Cli>activity (steps, energy expenditure, distance)\u003C/li>\n        \u003Cli>heart rate\u003C/li>\n        \u003Cli>sleep data\u003C/li>\n        \u003Cli>body metrics (weight, height — if shared)\u003C/li>\n    \u003C/ul>\n    \u003Cp>This data falls under \u003Cstrong>special categories of personal data\u003C/strong> per Art. 9 GDPR and we process it \u003Cstrong>solely on the basis of your explicit consent\u003C/strong>. You may withdraw consent at any time in the App settings or at the device system level; after withdrawal we no longer synchronise the data and existing records can be deleted on request.\u003C/p>\n\n    \u003Ch3>3.8 Feedback data\u003C/h3>\n    \u003Cp>When you use the feedback widget, we store the message text, a screenshot of the current screen, the page URL and the browser type. This data is transferred via webhook to our internal issue tracking system (GitLab).\u003C/p>\n\n    \u003Ch3>3.9 Publicly available data about venues\u003C/h3>\n    \u003Cp>Our directory also lists venues that do not yet have a manager on fitliftly. Their details (name, address, location, and where available contact and opening hours) come from public sources, in particular OpenStreetMap (© OpenStreetMap contributors, ODbL licence). We process them on the basis of our \u003Cstrong>legitimate interest\u003C/strong> (Art. 6(1)(f) GDPR) — maintaining a directory of venues. If you are a venue operator, you may request to take over management, to correct, or to \u003Cstrong>remove\u003C/strong> the data directly at the given venue in the app or at \u003Ca href=\"mailto:info@stelixholding.cz\">info@stelixholding.cz\u003C/a>, and you may \u003Cstrong>object\u003C/strong> to the processing at any time.\u003C/p>\n\n    \u003Ch2>4. Processing Purposes, Legal Bases and Retention\u003C/h2>\n    \u003Ctable>\n        \u003Cthead>\n            \u003Ctr>\n                \u003Cth>Purpose\u003C/th>\n                \u003Cth>Legal basis (GDPR Art. 6/9)\u003C/th>\n                \u003Cth>Data categories\u003C/th>\n                \u003Cth>Retention\u003C/th>\n            \u003C/tr>\n        \u003C/thead>\n        \u003Ctbody>\n            \u003Ctr>\n                \u003Ctd>Creation and management of the User Account, authentication\u003C/td>\n                \u003Ctd>performance of contract (Art. 6(1)(b)); after account deletion legitimate interest (Art. 6(1)(f)) — defence of legal claims\u003C/td>\n                \u003Ctd>3.1, 3.2, 3.3\u003C/td>\n                \u003Ctd>duration of the account + \u003Cstrong>3 years\u003C/strong> after deletion (limitation period for claims)\u003C/td>\n            \u003C/tr>\n            \u003Ctr>\n                \u003Ctd>Provision of the Service (social network, booking, check-in, statistics)\u003C/td>\n                \u003Ctd>performance of contract\u003C/td>\n                \u003Ctd>3.4\u003C/td>\n                \u003Ctd>duration of the account\u003C/td>\n            \u003C/tr>\n            \u003Ctr>\n                \u003Ctd>Chat messages (conversations and message content)\u003C/td>\n                \u003Ctd>performance of contract (Art. 6(1)(b))\u003C/td>\n                \u003Ctd>3.4\u003C/td>\n                \u003Ctd>duration of the account; deleted messages and messages of a deleted account are permanently removed \u003Cstrong>within 30 days\u003C/strong>\u003C/td>\n            \u003C/tr>\n            \u003Ctr>\n                \u003Ctd>Payment processing and tax document issuance\u003C/td>\n                \u003Ctd>legal obligation (Art. 6(1)(c)) — Accounting Act, VAT Act\u003C/td>\n                \u003Ctd>3.5\u003C/td>\n                \u003Ctd>\u003Cstrong>10 years\u003C/strong> from the end of the accounting period\u003C/td>\n            \u003C/tr>\n            \u003Ctr>\n                \u003Ctd>Service security, fraud prevention, debugging\u003C/td>\n                \u003Ctd>legitimate interest (Art. 6(1)(f))\u003C/td>\n                \u003Ctd>3.4, 3.6, 3.8\u003C/td>\n                \u003Ctd>logs 6 months, security incidents 3 years\u003C/td>\n            \u003C/tr>\n            \u003Ctr>\n                \u003Ctd>Marketing communication (newsletter, news)\u003C/td>\n                \u003Ctd>consent (Art. 6(1)(a))\u003C/td>\n                \u003Ctd>3.1\u003C/td>\n                \u003Ctd>until consent withdrawn or \u003Cstrong>3 years\u003C/strong> from last interaction\u003C/td>\n            \u003C/tr>\n            \u003Ctr>\n                \u003Ctd>Health Sync — synchronisation of health data\u003C/td>\n                \u003Ctd>\u003Cstrong>explicit consent\u003C/strong> (Art. 9(2)(a))\u003C/td>\n                \u003Ctd>3.7\u003C/td>\n                \u003Ctd>until consent withdrawn or account deleted\u003C/td>\n            \u003C/tr>\n            \u003Ctr>\n                \u003Ctd>Feedback / error reporting\u003C/td>\n                \u003Ctd>legitimate interest\u003C/td>\n                \u003Ctd>3.8\u003C/td>\n                \u003Ctd>until resolution + 6 months\u003C/td>\n            \u003C/tr>\n            \u003Ctr>\n                \u003Ctd>Push notifications (bookings, social activity)\u003C/td>\n                \u003Ctd>performance of contract\u003C/td>\n                \u003Ctd>device token\u003C/td>\n                \u003Ctd>while the device is active\u003C/td>\n            \u003C/tr>\n        \u003C/tbody>\n    \u003C/table>\n\n    \u003Ch2>5. Recipients of Personal Data (Processors)\u003C/h2>\n    \u003Cp>We share your data only to the necessary extent with the categories of recipients listed below. We have \u003Cstrong>data processing agreements\u003C/strong> (DPAs) in place with all of them in accordance with Art. 28 GDPR.\u003C/p>\n    \u003Ctable>\n        \u003Cthead>\n            \u003Ctr>\n                \u003Cth>Processor\u003C/th>\n                \u003Cth>Purpose\u003C/th>\n                \u003Cth>Location\u003C/th>\n                \u003Cth>Transfer outside EU\u003C/th>\n            \u003C/tr>\n        \u003C/thead>\n        \u003Ctbody>\n            \u003Ctr>\u003Ctd>\u003Cstrong>Hetzner Online GmbH\u003C/strong>\u003C/td>\u003Ctd>Hosting (servers, database, backups)\u003C/td>\u003Ctd>Germany\u003C/td>\u003Ctd>no\u003C/td>\u003C/tr>\n            \u003Ctr>\u003Ctd>\u003Cstrong>Stripe Payments Europe, Ltd.\u003C/strong>\u003C/td>\u003Ctd>Payment gateway (card payments, payee onboarding)\u003C/td>\u003Ctd>Ireland / EU; partial processing in the USA under Standard Contractual Clauses and the EU-U.S. Data Privacy Framework\u003C/td>\u003Ctd>limited (see left column)\u003C/td>\u003C/tr>\n            \u003Ctr>\u003Ctd>\u003Cstrong>Cloudflare, Inc.\u003C/strong>\u003C/td>\u003Ctd>CDN, DDoS protection, Turnstile\u003C/td>\u003Ctd>USA / global\u003C/td>\u003Ctd>yes — DPF / SCC\u003C/td>\u003C/tr>\n            \u003Ctr>\u003Ctd>\u003Cstrong>Google LLC\u003C/strong>\u003C/td>\u003Ctd>Google Sign-In, Health Connect (Android)\u003C/td>\u003Ctd>USA\u003C/td>\u003Ctd>yes — DPF / SCC\u003C/td>\u003C/tr>\n            \u003Ctr>\u003Ctd>\u003Cstrong>Apple Inc.\u003C/strong>\u003C/td>\u003Ctd>Sign in with Apple, HealthKit (iOS)\u003C/td>\u003Ctd>USA\u003C/td>\u003Ctd>yes — DPF / SCC\u003C/td>\u003C/tr>\n            \u003Ctr>\u003Ctd>\u003Cstrong>Meta Platforms Ireland Ltd.\u003C/strong>\u003C/td>\u003Ctd>Facebook Login\u003C/td>\u003Ctd>Ireland / USA\u003C/td>\u003Ctd>yes — DPF / SCC\u003C/td>\u003C/tr>\n            \u003Ctr>\u003Ctd>\u003Cstrong>PostHog EU B.V.\u003C/strong>\u003C/td>\u003Ctd>Product analytics and session replay — pseudonymised, with input masking and sensitive content excluded\u003C/td>\u003Ctd>EU (Frankfurt data centre)\u003C/td>\u003Ctd>no\u003C/td>\u003C/tr>\n            \u003Ctr>\u003Ctd>\u003Cstrong>Functional Software, Inc. (Sentry)\u003C/strong>\u003C/td>\u003Ctd>Application error tracking\u003C/td>\u003Ctd>EU data residency (Germany); parent company USA\u003C/td>\u003Ctd>limited — DPF / SCC\u003C/td>\u003C/tr>\n            \u003Ctr>\u003Ctd>\u003Cstrong>DeepL SE\u003C/strong>\u003C/td>\u003Ctd>Machine translation of exercise descriptions (no User identifiers)\u003C/td>\u003Ctd>Germany\u003C/td>\u003Ctd>no\u003C/td>\u003C/tr>\n            \u003Ctr>\u003Ctd>\u003Cstrong>GitLab Inc.\u003C/strong>\u003C/td>\u003Ctd>Internal issue tracking system (feedback widget)\u003C/td>\u003Ctd>USA\u003C/td>\u003Ctd>yes — SCC\u003C/td>\u003C/tr>\n            \u003Ctr>\u003Ctd>\u003Cstrong>OpenStreetMap Foundation / Mapy.cz a.s.\u003C/strong>\u003C/td>\u003Ctd>Geocoding of venue addresses (not user addresses)\u003C/td>\u003Ctd>EU / UK\u003C/td>\u003Ctd>no personal data transfer (only POI addresses)\u003C/td>\u003C/tr>\n            \u003Ctr>\u003Ctd>\u003Cstrong>Accounting and tax advisor\u003C/strong>\u003C/td>\u003Ctd>Accounting\u003C/td>\u003Ctd>Czech Republic\u003C/td>\u003Ctd>no\u003C/td>\u003C/tr>\n        \u003C/tbody>\n    \u003C/table>\n    \u003Cp>We \u003Cstrong>do not sell\u003C/strong> your personal data to third parties for marketing purposes.\u003C/p>\n\n    \u003Ch2>6. Transfers to Third Countries\u003C/h2>\n    \u003Cp>Some of the services listed above (Google, Apple, Meta, Cloudflare, GitLab, Sentry) operate as part of global infrastructures. Sentry and PostHog data is stored in EU data centres; for Sentry, the US parent company may have limited access. When transferring personal data outside the European Economic Area we rely on:\u003C/p>\n    \u003Cul>\n        \u003Cli>\u003Cstrong>EU-US Data Privacy Framework\u003C/strong> (DPF) — for the United States with certified recipients;\u003C/li>\n        \u003Cli>\u003Cstrong>Standard Contractual Clauses\u003C/strong> (SCCs) adopted by the European Commission — for other cases;\u003C/li>\n        \u003Cli>supplementary organisational and technical measures (encryption, pseudonymisation) where relevant.\u003C/li>\n    \u003C/ul>\n\n    \u003Ch2>7. Your Rights as a Data Subject\u003C/h2>\n    \u003Cp>Under the GDPR you have the following rights:\u003C/p>\n    \u003Cul>\n        \u003Cli>\u003Cstrong>Right of access\u003C/strong> (Art. 15) — to obtain information about what data we process about you.\u003C/li>\n        \u003Cli>\u003Cstrong>Right to rectification\u003C/strong> (Art. 16) — to correct inaccurate or incomplete data.\u003C/li>\n        \u003Cli>\u003Cstrong>Right to erasure\u003C/strong> (\"right to be forgotten\", Art. 17) — to request deletion of data when no longer needed or upon withdrawal of consent. This also covers manual deletion of health data.\u003C/li>\n        \u003Cli>\u003Cstrong>Right to restriction of processing\u003C/strong> (Art. 18).\u003C/li>\n        \u003Cli>\u003Cstrong>Right to data portability\u003C/strong> (Art. 20) — to receive your data in a machine-readable format (JSON/CSV).\u003C/li>\n        \u003Cli>\u003Cstrong>Right to object\u003C/strong> (Art. 21) — to processing based on legitimate interest or for direct marketing purposes.\u003C/li>\n        \u003Cli>\u003Cstrong>Right to withdraw consent\u003C/strong> (Art. 7(3)) — at any time, with effect for the future (in particular for marketing and Health Sync).\u003C/li>\n        \u003Cli>\u003Cstrong>Right not to be subject to automated decision-making\u003C/strong> (Art. 22) — the App does not perform automated decision-making with legal effects.\u003C/li>\n    \u003C/ul>\n    \u003Ch3>How to exercise your rights\u003C/h3>\n    \u003Cp>Rights can be exercised:\u003C/p>\n    \u003Cul>\n        \u003Cli>in the App under \u003Cstrong>\"Privacy & Data\"\u003C/strong> (export, deletion, withdrawal of consents);\u003C/li>\n        \u003Cli>by e-mail to \u003Cstrong>info@stelixholding.cz\u003C/strong>.\u003C/li>\n    \u003C/ul>\n    \u003Cp>We handle requests \u003Cstrong>free of charge\u003C/strong> within \u003Cstrong>30 days\u003C/strong> of receipt (the period may be extended by an additional 2 months for complex cases, with notice to the data subject).\u003C/p>\n\n    \u003Ch2>8. Cookies and Similar Technologies\u003C/h2>\n\n    \u003Ch3>8.1 Strictly necessary (no consent required)\u003C/h3>\n    \u003Cul>\n        \u003Cli>session cookie (\u003Ccode>fitliftly_session\u003C/code>, \u003Ccode>XSRF-TOKEN\u003C/code>) — authentication and CSRF protection\u003C/li>\n        \u003Cli>language preference (\u003Ccode>locale\u003C/code>)\u003C/li>\n        \u003Cli>role preference (\u003Ccode>active_role_context\u003C/code>)\u003C/li>\n        \u003Cli>App localStorage (remembered UI settings, such as venue chat visibility)\u003C/li>\n    \u003C/ul>\n\n    \u003Ch3>8.2 Application usage analytics\u003C/h3>\n    \u003Cp>To understand how the App is used we rely on \u003Cstrong>PostHog\u003C/strong>, operated exclusively in the EU (Frankfurt data centre). It is configured to \u003Cstrong>store no cookies or other identifiers on your device\u003C/strong> — which is why no cookie-banner consent is required. The processing covers:\u003C/p>\n    \u003Cul>\n        \u003Cli>\u003Cstrong>usage measurement\u003C/strong> (page views, clicks, performance metrics);\u003C/li>\n        \u003Cli>\u003Cstrong>session replay\u003C/strong> — a visual recording of navigation through the App used to improve usability; all form inputs are masked and sensitive blocks (chat messages, health data, credit balances, benefit-card numbers) are excluded from the recording entirely;\u003C/li>\n        \u003Cli>for logged-in users, matching under a \u003Cstrong>pseudonymous numeric identifier\u003C/strong> (no name or e-mail).\u003C/li>\n    \u003C/ul>\n    \u003Cp>The legal basis is our legitimate interest in improving the Service (Art. 6(1)(f) GDPR). You may \u003Cstrong>object\u003C/strong> to this processing at any time using the contacts in Section 7.\u003C/p>\n\n    \u003Ch3>8.3 Marketing (with consent)\u003C/h3>\n    \u003Cp>Currently not used. If deployed in the future, we will request your consent via a cookie banner.\u003C/p>\n\n    \u003Cp>Cookie consent can be updated at any time in the settings.\u003C/p>\n\n    \u003Ch2>9. Security of Personal Data\u003C/h2>\n    \u003Cp>We implement in particular the following technical and organisational measures:\u003C/p>\n    \u003Cul>\n        \u003Cli>transport encryption (TLS 1.2+, HTTPS);\u003C/li>\n        \u003Cli>password hashing (bcrypt);\u003C/li>\n        \u003Cli>restricted access to the production database (administrators only);\u003C/li>\n        \u003Cli>regular backups (daily incremental, weekly full);\u003C/li>\n        \u003Cli>network segmentation (PostgreSQL and Redis are not exposed to the internet);\u003C/li>\n        \u003Cli>security headers (HSTS, X-Frame-Options, etc.);\u003C/li>\n        \u003Cli>protection against automated attacks (Cloudflare Turnstile, honeypot);\u003C/li>\n        \u003Cli>regular operating system and library updates;\u003C/li>\n        \u003Cli>access monitoring.\u003C/li>\n    \u003C/ul>\n    \u003Cp>In the event of a security breach with risk to the rights of data subjects, we will notify you in accordance with Art. 33 and 34 GDPR.\u003C/p>\n\n    \u003Ch2>10. Children\u003C/h2>\n    \u003Cp>The App \u003Cstrong>is not intended for children under 15\u003C/strong> and independent registration in this age group is prohibited. Where the App is used by a person aged 15–18, we recommend obtaining consent from a legal guardian. If we discover that we have collected data from a child without the necessary consent, we will delete the data immediately.\u003C/p>\n\n    \u003Ch2>11. Changes to the Privacy Policy\u003C/h2>\n    \u003Cp>This Policy may be updated from time to time. We will inform Users of \u003Cstrong>material\u003C/strong> changes via e-mail and/or via in-App notification at least \u003Cstrong>30 days\u003C/strong> before the change takes effect. The current version is always available at \u003Ca href=\"/privacy\">fitliftly.com/privacy\u003C/a>.\u003C/p>\n\n    \u003Ch2>12. Complaint to the Supervisory Authority\u003C/h2>\n    \u003Cp>If you believe that your personal data is being processed in breach of the GDPR, you have the right to lodge a complaint with the supervisory authority:\u003C/p>\n    \u003Cp>\n        \u003Cstrong>Office for Personal Data Protection (ÚOOÚ)\u003C/strong>\u003Cbr>\n        Pplk. Sochora 27\u003Cbr>\n        170 00 Prague 7, Czech Republic\u003Cbr>\n        \u003Ca href=\"https://www.uoou.gov.cz/\" target=\"_blank\" rel=\"noopener\">uoou.gov.cz\u003C/a>\n    \u003C/p>\n\n    \u003Ch2>13. Contact\u003C/h2>\n    \u003Cp>For any questions regarding the protection of personal data, please contact us:\u003C/p>\n    \u003Caddress>\n        Stelix holding s.r.o.\u003Cbr>\n        Ke stadionu 1953, 272 01 Kladno, Czech Republic\u003Cbr>\n        Company ID (IČO): 01443909\u003Cbr>\n        E-mail: \u003Ca href=\"mailto:info@stelixholding.cz\">info@stelixholding.cz\u003C/a>\n    \u003C/address>",1784835008247]