LEGAL

PARK ME — PRIVACY POLICY

Effective Date: 09/09/2026
Last Updated: 09/09/2026

This Privacy Policy explains how PARK ME, a software-as-a-service application developed and operated by INKED BYTES, collects, uses, stores, processes, shares and protects personal data when you access or use the PARK ME website, mobile application, mobile website, dashboards, APIs, payment interfaces, booking services, parking-space listing services and other related features.

For purposes of this Privacy Policy:

PARK ME, Park Me, INKED BYTES, we, us and our refer to the legal entity operating the PARK ME Platform.

Our details are:

INKED BYTES

Legal Entity Name
INKED BYTES LLP
Entity Type
LLP
Registered Address
Door No. 42, Narikkundam, Narayana Nivas, Iritty, Iritty, Thalassery, Kannur- 670703, Kerala, India
GSTIN
NILL
CIN/LLPIN
ACX-5848
Email
inkedbytes.saas@gmail.com
Support Email
inkedbytes.saas@gmail.com
Grievance Officer
Deepak Dileep Kumar K
Grievance Email
inkedbytes.saas@gmail.com

By using PARK ME, you acknowledge that your personal data may be processed in accordance with this Privacy Policy and applicable law.

1. PURPOSE OF THIS PRIVACY POLICY

PARK ME connects drivers looking for parking with individuals, businesses, landlords, property managers, commercial operators and other authorized persons who make parking spaces available.

Because operating this service requires information about users, vehicles, locations, bookings and payments, we collect certain personal data necessary to:

  • create and maintain accounts
  • locate nearby parking
  • enable parking searches
  • facilitate bookings
  • process payments
  • manage host listings
  • provide directions
  • communicate booking information
  • protect users and the Platform
  • prevent fraud
  • comply with legal requirements
  • improve PARK ME

We seek to collect only information reasonably necessary for legitimate and specified purposes.

2. APPLICABLE DATA PROTECTION FRAMEWORK

Our handling of personal data is intended to comply with applicable Indian laws and regulations, including, where applicable:

  • Digital Personal Data Protection Act, 2023
  • Digital Personal Data Protection Rules, 2025
  • Information Technology Act, 2000
  • applicable cybersecurity directions and regulations
  • Consumer Protection Act, 2019
  • Consumer Protection (E-Commerce) Rules, 2020
  • applicable payment-system requirements
  • other laws relevant to our operations

India's DPDP Act defines personal data broadly as data about an individual who is identifiable by or in relation to such data. It also defines processing to include operations such as collection, storage, use, sharing, restriction and deletion.

The final DPDP Rules were notified in November 2025 and have phased commencement dates for different obligations.

3. OUR ROLE UNDER DATA PROTECTION LAW

Depending on the context, INKED BYTES may act as a Data Fiduciary in determining why and how personal data is processed through PARK ME.

For example, we generally determine the purposes and means of processing relating to:

  • account administration
  • PARK ME bookings
  • payment records
  • platform security
  • customer support
  • fraud prevention
  • analytics
  • notifications
  • Platform operations

Certain third-party providers may process personal data on our behalf as service providers or processors.

Parking Hosts may also independently process certain personal data made available to them for purposes of fulfilling a Booking.

Where a Host independently determines how personal data is processed beyond the purposes authorized by PARK ME, that Host may have its own independent legal obligations.

4. DEFINITIONS

For purposes of this Privacy Policy:

"Personal Data" means information about an identifiable individual, consistent with applicable law.

"Processing" includes collecting, recording, organizing, storing, retrieving, using, transmitting, sharing, restricting, deleting or otherwise handling Personal Data.

"Data Principal" means the individual to whom Personal Data relates.

"Driver" means a User searching for or reserving parking.

"Host" means a User who lists or provides a Parking Space.

"Parking Space" means a location offered for parking through PARK ME.

"Booking" means a parking reservation made through the Platform.

"Platform" means all PARK ME applications, websites, APIs, dashboards and related services.

"Service Provider" means a third party processing information for or on behalf of PARK ME.

5. PERSONAL DATA WE MAY COLLECT

The categories below describe information we may collect depending on how you use PARK ME.

5.1. Account and Identity Information

We may collect:

  • full name
  • username
  • mobile number
  • email address
  • profile photograph
  • date of birth, where required
  • account ID
  • login credentials
  • OTP verification status
  • authentication information

We may use third-party identity providers where available.

5.2. Contact Information

We may collect:

  • mobile phone number
  • email address
  • residential or business address
  • contact preferences
  • emergency or alternate contact details where applicable

5.3. Driver Vehicle Information

Drivers may provide:

  • vehicle registration number
  • vehicle make
  • vehicle model
  • colour
  • vehicle type
  • vehicle dimensions
  • fuel type
  • EV status
  • photographs or other identification details where necessary

This information allows Hosts to identify authorized vehicles.

5.4. Location and Geolocation Data

Location information is central to PARK ME.

We may collect:

  • approximate device location
  • precise GPS location, where permission is granted
  • searched destinations
  • parking location coordinates
  • navigation start points
  • route-related information
  • IP-derived approximate location
  • Booking arrival/departure location signals

