CLAIMING DEL REYES ( SG#1)

CLAIMING DEL REYES ( SG#1)

  • WpView
    Reads 594
  • WpVote
    Votes 72
  • WpPart
    Parts 20
WpMetadataReadOngoing7h 19m
WpMetadataNoticeLast published Mon, Dec 15, 2025
Chae is a force to be reckoned with, a woman who stands tall on her own two feet, fiercely independent and strong-willed. She's been raised with a heart that beats to its own rhythm, unafraid to take on the world. But even the strongest among us have our moments of vulnerability. There are days when the weight of the world feels like it's crushing her, when the people she holds dear drift away, and she's left feeling drained and lost. It's in these moments that her true character shines through; she refuses to give up. Not on herself, not on her dreams, and certainly not on love.
All Rights Reserved
Join the largest storytelling communityGet personalized story recommendations, save your favourites to your library, and comment and vote to grow your community.
Illustration

You may also like

  • WHEN FATE MEETS DESTINY
  • UNVEILED
  • Til One Breaks
  • Coffee Heart Avenue Series #2: It's Ending with a LOVE
  • The princess and the General
  • What If I Was Nothing?
  • DROWNED (JenLisa/Chaesoo FF) (COMPLETED)
  • Addictive minds (18+)

She used to be the girl who feared no one - the one who spoke first, loved openly, and never apologised for it. Until one night destroyed everything. The world that once welcomed her suddenly judged her, and she learned the hardest lesson of all - loving honestly doesn't always mean being loved back kindly. Years later, Adira lives quietly, far from the girl she used to be. She runs a small café, keeps her distance from people, and trusts no one. Then he walks in. Kabir - the man she once loved... now holding the hand of a two-year-old boy. And the child looks at her like she already belongs in his world. Old wounds reopen. Unspoken truths resurface. And the past refuses to stay buried. Sometimes fate and destiny meet in the most unexpected ways - and second chances come when you least expect them.

More details
WpActionLinkContent Guidelines