ARAKI MAGAZINE

PRIVACY POLICY

Effective date: 28 October 2026

1. Who we are

This policy explains how Araki Magazine processes personal information when you visit arakimagazine.com, use its related services, or contact us. It covers the English and Georgian editions and requests handled through our API at api.arakimagazine.com. Our alternative domain redirects visitors to the main website.

Website operator / data controller
Nino Imerlishvili
Place of business
Tbilisi, Georgia
Country
Georgia
Privacy contact
[email protected]

You can read the magazine without creating an account.

2. Information we process

  • Technical and security information: IP address, requested pages and API URLs, request time, browser and device information, response status, errors, and security events. Search terms can be included in request URLs and technical logs. Please avoid entering confidential personal information into the search box.
  • Language preferences: your browser’s language settings and, where set, your selected English or Georgian edition.
  • Correspondence: your email address, name if supplied, message, attachments, and information you choose to send when contacting us.
  • Account information, if you use account functions: email address, first and last name, password hash, optional profile image, access role, account status, and sign-in/session information, including IP address and browser/device information. This includes editorial and administrator accounts.
  • Editorial material: names, biographies, photographs, credits, quotations, and other information included in material submitted to or published by the magazine. Published editorial material is publicly accessible.

Account and contact details come from you or an authorised person administering your account. Technical information is generated when your browser requests our services. Editorial information may also come from contributors, interviewees, and public sources.

3. Why we use information

We use information to deliver pages and search results, remember the selected language, secure the website, investigate errors or abuse, administer accounts, respond to messages, and manage editorial contributions. We also measure overall website traffic and performance.

Where applicable, the legal basis is our legitimate interest in running a secure, reliable magazine, handling enquiries, and understanding site performance; contractual necessity for relevant account or contributor arrangements; or a legal obligation. If an activity requires consent, we obtain it separately. Visiting the website alone is not treated as consent to unrelated processing.

4. Cookies

Cookies are small files stored by your browser. Our application uses the following cookies when the relevant function is used:

CookiePurposeLifetime
NEXT_LOCALERemembers the selected language when needed.Browser session.
access_tokenAuthenticates a signed-in account.15 minutes per issuance.
refresh_tokenMaintains and renews an authenticated session.Up to 7 days per issuance; may be renewed during use.
auth_sessionIndicates that an account session exists.Up to 7 days per issuance; may be renewed during use.

The three account cookies are associated with sign-in, rather than being required just to read articles. Signing out clears them. Cloudflare may also set security or challenge cookies when its relevant protections are triggered or enabled; their names and lifetimes depend on those protections. See Cloudflare’s cookie information.

You can delete or block cookies through your browser settings. Blocking sign-in cookies can prevent account access, and blocking security cookies may prevent a security check from working. Your language choice may need to be selected again.

5. Website analytics

The live website loads Cloudflare’s Web Analytics/performance beacon. It measures visits and page performance. Reports can include page paths, referring sites, browser and device categories, country, and loading-performance measurements. Cloudflare explains these report dimensions here.

According to Cloudflare, its Web Analytics service does not use cookies, local storage, or visitor fingerprinting to produce analytics. This is separate from the technical and security processing needed to deliver the website. See Cloudflare Web Analytics and Cloudflare’s privacy policy.

6. Advertising and external websites

The magazine displays advertisements and sponsored articles. Current advertising is placed by the editorial team, rather than selected using a reader advertising profile. Our built-in banner format does not run advertiser JavaScript.

Clicking an advertisement, Instagram link, or social-sharing link takes you to an external service with its own privacy practices. A sharing link can pass the selected article’s public URL and title to that service. An email link opens your email application. Our website does not provide advertisers with your account details or private email correspondence through these links.

7. Who can receive information

Access is limited to the people and providers who need information for the relevant task: authorised editorial or technical personnel, hosting and infrastructure providers, Cloudflare for network delivery, protection and analytics, and our email provider when you correspond with us. Information may also be disclosed where lawfully required or necessary to establish or defend legal claims.

Published articles and their associated names, images, and credits can be viewed by the public and indexed or shared by third parties. Information sent privately by email is not automatically published.

8. International processing

Hosting, email, and network providers may process information outside your country. Cloudflare operates a global network, and its processing may include the United States and other countries. See Cloudflare’s privacy policy for its international-processing information. You can contact us for information about the recipients involved in your data processing and the applicable transfer arrangements.

9. How long information is kept

  • Sign-in records: expired sessions and refresh-token records are scheduled for regular cleanup. Cookie lifetimes are listed above.
  • Deleted accounts: after an account is marked for deletion, its main account record is scheduled for permanent removal after a 30-day retention period. Deletion does not automatically remove independently published articles, reusable editorial images, or information retained for another valid purpose.
  • Correspondence: retained for the time needed to handle the enquiry and relevant follow-up, taking account of the subject, any ongoing relationship, and legal requirements.
  • Technical logs and security records: retained according to the need to diagnose faults, investigate incidents, prevent recurring abuse, and meet legal requirements.
  • Editorial material: may remain in the magazine’s publication archive. Requests concerning it are assessed separately in light of the material and applicable law.

Backup copies, where maintained, follow the applicable backup rotation and access restrictions rather than necessarily being removed at the same moment as live records. Contact us if you need more information about a particular retention period.

10. Security

We use encrypted connections, restricted administrative access, password hashing, and authentication and abuse-prevention controls. These measures reduce risk, but no online service can guarantee complete security.

Automated security checks can temporarily restrict suspicious requests or repeated failed sign-in attempts. If you believe access has been restricted incorrectly, email us so it can be reviewed.

11. Your rights and requests

Subject to applicable law and its exceptions, you may request information or a copy of your data, correction, deletion or cessation of processing, blocking/restriction, and portability where available. You may object where applicable and withdraw any consent on which processing depends. These rights are not absolute; editorial/public-interest exceptions may apply. See Georgia’s Law on Personal Data Protection.

Send requests to [email protected]. Describe the information or article concerned. We may request proportionate identity verification and will respond within applicable statutory periods. Do not send passwords. You may also complain to the State Audit Office of Georgia or seek a court remedy, as provided by applicable law.

12. Changes and contact

We may update this policy when the website’s features, providers, or legal requirements change. The effective date at the top identifies the current version. For privacy questions or requests, contact [email protected].