Location data may be collected:

  • when you search for nearby parking
  • when you use navigation
  • when you check in
  • when you verify your arrival
  • when a location-based fraud check is performed
  • when another location feature is actively being used

We will request device permission where required.

6. PRECISE LOCATION DATA

Precise geolocation may be particularly important to the PARK ME service.

For example, we may use it to:

  • identify parking spaces near you
  • calculate distance
  • display your position on a map
  • provide navigation
  • estimate arrival
  • confirm that you are near a reserved space
  • prevent location-related Booking fraud
  • improve location accuracy

You can disable location access through your device or browser settings.

However, certain features may not work properly without it.

We should not continuously collect precise background location unless such collection is genuinely required for a disclosed feature and appropriate permissions have been obtained.

7. PARKING SEARCH DATA

When you search for parking, we may collect:

  • destination
  • search location
  • selected map area
  • search date
  • start time
  • duration
  • filters
  • price preferences
  • vehicle type
  • Parking Spaces viewed
  • Listing interactions
  • search-result selections

We use this to generate relevant parking results.

8. BOOKING INFORMATION

When you make or manage a Booking, we may process:

  • Booking ID
  • Driver identity
  • Host identity
  • Parking Space
  • location
  • start time
  • end time
  • duration
  • price
  • vehicle
  • payment status
  • entry instructions
  • Booking status
  • extension requests
  • cancellation information
  • Booking communications

9. HOST INFORMATION

Hosts may be required to provide additional information including:

  • full legal name
  • business name
  • mobile number
  • email
  • business address
  • Parking Space address
  • bank account details
  • payout information
  • PAN
  • GSTIN
  • identity-verification details
  • property information
  • proof of ownership
  • lease documentation
  • authorization documentation
  • parking photographs
  • parking coordinates
  • operating hours
  • rate information
  • cancellation rules
  • accessibility information

10. HOST VERIFICATION DATA

Where Host verification is required, we may collect documents or information such as:

  • PAN
  • government-issued ID
  • business-registration records
  • GST registration
  • bank-account verification
  • property documentation
  • owner authorization
  • apartment association or RWA permission
  • video verification
  • verification photographs

We will seek to limit access to verification information to personnel and Service Providers who require it.

11. PAYMENT INFORMATION

Payments may be handled by regulated third-party Payment Service Providers.

Depending on the payment method, PARK ME may receive information such as:

  • transaction ID
  • payment method type
  • masked card information
  • payment gateway response
  • UPI transaction reference
  • amount
  • currency
  • payment status
  • refund status
  • payment timestamp
  • billing information
  • chargeback information

PARK ME should generally avoid storing full payment-card credentials where processing is delegated to a compliant Payment Service Provider.

12. BANK AND PAYOUT INFORMATION

For Hosts receiving payouts, we may collect or receive:

  • bank-account holder name
  • account number
  • IFSC
  • UPI identifier
  • payout account ID
  • beneficiary verification status
  • settlement details
  • payout transaction information

This information may be shared with payment providers as required for settlements.

13. TAX INFORMATION

Where legally required, we may collect:

  • PAN
  • GSTIN
  • tax-registration status
  • legal entity name
  • business type
  • billing address
  • invoice information
  • withholding or tax-reporting details

14. COMMUNICATION DATA

We may collect communications involving PARK ME, including:

  • customer-support messages
  • complaint submissions
  • emails
  • chat messages
  • Host-Driver messages
  • refund requests
  • dispute communications
  • support-call records
  • feedback
  • legal notices

Calls may be recorded where appropriate and after providing applicable notice.

15. RATINGS, REVIEWS AND FEEDBACK

If PARK ME supports ratings or reviews, we may collect:

  • rating score
  • written review
  • photos submitted with reviews
  • Booking reference
  • reviewer account
  • Host response
  • moderation information

Reviews may be publicly displayed alongside profile information as described on the Platform.

16. DEVICE AND TECHNICAL INFORMATION

When you access PARK ME, we may automatically collect:

  • IP address
  • browser type
  • operating system
  • device type
  • device identifiers
  • application version
  • language
  • time zone
  • network information
  • crash logs
  • request timestamps
  • referring URL
  • pages viewed
  • session identifiers
  • diagnostic data

17. SECURITY INFORMATION

For security and fraud-prevention purposes, we may process signals such as:

  • login history
  • failed login attempts
  • device changes
  • suspicious IP activity
  • abnormal Booking activity
  • unusual payment behaviour
  • repeated account creation
  • OTP events
  • fraud scores
  • account-security events

18. COOKIES AND SIMILAR TECHNOLOGIES

PARK ME's website may use cookies, local storage, SDKs, pixels and similar technologies.

These may be used for:

  • authentication
  • session continuity
  • security
  • preferences
  • analytics
  • performance monitoring
  • fraud prevention
  • marketing, where applicable

Cookies may include:

Essential cookies

Required for authentication, account security and basic Platform operation.

Preference cookies

Remember settings such as language or map preferences.

Analytics cookies

Help us understand how PARK ME is used.

Advertising cookies

May be used only where applicable and subject to appropriate choices or consent.

19. INFORMATION FROM THIRD PARTIES

We may receive information from third parties including:

  • Payment Service Providers
  • mapping providers
  • identity-verification services
  • authentication providers
  • analytics providers
  • referral partners
  • property managers
  • Hosts
  • fraud-prevention providers
  • government authorities where legally permitted

20. INFORMATION FROM GOOGLE OR APPLE LOGIN

If you choose to authenticate using Google, Apple or another identity provider, PARK ME may receive information permitted by your account settings, such as:

  • name
  • email address
  • profile image
  • provider account identifier
  • authentication confirmation

We do not receive your third-party account password.

21. INFORMATION ABOUT OTHER PEOPLE

Users should not provide Personal Data relating to other persons unless authorized to do so.

For example, if you enter another person's vehicle or contact information, you are responsible for ensuring you have appropriate authority.

22. HOW WE USE PERSONAL DATA

We may process Personal Data for the purposes described below.

22.1. Providing the PARK ME Service

We use information to:

  • create accounts
  • authenticate users
  • display Parking Spaces
  • enable search
  • manage Listings
  • create Bookings
  • manage reservations
  • provide directions
  • process payments
  • make Host payouts
  • provide customer support

22.2. Location-Based Parking Discovery

We may use your location to:

  • show nearby spaces
  • calculate distance
  • rank nearby Parking Spaces
  • display maps
  • generate navigation routes

22.3. Booking Fulfilment

We process relevant information so Hosts and Drivers can complete Bookings.

For example, a Host may receive:

  • Driver name
  • vehicle registration number
  • vehicle description
  • Booking period
  • information reasonably necessary to identify the authorized Vehicle

We do not intend to disclose unnecessary Driver data to Hosts.

23. HOST LISTING MANAGEMENT

We use Host information to:

  • publish Listings
  • display Parking Space details
  • verify Host eligibility
  • manage Bookings
  • communicate with Drivers
  • calculate earnings
  • issue payouts
  • administer Host accounts

24. PAYMENT PROCESSING

We process transaction information to:

  • authorize payments
  • confirm Bookings
  • reconcile transactions
  • issue refunds
  • settle Hosts
  • handle disputes
  • comply with tax and accounting obligations

25. CUSTOMER SUPPORT

We use account, Booking and communication data to:

  • respond to questions
  • investigate Parking Space issues
  • resolve disputes
  • issue refunds
  • diagnose technical problems
  • prevent repeated abuse

26. SAFETY AND FRAUD PREVENTION

We may process Personal Data to:

  • identify fake accounts
  • detect fraudulent Bookings
  • identify unauthorized Listings
  • prevent payment fraud
  • protect Hosts and Drivers
  • investigate suspicious activity
  • enforce our Terms
  • protect PARK ME systems

27. PLATFORM SECURITY

We may use information to:

  • detect attacks
  • block malicious traffic
  • prevent credential abuse
  • investigate security incidents
  • maintain audit logs
  • protect Platform availability

28. SERVICE IMPROVEMENT

We may analyze usage patterns to improve:

  • parking search
  • map experience
  • search ranking
  • user interface
  • pricing features
  • Host tools
  • fraud detection
  • navigation
  • customer support
  • system performance

29. ANALYTICS

We may use analytics technologies to understand:

  • number of visitors
  • popular features
  • search conversion
  • Booking completion
  • navigation patterns
  • device types
  • error rates
  • Platform performance

Where possible, analytics may be aggregated or de-identified.

30. PERSONALIZATION

PARK ME may personalize the service based on:

  • previous parking searches
  • previous Booking locations
  • saved Parking Spaces
  • vehicle preferences
  • commonly used filters
  • Platform interactions

Examples could include:

Parking near your usual office

or

Recently searched locations

31. PARKING RECOMMENDATIONS

We may rank or recommend Parking Spaces using factors including:

  • distance
  • availability
  • pricing
  • ratings
  • vehicle compatibility
  • search preferences
  • previous interactions

32. MARKETING COMMUNICATIONS

Where permitted, we may send communications about:

  • promotions
  • new features
  • offers
  • referral programs
  • new parking areas
  • Host opportunities
  • PARK ME updates

You may opt out of promotional communications.

Transactional messages required for Bookings or security are separate and may still be sent.

33. PUSH NOTIFICATIONS

If enabled, PARK ME may send push notifications about:

  • Booking confirmations
  • upcoming reservations
  • parking expiry
  • extensions
  • payment confirmation
  • Host communication
  • cancellations
  • offers

Users may manage push-notification permissions through device settings.

34. SMS AND WHATSAPP

Where supported and permitted, PARK ME may use SMS or WhatsApp for:

  • OTP verification
  • Booking confirmation
  • arrival instructions
  • cancellation alerts
  • payment notifications
  • support
  • permitted promotional communications

35. LEGAL AND REGULATORY COMPLIANCE

We may process or disclose Personal Data where necessary to:

  • comply with Indian law
  • comply with court orders
  • respond to lawful government requests
  • meet tax obligations
  • comply with cybersecurity requirements
  • comply with payment-system obligations
  • enforce legal rights

36. BASIS FOR PROCESSING

Where applicable under the DPDP framework, PARK ME may process Personal Data based on:

  • valid consent
  • certain legitimate uses recognized by applicable law

Where consent is relied upon, the consent request should clearly describe the Personal Data and specified purpose.

The DPDP framework is structured around processing for lawful purposes and provides rights and obligations for Data Principals and Data Fiduciaries.

37. CONSENT

Where consent is required, PARK ME intends for consent to be:

  • freely given
  • specific
  • informed
  • unambiguous
  • based on clear affirmative action

Consent should not be bundled unnecessarily.

For example, using precise GPS location should be separately understandable from receiving marketing communications.

38. WITHDRAWING CONSENT

Where processing is based on consent, you may withdraw consent through available Platform settings or by contacting us.

Withdrawal will not invalidate processing lawfully carried out before withdrawal.

If the information is essential to the service, withdrawal may prevent PARK ME from continuing to provide that feature.

For example, if you disable location permission, nearby-parking functionality may be limited.

39. DATA MINIMIZATION

We aim to collect only Personal Data that is reasonably necessary for the specified purpose.

Examples:

A Host usually needs your vehicle registration number to identify the booked Vehicle, but ordinarily does not require access to your full payment-card information.

A mapping provider may need coordinates for route calculation, but does not necessarily need your Host payout details.

40. PURPOSE LIMITATION

We do not intend to use Personal Data for materially incompatible purposes without an appropriate legal basis or notice.

41. ACCURACY OF INFORMATION

Users should maintain accurate Personal Data.

You can update certain information from your account.

For critical information, such as:

  • legal name
  • PAN
  • Host bank account
  • verified property information

additional verification may be required before changes take effect.

42. SHARING PERSONAL DATA

We may share Personal Data only as reasonably necessary for the purposes described in this Privacy Policy.

Potential recipients are described below.

43. SHARING WITH HOSTS

When a Driver books a Parking Space, we may provide the Host with information reasonably necessary to fulfil the Booking.

This could include:

  • Driver name
  • Booking ID
  • Vehicle registration
  • vehicle make/model/colour
  • Booking period
  • arrival information
  • Driver communication

Hosts are not authorized to use Driver information for unrelated marketing or other unauthorized purposes.

44. SHARING WITH DRIVERS

Drivers may receive Host or Parking Space information including:

  • Host/display name
  • Parking Space address
  • Parking coordinates
  • entry instructions
  • Host-approved communication channel
  • Parking Space details

Exact Parking Space information may be withheld until Booking where appropriate for privacy or security.

45. PAYMENT SERVICE PROVIDERS

We may share transaction-related information with banks, payment gateways, payment aggregators and settlement providers to:

  • process payments
  • authenticate transactions
  • settle Hosts
  • process refunds
  • prevent fraud
  • resolve payment disputes

46. MAP AND NAVIGATION PROVIDERS

We may provide location or route information to mapping providers such as those used to deliver:

  • maps
  • geocoding
  • navigation
  • distance calculations
  • location search

Such providers may process information under their own privacy terms.

47. CLOUD INFRASTRUCTURE PROVIDERS

Personal Data may be hosted or processed using cloud infrastructure.

Cloud providers may support:

  • databases
  • storage
  • backups
  • application servers
  • content delivery
  • security
  • logging

48. COMMUNICATION SERVICE PROVIDERS

We may use third parties for:

  • SMS
  • OTP
  • email
  • push notifications
  • customer support
  • WhatsApp messaging

They may receive only information reasonably necessary to provide those services.

49. ANALYTICS PROVIDERS

We may use analytics providers to understand Platform usage.

Analytics information may include:

  • device data
  • session events
  • page interactions
  • technical identifiers
  • approximate location

50. IDENTITY VERIFICATION PROVIDERS

Host verification or fraud checks may involve specialized providers.

Such providers may process:

  • identity details
  • documentation
  • government identifiers
  • verification results

51. PROFESSIONAL ADVISERS

We may disclose information to:

  • lawyers
  • accountants
  • auditors
  • insurers
  • consultants
  • other professional advisers

where reasonably necessary and subject to appropriate confidentiality obligations.

52. LAW ENFORCEMENT AND GOVERNMENT AUTHORITIES

We may disclose information where required or lawfully requested by:

  • courts
  • law enforcement
  • tax authorities
  • regulatory authorities
  • consumer authorities
  • cybersecurity authorities
  • other competent government agencies

53. EMERGENCY DISCLOSURES

Where legally permissible, we may disclose information where reasonably necessary to protect:

  • life
  • health
  • physical safety
  • users
  • property
  • PARK ME systems

54. BUSINESS TRANSFERS

If INKED BYTES undergoes:

  • merger
  • acquisition
  • restructuring
  • financing
  • asset sale
  • corporate reorganization
  • sale of the PARK ME business

Personal Data may be transferred as part of that transaction, subject to applicable law.

55. WE DO NOT SELL PERSONAL DATA AS A BUSINESS MODEL

PARK ME does not intend to sell users' Personal Data to unrelated third parties in exchange for money.

If this business practice changes materially, this Privacy Policy should be updated and appropriate notices or choices provided.

56. PUBLIC INFORMATION

Some information may be visible publicly.

For example, a Host Listing may display:

  • property photographs
  • approximate location
  • Parking Space description
  • price
  • rating
  • Host display name
  • availability

Hosts should not upload information they do not want publicly displayed.

57. EXACT ADDRESS VISIBILITY

For safety and privacy, PARK ME may show only an approximate location before Booking.

The precise address may be disclosed after a Booking is confirmed.

This policy may vary depending on the type of Parking Space.

58. PROFILE VISIBILITY

PARK ME may display limited profile information to facilitate trust.

We do not intend to publicly expose unnecessary contact, payment or identity-verification information.

59. DATA RETENTION

We retain Personal Data only for as long as reasonably necessary for:

  • providing services
  • maintaining accounts
  • fulfilling Bookings
  • resolving disputes
  • fraud prevention
  • security
  • taxation
  • accounting
  • regulatory compliance
  • legal claims

Retention periods may differ by data category.

60. PROPOSED RETENTION SCHEDULE

PARK ME may adopt an internal schedule such as:

Account information: For the duration of the active account plus an appropriate post-closure period.

Booking records: Typically retained for applicable tax, accounting, dispute and regulatory periods.

Payment records: Retained according to financial, accounting and regulatory requirements.

Host KYC records: Retained for the period required by applicable law and Payment Service Providers.

Support records: Retained for an appropriate period after case closure.

Security logs: Retained based on cybersecurity requirements and security needs.

Marketing consent records: Retained while consent is active and for an appropriate evidentiary period thereafter.

These periods should be finalized before launch based on PARK ME's actual regulatory obligations.

61. DELETION OF PERSONAL DATA

Where Personal Data is no longer required for the specified purpose and there is no lawful reason to retain it, PARK ME may delete or anonymize it.

Some information cannot be deleted immediately because of:

  • pending Bookings
  • outstanding payments
  • tax obligations
  • fraud investigations
  • disputes
  • security investigations
  • legal retention requirements

62. ANONYMIZED AND AGGREGATED DATA

PARK ME may create aggregated or anonymized data that does not identify an individual.

Examples include:

  • average parking prices by city
  • number of searches in an area
  • occupancy levels
  • average booking duration
  • parking demand trends

Such data may be used for:

  • analytics
  • planning
  • product development
  • market insights
  • business operations

63. INTERNATIONAL DATA TRANSFERS

PARK ME may use Service Providers with infrastructure or personnel outside India.

Where cross-border processing occurs, it will be handled in accordance with applicable Indian data-protection requirements.

PARK ME may implement appropriate contractual, security and organizational safeguards.

64. DATA HOSTING

PARK ME may host information in:

India; and/or

  • other jurisdictions permitted by applicable law

The exact infrastructure architecture may change as the Platform evolves.

65. SECURITY MEASURES

We intend to implement reasonable administrative, technical and organizational safeguards.

These may include:

  • encryption in transit
  • encryption at rest where appropriate
  • access controls
  • role-based permissions
  • password hashing
  • MFA for privileged accounts
  • secure secrets management
  • network protections
  • audit logging
  • vulnerability management
  • backup procedures
  • incident-response procedures
  • secure development practices
  • employee-access controls

66. PAYMENT SECURITY

We should use reputable payment providers rather than directly handling unnecessary financial credentials.

Sensitive payment details should be tokenized or handled by the Payment Service Provider wherever possible.

67. ACCESS CONTROL

Access to Personal Data should be restricted according to job responsibilities.

For example:

  • support staff may require Booking information
  • finance staff may require settlement information
  • developers generally should not require unrestricted access to production Personal Data
  • Hosts should receive only information needed for their Booking

68. EMPLOYEE AND CONTRACTOR CONFIDENTIALITY

INKED BYTES personnel and contractors with access to Personal Data may be subject to confidentiality and access-control obligations.

69. PERSONAL DATA BREACHES

A Personal Data breach can include unauthorized access, disclosure, alteration, loss, destruction or other compromise of Personal Data.

The DPDP Act expressly defines a personal data breach in terms of unauthorized processing or accidental disclosure, acquisition, sharing, alteration, destruction or loss of access that compromises confidentiality, integrity or availability.

PARK ME intends to maintain procedures for detecting, investigating, documenting and responding to security incidents.

70. BREACH NOTIFICATION

Where applicable law requires notification of a Personal Data breach to affected individuals, the Data Protection Board of India or another authority, PARK ME will seek to comply with applicable notification requirements.

71. USER SECURITY RESPONSIBILITIES

Users should:

  • use strong passwords
  • protect OTPs
  • not share account credentials
  • keep devices secure
  • review suspicious account activity
  • avoid phishing links
  • immediately report suspected account compromise

72. CHILDREN'S DATA

PARK ME is primarily intended for adults who can enter into legally binding parking transactions.

Users generally must be at least 18 years old.

PARK ME does not knowingly intend to provide parking-account services directly to children.

If we learn that Personal Data relating to a child has been collected contrary to applicable requirements, we may take steps to delete or appropriately handle it.

73. THIRD-PARTY LINKS

PARK ME may contain links to third-party websites, map providers, payment providers or other services.

This Privacy Policy does not govern independent third-party services.

Users should review those providers' privacy policies.

74. API INTEGRATIONS

PARK ME may integrate external APIs for functions such as:

  • maps
  • navigation
  • address lookup
  • payments
  • communications
  • identity verification
  • analytics
  • fraud prevention

Only information reasonably necessary for the relevant integration should be transmitted.

75. AUTOMATED DECISION-MAKING AND RISK SCORING

PARK ME may use automated systems to support decisions relating to:

  • fraud risk
  • search ranking
  • suspicious payments
  • duplicate accounts
  • Booking abuse
  • Listing quality

Where appropriate, significant enforcement actions may be subject to review.

76. SEARCH RANKING

Search results may use factors including:

  • distance
  • price
  • availability
  • user preferences
  • rating
  • Host responsiveness
  • space characteristics
  • Platform relevance

Ranking should not require disclosure of unnecessary Personal Data.

77. CCTV AT PARKING LOCATIONS

Some Parking Spaces may use CCTV operated by the Host, building owner, operator or security service.

PARK ME may not control such CCTV.

Hosts are responsible for operating surveillance systems lawfully.

Where PARK ME itself processes CCTV or imagery, such processing will be handled according to this Privacy Policy and applicable law.

78. ANPR / NUMBER-PLATE RECOGNITION

PARK ME may in the future support automatic number-plate recognition for:

  • parking access
  • Booking verification
  • check-in/check-out
  • fraud prevention
  • parking enforcement

Where implemented, PARK ME should provide appropriate notice before or at the point of collection.

79. PHOTOS OF PARKING SPACES

Hosts may upload images of:

  • parking bays
  • entrances
  • buildings
  • access points
  • signs
  • garages
  • surrounding areas

Hosts should avoid unnecessarily uploading:

  • identifiable individuals
  • vehicle plates unrelated to the Listing
  • private household information
  • documents visible in photographs
  • other unrelated Personal Data

80. DRIVER-PROVIDED PHOTOS

Drivers may submit photographs as evidence for:

  • inaccessible Parking Spaces
  • damage
  • disputes
  • blocked spaces
  • incorrect Listings
  • support cases

Such images may contain incidental Personal Data.

They should only be used for legitimate support and safety purposes.

81. ACCESS TO PERSONAL DATA

Subject to applicable law, you may have rights relating to Personal Data processed by PARK ME.

The exact scope of rights depends on applicable provisions and their commencement.

82. CORRECTION OF PERSONAL DATA

You may request correction of Personal Data that is:

  • inaccurate
  • incomplete
  • outdated

PARK ME may require verification before changing certain sensitive account details.

83. ERASURE REQUESTS

You may request erasure of Personal Data where applicable.

PARK ME may retain information where legally necessary for:

  • fraud prevention
  • payment reconciliation
  • legal claims
  • taxation
  • accounting
  • security
  • regulatory compliance

84. GRIEVANCE RIGHTS

You may raise concerns regarding processing of Personal Data.

PARK ME will maintain a grievance mechanism consistent with applicable law.

85. NOMINATION RIGHTS

Where applicable under the DPDP framework, a Data Principal may have the ability to nominate another individual to exercise certain rights in the event of death or incapacity.

Implementation will follow applicable statutory requirements as they become operative.

86. EXERCISING PRIVACY RIGHTS

Privacy requests may be submitted to:

  • inkedbytes.saas@gmail.com

Your request should include sufficient information to identify your account.

PARK ME may request reasonable verification before responding to protect against unauthorized disclosure.

87. AUTHORIZED REQUESTS

We may reject or seek additional verification for requests made by persons who cannot establish authority to act on behalf of another individual.

88. WITHDRAWAL OF MARKETING CONSENT

You may unsubscribe from promotional emails through the unsubscribe mechanism provided.

SMS, WhatsApp or push preferences may be managed through supported Platform settings or communication channels.

89. LOCATION PERMISSIONS

Location access can ordinarily be managed through your:

  • browser permissions
  • Android settings
  • iOS settings
  • device privacy settings

Disabling location may reduce functionality.

90. COOKIE CONTROLS

Users may control cookies through their browser.

Disabling essential cookies may prevent authentication or other Platform features from working.

91. DO NOT TRACK SIGNALS

PARK ME's handling of browser "Do Not Track" signals may depend on available technology and applicable requirements.

A separate cookie-preference mechanism may be provided where appropriate.

92. DATA PORTABILITY / ACCOUNT EXPORT

Where required or offered by PARK ME, users may request or obtain certain account information in a structured format.

Availability may depend on applicable law and technical feasibility.

93. ACCOUNT DELETION

Users may request account deletion.

Before deletion, PARK ME may require resolution of:

  • active Bookings
  • outstanding balances
  • payouts
  • disputes
  • refunds
  • fraud investigations

Certain transaction records may be retained where legally required.

94. HOST DATA AFTER LISTING REMOVAL

Removing a Parking Listing does not necessarily delete:

  • previous Booking records
  • tax records
  • payout history
  • dispute records
  • audit logs
  • legal compliance records

95. BACKUPS

Deleted Personal Data may remain temporarily in secured backups until those backups are rotated or overwritten according to our retention processes.

Backup copies should not ordinarily be restored for routine business use after deletion except where necessary for disaster recovery or legal requirements.

96. FRAUD AND SECURITY RETENTION

We may retain limited information regarding fraudulent or abusive accounts to prevent repeat abuse.

This may include:

  • account identifiers
  • device signals
  • payment-risk information
  • enforcement records

97. BUSINESS ANALYTICS AFTER ACCOUNT DELETION

Aggregated or anonymized information that no longer identifies you may continue to be used after account deletion.

98. DATA QUALITY

Users are responsible for providing accurate information.

Hosts have a particular obligation to ensure Parking Space location and access details are correct.

99. CHANGES TO THIS PRIVACY POLICY

We may update this Privacy Policy to reflect:

  • changes in law
  • new features
  • new Service Providers
  • security improvements
  • changes in business operations
  • changes in data processing

The "Last Updated" date will be revised accordingly.

100. MATERIAL CHANGES

Where changes materially affect how Personal Data is processed, PARK ME may provide notice through:

  • email
  • in-app notification
  • website banner
  • login notice
  • other appropriate mechanisms

Where applicable, renewed consent may be requested.

101. PRIVACY BY DESIGN

As PARK ME develops, INKED BYTES should incorporate privacy considerations into:

  • product design
  • database architecture
  • API access
  • user interfaces
  • analytics
  • Host dashboards
  • employee tooling
  • security architecture

102. DEFAULT PRIVACY SETTINGS

Where practical, features should default to reasonable privacy protection.

For example:

  • exact Host addresses can be hidden before Booking
  • Driver contact details can be masked
  • payment details should not be shown to Hosts
  • internal admin access should be role-restricted

103. MASKED COMMUNICATION

PARK ME may use:

  • in-app messaging
  • masked phone numbers
  • relay communications

to reduce unnecessary direct disclosure of Driver and Host contact information.

104. INTERNAL ADMIN ACCESS

PARK ME administrators may access information only where reasonably necessary for:

  • support
  • fraud investigations
  • technical troubleshooting
  • payment reconciliation
  • compliance
  • security

Access may be logged and monitored.

105. PRODUCTION DATABASE ACCESS

INKED BYTES should restrict direct production database access to authorized personnel.

Access should preferably involve:

  • individual accounts
  • MFA
  • audit logging
  • least-privilege permissions
  • approval processes

106. DEVELOPER AND TEST ENVIRONMENTS

Production Personal Data should not be copied into development or test environments unnecessarily.

Where representative data is required, anonymized or synthetic data should be preferred.

107. SUPPORT SCREEN ACCESS

Support personnel should only receive the minimum information needed to resolve a User's issue.

Sensitive data should be masked where possible.

108. HOST ACCESS RESTRICTIONS

Hosts may use Booking data only for legitimate parking-related purposes.

Hosts must not:

  • add Drivers to marketing lists without lawful authorization
  • sell Driver information
  • contact Drivers for unrelated purposes
  • publish Driver information
  • misuse vehicle registration information
  • retain unnecessary copies of User information

109. DRIVER RESPONSIBILITY FOR HOST INFORMATION

Drivers must also respect Host privacy.

Host addresses, gate codes and access instructions must not be:

  • publicly posted
  • shared unnecessarily
  • sold
  • used to enter property outside the Booking Period
  • used for unrelated purposes

110. ACCESS CODES AND SECURITY INFORMATION

Certain Parking Spaces may provide:

  • gate codes
  • access PINs
  • entry instructions
  • security contact details

These should be treated as confidential and used only for the relevant Booking.

111. EMERGENCY CONTACT INFORMATION

Where emergency contact information is collected, it will be used only for appropriate safety or emergency purposes.

112. VEHICLE LOCATION HISTORY

PARK ME should not maintain unnecessary long-term precise vehicle movement histories.

Where location history is required for Bookings, navigation or fraud investigations, retention should be proportionate to that purpose.

113. LOCATION DATA IN ANALYTICS

Precise GPS location should generally be avoided in broad analytics where approximate or aggregated geographic information is sufficient.

114. ADVERTISING

PARK ME may in the future display advertising.

If Personal Data is used for targeted advertising, the Privacy Policy and consent mechanisms should be updated appropriately before such processing begins.

115. THIRD-PARTY ADVERTISING

We should not provide precise parking-location histories to advertising networks merely for behavioral advertising unless there is a lawful basis, appropriate disclosure and any required consent.

116. AI AND MACHINE LEARNING

PARK ME may use machine-learning or AI systems in the future for:

  • parking-demand prediction
  • fraud detection
  • search ranking
  • customer support
  • pricing recommendations
  • operational optimization

Where Personal Data is used, processing will remain subject to this Privacy Policy and applicable law.

117. GENERATIVE AI SUPPORT

If PARK ME uses AI-assisted customer support, user messages may be processed by authorized technology providers.

Sensitive data should be minimized before transmission wherever practical.

118. DATA USED FOR MODEL TRAINING

PARK ME should not use identifiable private Booking communications to train general-purpose AI models unless this is expressly disclosed and legally permitted.

Aggregated or de-identified data may be used for service improvement.

119. PAYMENT FRAUD MODELS

Transaction metadata may be evaluated using automated fraud-detection systems.

Such systems may consider:

  • payment history
  • account age
  • transaction velocity
  • device signals
  • IP information
  • Booking patterns

120. SUSPICIOUS ACTIVITY

Where PARK ME identifies suspicious activity, it may:

  • request verification
  • restrict the account
  • delay payment
  • suspend a Listing
  • hold a Host payout
  • conduct an investigation

121. PUBLIC AUTHORITIES

Where required by lawful order or statutory obligation, PARK ME may preserve or disclose relevant records.

PARK ME does not intend to provide authorities unrestricted access to User data absent appropriate lawful authority.

122. LEGAL CLAIMS

We may retain and use Personal Data where reasonably necessary to:

  • establish legal claims
  • defend claims
  • enforce contracts
  • recover outstanding amounts
  • protect our legal rights

123. TAX AND ACCOUNTING RECORDS

Transaction data may need to be retained independently of an account-deletion request where required under applicable tax or accounting laws.

124. PARKING DISPUTES

For disputes involving:

  • property damage
  • inaccessible parking
  • overstaying
  • unauthorized parking
  • incorrect Listings
  • refund claims
  • accidents

we may preserve relevant Booking and communication data until the issue is reasonably resolved.

125. LAW ENFORCEMENT REQUEST PROCESS

Requests for information should be reviewed by authorized personnel.

Where appropriate, PARK ME may require:

  • valid legal authority
  • scope
  • identification of the relevant account
  • specific information requested
  • legal basis

126. SAFETY INCIDENTS

Information concerning serious safety incidents may be retained for longer where necessary for:

  • insurance
  • legal claims
  • regulatory investigations
  • prevention of repeated safety issues

127. HOST PROPERTY INFORMATION

Host property information may itself constitute Personal Data where it identifies an individual.

We should therefore avoid unnecessary disclosure of:

  • residential owner details
  • ownership documentation
  • personal correspondence
  • verification documents

128. MAP PIN ACCURACY

Hosts should verify that the Parking Space pin accurately identifies the correct entrance or parking location.

Incorrect pin information may inadvertently reveal or direct Drivers to neighboring property.

129. PRIVACY OF NEIGHBOURS AND THIRD PARTIES

Hosts should avoid including Personal Data relating to neighbours or third parties in:

  • Parking Space descriptions
  • photographs
  • directions
  • CCTV imagery
  • access instructions

130. USER RESPONSIBILITY FOR CONTENT

Users should consider privacy before uploading:

  • photos
  • videos
  • documents
  • reviews
  • messages
  • access instructions

131. CONTACTING US ABOUT PRIVACY

Questions concerning this Privacy Policy may be submitted to:

Privacy Team — PARK ME / INKED BYTES

Email
inkedbytes.saas@gmail.com

132. GRIEVANCE OFFICER

Privacy-related grievances may be addressed to:

Grievance Officer

Name
Deepak Dileep Kumar K
Designation
Grievance Officer
Company
INKED BYTES
Email
inkedbytes.saas@gmail.com
Phone
+91-6282420103
Address
Door No. 42, Narikkundam, Narayana Nivas, Iritty, Iritty, Thalassery, Kannur- 670703, Kerala, India

133. RESPONSE TO PRIVACY REQUESTS

We will seek to respond to valid privacy requests within timelines required under applicable law.

Requests may require identity verification.

134. DATA PROTECTION BOARD OF INDIA

Where statutory remedies become applicable and a complaint remains unresolved through PARK ME's grievance process, individuals may have rights to approach the Data Protection Board of India in accordance with the DPDP framework.

The Government established the Data Protection Board as part of the implementation measures notified alongside the final DPDP Rules in November 2025.

135. CONSENT MANAGERS

Where legally applicable and technically supported, individuals may be able to manage certain consent through registered Consent Managers under India's DPDP framework.

The DPDP Rules establish a framework for Consent Managers and their registration/operation.

136. LANGUAGE OF PRIVACY NOTICES

PARK ME may provide privacy notices in English and additional Indian languages.

Where local-language notices are provided, we will seek to keep them clear and understandable.

137. SUMMARY OF KEY PRIVACY PRACTICES

In practical terms, PARK ME's approach should be:

We collect what we need to help you find, book, pay for or provide parking.

We use precise location primarily when it is needed for parking discovery and navigation.

Hosts receive only the information reasonably required to service a Booking.

Payment credentials should be handled primarily by regulated payment providers rather than stored unnecessarily by PARK ME.

We do not intend to sell your Personal Data.

You can request correction, erasure or account closure subject to legal and operational requirements.

We apply reasonable security measures to protect Personal Data.

138. CONTACT DETAILS

PARK ME

A SaaS platform by INKED BYTES

Website
parkme.online
General Support
inkedbytes.saas@gmail.com
Privacy
inkedbytes.saas@gmail.com
Grievance
inkedbytes.saas@gmail.com

INKED BYTES

Legal Name
INKED BYTES LLP
Registered Address
Door No. 42, Narikkundam, Narayana Nivas, Iritty, Iritty, Thalassery, Kannur- 670703, Kerala, India
GSTIN
NILL
CIN/LLPIN
ACX-5848

Related: Terms and Conditions. Privacy questions: inkedbytes.saas@gmail.com.